-
Notifications
You must be signed in to change notification settings - Fork 618
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
Enable credentials endpoint for ecs task role? #511
Comments
Btw, is there anyway to add custom fields to the credentials payload? |
@jamesongithub Are you using the ECS-optimized AMI or did you manually install the ECS agent? It looks like the |
The agent should be listening on 51679 as well; that's the credential endpoint. I'll make a note to update the README; the most up-to-date instructions on launching the agent on Ubuntu are in our documentation. |
Ah, that makes sense. Thanks for the quick response. Anyway to add custom fields to the creds response btw? |
No, the credential endpoint only returns credentials. What kinds of custom things are you looking for it to return? |
Other secrets that we would like to pass instead of having them show up as plaintext envs in the aws ecs console. |
@jamesongithub That sounds pretty similar to #328. @aaithal's suggestion on that issue is a good approach. I've also opened #512 to update the README. Thanks for catching the errors! |
yup. thanks! |
@samuelkarp, @aaithal: I am having the same issue and I have logs. Should I open a ticket? I'd appreciate if you can help me debug this, but I don't want to leave my broken container error'ing out for much longer. My work email is hugo at yipitdata.com I am running the latest agent (ECS-optimized AMI ami-04351e12). Thanks |
@hltbra I'm sorry that you're running into this issue. Please create a new github issue or a support case via the AWS Developer Support program. Thanks! |
@aaithal: cool. I created an AWS Support ticket with logs from my application and the ECS agent (case ID 4260162261). |
Seem to be having problems with getting credentials from ecs-agent within the container. The route doesn't seem to be available.
ecs-agent env
Is there anything else needed to enable ecs iam roles for ecs agent?
The text was updated successfully, but these errors were encountered: