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

providers/aws: fix LCs being invalid in classic #1412

Merged
merged 1 commit into from
Apr 7, 2015
Merged

Conversation

phinze
Copy link
Contributor

@phinze phinze commented Apr 7, 2015

Turns out AssociatePublicIPAddress was always being set, but the AWS
APIs don't like that when you're launching into EC2 Classic and return a
validation error at ASG launch time.

Fixes #1410

Turns out AssociatePublicIPAddress was always being set, but the AWS
APIs don't like that when you're launching into EC2 Classic and return a
validation error at ASG launch time.

Fixes #1410
@catsby
Copy link
Contributor

catsby commented Apr 7, 2015

👍

phinze added a commit that referenced this pull request Apr 7, 2015
providers/aws: fix LCs being invalid in classic
@phinze phinze merged commit a9ea489 into master Apr 7, 2015
@phinze phinze deleted the b-asg-in-classic branch April 7, 2015 22:31
@ghost
Copy link

ghost commented May 3, 2020

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.

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

Successfully merging this pull request may close these issues.

Cannot create ASG in EC2 Classic
2 participants