- Newest
- Most votes
- Most comments
Hi brunoaduarte,
I have done some testing and I think I know what is your issue.
Is your affected instance in us-east-1e AZ?
t3.2xlarge instances are not offered in us-east-1e AZ. This is the only AZ in us-east-1 region that does not have this instance type.
You can check the offering via AWS CLI, like this:
# aws ec2 describe-instance-type-offerings --location-type availability-zone --filters Name=instance-type,Values=t3.2xlarge --region us-east-1 --output table
-------------------------------------------------------
| DescribeInstanceTypeOfferings |
_-----------------------------------------------------_
|| InstanceTypeOfferings ||
|_--------------_--------------_---------------------_|
|| InstanceType | Location | LocationType ||
|_--------------_--------------_---------------------_|
|| t3.2xlarge | us-east-1b | availability-zone ||
|| t3.2xlarge | us-east-1c | availability-zone ||
|| t3.2xlarge | us-east-1a | availability-zone ||
|| t3.2xlarge | us-east-1d | availability-zone ||
|| t3.2xlarge | us-east-1f | availability-zone ||
|_--------------_--------------_---------------------_|
Source:
https://aws.amazon.com/premiumsupport/knowledge-center/ec2-instance-type-not-supported-az-error/
If you would like to use AWS CLI, first you have to install it:
https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html
Then configure:
https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html
In order to solve your issue, create an AMI out of your instance and launch a new, t3.2xlarge instance in any other AZ. You can specify AZ in the "Next: Configure Instance Details" -> "Subnet" dropdown menu.
Here you will find information regarding creation of AMI:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-ebs.html#how-to-create-ebs-ami
Hope that this will help you.
Regards,
Daniel
Hi,
Use the Nitro script created by AWS. It will check prerequisites on your T2 instance for changing to T3:
https://github.com/awslabs/aws-support-tools/tree/master/EC2/NitroInstanceChecks
As for the errors, check the Knowledge Center, you can find there most common issues:
https://aws.amazon.com/premiumsupport/knowledge-center/boot-error-linux-nitro-instance/
Daniel
Hi Daniel, thanks for the reply, but even though the script shows no error messages i still cannot start the instance after changing it's type from t2.2xlarge to t3.2xlarge
I run "nitro_check_script.sh" and the response is OK for all
OK NVMe Module is installed and available on your instance
OK ENA Module with version is installed and available on your instance
OK fstab file looks fine and does not contain any device names.
The following error message is presented when i try to start it
"Error starting instances The requested configuration is currently not supported. Please check the documentation for supported configurations."
I even tried to create a brand new t2.2xlarge instance and changed the type to t3 just to test it and it also doesn't work.
Relevant content
- asked 2 years ago
- asked 5 years ago
- AWS OFFICIALUpdated 13 days ago
- AWS OFFICIALUpdated a year ago