Skip to content
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

Closed
cmacmurray opened this issue Nov 16, 2015 · 7 comments
Closed

Terraform Launch Configuration Will only Launch in Default VPC #3942

cmacmurray opened this issue Nov 16, 2015 · 7 comments

Comments

@cmacmurray
Copy link

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.

@jen20
Copy link
Contributor

jen20 commented Nov 17, 2015

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?

@catsby
Copy link
Member

catsby commented Jan 8, 2016

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!

@catsby catsby closed this as completed Jan 8, 2016
@patrobinson
Copy link

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 The security group 'sg-abcd1234,sg-1234abcd' does not exist in default VPC 'vpc-abcd1234' is deceptive, it actually means that the security group was not found anywhere, because you've provided a comma separated list of IDs!

@jkinred
Copy link
Contributor

jkinred commented Mar 20, 2016

@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.

@n-my
Copy link

n-my commented Sep 18, 2016

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 :
'sg_bastion' does not exist in default 'VPC vpc-xxx'

omeid pushed a commit to omeid/terraform that referenced this issue Mar 30, 2018
…ladvictor/fix-service-linked-role-update

resource/aws_autoscaling_group: Fix updating of service_linked_role
omeid pushed a commit to omeid/terraform that referenced this issue Mar 30, 2018
@dmcgowandmc
Copy link

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

@apparentlymart
Copy link
Member

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.

@hashicorp hashicorp locked and limited conversation to collaborators Nov 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants