ecs_takeover creation fail >>> FIX about cloudgoat HOT 6 CLOSED

What issue is this fixing?

It fixes this issue:

╷
│ Error: creating EC2 Instance: InvalidParameterValue: The t2.micro instance type does not support an AMI with a boot mode of UEFI. Only instance types built on the Nitro System support UEFI. Specify an instance type that supports UEFI, and try again.
│ 	status code: 400, request id: 
│ 
│   with aws_instance.vulnsite,
│   on ec2.tf line 23, in resource "aws_instance" "vulnsite":
│   23: resource "aws_instance" "vulnsite" {
│ 
╵
╷
│ Error: creating EC2 Instance: InvalidParameterValue: The t2.micro instance type does not support an AMI with a boot mode of UEFI. Only instance types built on the Nitro System support UEFI. Specify an instance type that supports UEFI, and try again.
│ 	status code: 400, request id: 
│ 
│   with aws_instance.vault,
│   on ec2.tf line 37, in resource "aws_instance" "vault":
│   37: resource "aws_instance" "vault" {
│ 
╵

from cloudgoat.

What issue is this fixing?

It fixes this issue:

╷
│ Error: creating EC2 Instance: InvalidParameterValue: The t2.micro instance type does not support an AMI with a boot mode of UEFI. Only instance types built on the Nitro System support UEFI. Specify an instance type that supports UEFI, and try again.
│ 	status code: 400, request id: 
│ 
│   with aws_instance.vulnsite,
│   on ec2.tf line 23, in resource "aws_instance" "vulnsite":
│   23: resource "aws_instance" "vulnsite" {
│ 
╵
╷
│ Error: creating EC2 Instance: InvalidParameterValue: The t2.micro instance type does not support an AMI with a boot mode of UEFI. Only instance types built on the Nitro System support UEFI. Specify an instance type that supports UEFI, and try again.
│ 	status code: 400, request id: 
│ 
│   with aws_instance.vault,
│   on ec2.tf line 37, in resource "aws_instance" "vault":
│   37: resource "aws_instance" "vault" {
│ 
╵

This ^^^
Thank you!

from cloudgoat.

What issue is this fixing?

from cloudgoat.

Do you know what ami it was using?
Its pulling the latest image and it can be for arm64 which requires uefi. If I require it to be x86_64 it should still work with t2.micro

from cloudgoat.

Do you know what ami it was using? Its pulling the latest image and it can be for arm64 which requires uefi. If I require it to be x86_64 it should still work with t2.micro

Sorry I do not recall, but it is whatever you had in your original terraform files I believe

from cloudgoat.

NP
Its probably an issue that only happens sometimes depending when AWS release a new AMI. Should be solved by #219

from cloudgoat.