-
Notifications
You must be signed in to change notification settings - Fork 62
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 ECS server endpoint #398
Comments
@wparad since you voted for this feature, I'm curious if your use case would require |
I'm not totally sure I understand what the difference would be. Is there one that is easier? That we could test out and if works great! and if not we could create follow up issue? |
- Add ECS Server doc - create basic CLI utility boilerplate - refactor exec to make it easier to use for ecs Refs: #398
- Add ECS Server doc - create basic CLI utility boilerplate - refactor exec to make it easier to use for ecs Refs: #398
- Add ECS Server doc - create basic CLI utility boilerplate - refactor exec to make it easier to use for ecs Refs: #398
- Add ECS Server doc - create basic CLI utility boilerplate - refactor exec to make it easier to use for ecs Refs: #398
- Totally stealing code from aws-vault - refactor our interactive prompt code for exec/ecs load/console Fixes: #398
- Add ECS Server doc - create basic CLI utility boilerplate - refactor exec to make it easier to use for ecs Refs: #398
This is different from the standard metadata service #265 because it runs on an ephemeral port and depends on the SDK supporting
AWS_CONTAINER_CREDENTIALS_FULL_URI
More info how this works here: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html
https://docs.aws.amazon.com/sdkref/latest/guide/feature-container-credentials.html
The text was updated successfully, but these errors were encountered: