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 IMDS V2 Support #238

Closed
ericlarssen-wf opened this issue Oct 8, 2020 · 1 comment · Fixed by #249
Closed

AWS IMDS V2 Support #238

ericlarssen-wf opened this issue Oct 8, 2020 · 1 comment · Fixed by #249
Assignees
Labels
p1 Highest priority work items

Comments

@ericlarssen-wf
Copy link

ericlarssen-wf commented Oct 8, 2020

Summary

AWS has created a newer protocol to communicate with the Metadata server ( context), that enables clients to use a session based request which is more secure. With the idea of deprecating the usage of the V1 protocol, we rely on the agent to no longer use that authentication method.

Desired Behaviour

Adopt the session based authentication with the AWS metadata server.

Describe Alternatives

None that I can think of.

Additional context

https://krebsonsecurity.com/2019/08/what-we-can-learn-from-the-capital-one-hack/

@RichVanderwal
Copy link
Contributor

Hi @ericlarssen-wf , thanks for this request! I've reviewed the Java Agent changes to accept this token and forward it through with the next IMDS request, and now I'll bring our Product Manager in on this one to get her input on how this works with our roadmap.

@jodeev jodeev added the p1 Highest priority work items label Oct 21, 2020
@RichVanderwal RichVanderwal self-assigned this Nov 12, 2020
@jodeev jodeev closed this as completed Nov 13, 2020
@jodeev jodeev reopened this Nov 13, 2020
@RichVanderwal RichVanderwal linked a pull request Nov 25, 2020 that will close this issue
@jodeev jodeev closed this as completed Dec 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p1 Highest priority work items
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants