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

AWS accounts with EC2-Classic support #2

Merged
merged 1 commit into from
Oct 30, 2017
Merged

AWS accounts with EC2-Classic support #2

merged 1 commit into from
Oct 30, 2017

Conversation

jac1013
Copy link
Member

@jac1013 jac1013 commented Oct 18, 2017

Hi Guys,

For getting context about the EC2-classic problem check this out.

Also you can see the problem in this issue too, I'll put a reference of this solution in the issue because it might help a lot people in the future.

So what we are doing here (In case you want to create everything from scratch in a EC2-Classic AWS accoun)t:

  • We create a VPC
  • We create a Route Table rule for the VPC in the default Route table of that VPC
  • Create an Internet Gateway and associate it with the VPC we just created.
  • Create a subnet and associate it with the VPC.
  • Associate the Security Group that we are creating with the VPC we just created, all of this is to be able to have "egress" rules in the Security Group.

TODO: #3

Thanks!

…re under EC2-classic way and don't use a VPC by default

added a readme explanation of why this module exist and its purpose
@jac1013 jac1013 merged commit b2c4e3c into master Oct 30, 2017
@jac1013 jac1013 deleted the ec2-classic branch October 30, 2017 21:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant