Skip to content

Conversation

@micvbang
Copy link

Hey!

Since this endpoint exposes AWS credentials directly to any callers, it is of utmost importance that it not be called by unauthorized 3rd parties. By listening only on 169.254.170.2, instead of all available interfaces, we ensure that it's only possible for callers that have access to that IP address to retrieve credentials. This avoids the potential mistake of e.g. hosting this with Docker's host networking and potentially making it publicly available.

Since this endpoint exposes AWS credentials directly to any callers, it
is of utmost importance that it not be called by unauthorized 3rd
parties. By listening only on 169.254.170.2, we ensure that it's only
possible for callers that have access to that IP address to retrieve
credentials. This avoids the potential mistake of e.g. hosting this with
host networking and allowing it publicly on all available interfaces.
@micvbang micvbang changed the title contrib: aws-vault proxy must listen on 169.254.170.2 contrib: aws-vault proxy listen on 169.254.170.2 May 16, 2024
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

Successfully merging this pull request may close these issues.

1 participant