From 2fc0d86a6d95c89e631e6a93c95414776d06f8cc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C4=81rti=C5=86=C5=A1=20Egl=C4=ABtis?= Date: Thu, 14 Nov 2024 10:43:47 +0200 Subject: [PATCH] Fix documentation about SDK's supporting AWS_CONTAINER_CREDENTIALS_FULL_URI As stated in https://docs.aws.amazon.com/sdkref/latest/guide/feature-container-credentials.html --- USAGE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/USAGE.md b/USAGE.md index 3219ad94..071dbbee 100644 --- a/USAGE.md +++ b/USAGE.md @@ -502,7 +502,7 @@ The ECS Credential provider binds to a random, ephemeral port and requires an au 2. Allows multiple providers simultaneously for discrete processes 3. Mitigates the security issues that accompany the EC2 Metadata Service because the address is not well-known and the authorization token is only exposed to the subprocess via environment variables -However, this will only work with the AWS SDKs [that support `AWS_CONTAINER_CREDENTIALS_FULL_URI`](https://docs.aws.amazon.com/sdkref/latest/guide/feature-container-credentials.html). The C++ and PHP SDKs do not currently support it. +However, this will only work with the AWS SDKs [that support `AWS_CONTAINER_CREDENTIALS_FULL_URI`](https://docs.aws.amazon.com/sdkref/latest/guide/feature-container-credentials.html). The ECS server also responds to requests on `/role-arn/YOUR_ROLE_ARN` with the role credentials, making it usable with `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` when combined with a reverse proxy (see the Docker section below).