-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Terraform Launch Configuration Will only Launch in Default VPC #3942
Comments
Hi @cmacmurray. Thanks for opening this, it should be straightforward enough to reproduce. Can you confirm whether your launch configuration target the default VPC? Alternatively do you have a minimal configuration that you could post showing this? |
Hey @cmacmurray – we haven't heard back in a while so I'm going to close this. Please let us know if you're still having an issue here. Thanks! |
I had this issue today, the issue was when I tried to pass a comma separated list of Security Group IDs but forgot split them. The error message from AWS |
@Nemski - Thanks a lot for posting your findings, luckily I found your comment here as I could have wasted hours trying to track the problem down. |
I had the same issue when specifying a security group name instead of its id. The error message is misleading. I am not using the default VPC but got the message : |
…ladvictor/fix-service-linked-role-update resource/aws_autoscaling_group: Fix updating of service_linked_role
Yeah, I got caught out with this one as well. It was as simple as wrong spelling meaning the security group technically didn't exist anywhere. A more accurate error message would be nice |
Hi all, The AWS provider is no longer developed in this repository. If you have feedback on the AWS provider, please open a new issue in the AWS provider's own repository. |
I have specified my vpc_zone_identifier's in my auto scaling group, however when I try to run terraform apply, it will fail with the error that the SG specified for the scaling group is not in the default VPC.
The text was updated successfully, but these errors were encountered: