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

Added container credential provider to the credential precedence documentation #4338

Merged
merged 2 commits into from
Nov 22, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/source/guide/credentials.rst
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,7 @@ Boto3 will look in several locations when searching for credentials. The mechani
#. Shared credential file (``~/.aws/credentials``)
#. AWS config file (``~/.aws/config``)
#. Boto2 config file (``/etc/boto.cfg`` and ``~/.boto``)
#. Container credential provider
#. Instance metadata service on an Amazon EC2 instance that has an IAM role configured.

Each of those locations is discussed in more detail below.
Expand Down Expand Up @@ -287,6 +288,11 @@ Boto3 will attempt to load credentials from the Boto2 config file. It first chec
This credential provider is primarily for backwards compatibility purposes with Boto2.


Container credential provider
---------
If you are using Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS), you can obtain credentials by specifying an HTTP endpoint as an environment variable. The SDK will request credentials from the specified endpoint. For more information, see `Container credential provider <https://docs.aws.amazon.com/sdkref/latest/guide/feature-container-credentials.html>`_ in the Amazon SDKs and Tools Reference Guide.


IAM roles
---------

Expand Down
Loading