-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error launching source instance: Your requested instance type (t2.micro) not supported in your requested Availability Zone (us-west-2d). #68
Comments
This kind of errors usually happens when the subnet is not specified (or not specified with the correct value). Could you verify that you specify correct subnet? Please include terraform code if the problem persists. |
No I am not, but I am creating the complete tire-2 setup from scratch using terraform configuration and only specifying us-west-2 as the region, and amiID. So I couldn't define the subnet ahead of the run. Does that mean such error could not be suppressed in such use-cases? |
You should reference values from VPC as an argument into this module as specified here - https://github.com/terraform-aws-modules/terraform-aws-ec2-instance/blob/master/examples/basic/main.tf#L62 |
This does seem like a better approach. Thanks. |
Hi, I have the same issue. I'm not sure what you mean with "reference values from VPC as an argument". I used this https://github.com/terraform-aws-modules/terraform-aws-ec2-instance/blob/master/examples/basic to create the ec2 instances. |
@jakemonton AWS may enable and disable certain types of instances or other resources (eg, when AZ is down, you can't launch resources there) at their discretion. "reference values from VPC as an argument" means that to make this working you need to set I hope it helps. |
@antonbabenko I was able to make it work. It was the |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Getting this error every now and then while I am running my test configurations. The point to note is, I haven't specified us-west-2d availability zone in any of my configurations. And when I get this error, I do a
terraform destroy
(to destroy created VPC, subnets, etc.), and then runterraform apply
again. On the second time, it completes without any errors.The text was updated successfully, but these errors were encountered: