Update Launch-Test Instance-Type to One That Supports EFI

[ferricoxide]

Expected behavior

Test-launches work whether or not the bootstrap-AMI is EFI-enabled or not

Actual behavior

With the use of m4.large instance types in the current tests/minimal-linux.pkr.hcl, test launches will fail if the bootstrap AMI was EFI-enabled.

Steps to reproduce behavior

1. Create EFI-enabled AMI using EFI-enabled bootstrap-AMI
2. Execute spel launch-test using an instance type that doesn't support EFI-enabled
3. Wait for test to experience a timeout-failure
4. Look at failed test-EC2's console screencap and find a failed boot like:

Context/Specifications

Things like:

• Template name
• AWS Component
• OS/AMI information

Suggestions for fix

Update instance-type to one that supports EFI. Using:

aws ec2 describe-instance-types \
  --filters Name=supported-boot-mode,Values=uefi 'Name=instance-type,Values=t*' \
  --query 'InstanceTypes[?
    ProcessorInfo.SupportedArchitectures[] == `["x86_64"]`
  ].[InstanceType]' --output text | \
sort

Any of the following instance-types:

t3.2xlarge
t3.large
t3.medium
t3.micro
t3.nano
t3.small
t3.xlarge
t3a.2xlarge
t3a.large
t3a.medium
t3a.micro
t3a.nano
t3a.small
t3a.xlarge

Should suffice. Alternately, if one wishes to stay with the m family of instance-types, upgrade to m5, m6i or m7i.