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

Support for configuring ClassicLink (VPC & launch configuration) #2985

Closed
neurogenesis opened this issue Aug 12, 2015 · 6 comments
Closed

Support for configuring ClassicLink (VPC & launch configuration) #2985

neurogenesis opened this issue Aug 12, 2015 · 6 comments

Comments

@neurogenesis
Copy link

While new AWS accounts are VPC-only by default, older accounts may have a bulk of their hosts provisioned in classic / public EC2 instances.

For large customers migrating from classic EC2 to VPC, the best practice is to migrate back-end services like SMTP clusters, databases or message queue servers into VPCs first. Connectivity from classic/public EC2 instances into private ip only VPCs is then enabled via ClassicLink per-instance or with an autoscaling launch configuration.

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/vpc-classiclink.html
https://aws.amazon.com/blogs/aws/classiclink-private-communication-between-classic-ec2-instances-vpc-resources/

The two pieces required for this to work are enabling ClassicLink on the VPC and enabling it on the instances / launch configuration.

It looks like it's partially supported in the AWS GO-SDK (autoscale launch configurations):

https://github.com/aws/aws-sdk-go/blob/7eb22717a36d32f4c60645b914ce54ba7c8b375d/service/autoscaling/api.go#L2063

@neurogenesis neurogenesis changed the title Add support for ClassicLink Support for configuring ClassicLink (VPC & launch configuration) Aug 12, 2015
@CpuID
Copy link
Contributor

CpuID commented Aug 12, 2015

Also, the only way to get any IPv6 support in AWS right now is via an ELB outside of a VPC, with EC2 instances outside a VPC. This is a specific use case where ClassicLink is useful for newly created instances.

@catsby
Copy link
Contributor

catsby commented Jan 12, 2016

I just merged #3994 to address this, let me know if you need anything else!

@catsby catsby closed this as completed Jan 12, 2016
@dfboyd
Copy link

dfboyd commented Sep 29, 2016

What about launching EC2 instances with ClassicLink enabled? There's nothing in the HCL documentation to suggest this is possible.

@howdoicomputer
Copy link

@catsby @dfboyd So... is creating vanilla classic instances with ClassicLink enabled a thing? That would be tops for doing migrations.

@lra
Copy link

lra commented May 5, 2017

@dfboyd @howdoicomputer I don't see such a thing, and I doubt it will ever be supported as the AWS API can only attach a classic link to running instances, which lose it on stop/terminate.

Hard to keep a state out of this.

@ghost
Copy link

ghost commented Apr 13, 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 Apr 13, 2020
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

6 participants