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

specify Placement Groups #5

Open
dsmiley opened this issue Aug 20, 2016 · 1 comment
Open

specify Placement Groups #5

dsmiley opened this issue Aug 20, 2016 · 1 comment

Comments

@dsmiley
Copy link

dsmiley commented Aug 20, 2016

To maximize network performance between my EC2 machines that will be talking to each other, I need to specify the "Placement Group":
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html
Once that's done, then my instances stand to possibly benefit from "Enhanced Networking": http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html Although I'd need to investigate if the AMI & setup Kontena does is enabled for it.

If maintaining this stuff in the Kontena AWS plugin gets unwieldy, it would at least be nice to document a method in which I could create Kontena nodes manually in EC2.

@dsmiley
Copy link
Author

dsmiley commented Aug 20, 2016

Partially answering my own question, it appears I can use CoreOS on EC2 and then use Kontena's CoreOS config generator: https://www.kontena.io/docs/getting-started/installing/coreos#installing-kontena-nodes So in this way I can self-serve instance creation, letting me handle that part. This should give more control over various things (e.g. instance volumes) wherein I'll customize the CoreOS config Kontena generates. It's not yet evident if there is a point in doing this in ECS (EC2 Container Service). Better monitoring perhaps?

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

No branches or pull requests

1 participant