From 3a23c63fcd8c2c414009871d8b4f2f2170dfb501 Mon Sep 17 00:00:00 2001 From: Nick Shadrin Date: Thu, 16 Oct 2025 12:41:47 -0500 Subject: [PATCH] Fix spelling of 'Uri' to 'URI' in documentation. Corrected the spelling of 'Uri' to 'URI' for consistency. (cherry picked from commit 8cac33f3667792d14158ce5e030ce6d5e29eb69d) Co-authored-by: Elijah Zupancic --- docs/getting_started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting_started.md b/docs/getting_started.md index 8b7aa7d..60b4252 100644 --- a/docs/getting_started.md +++ b/docs/getting_started.md @@ -464,7 +464,7 @@ An alternative way to use the container image on an EKS cluster is to use a serv - Configuring a [Kubernetes service account to assume an IAM role with EKS Pod Identity](https://docs.aws.amazon.com/eks/latest/userguide/pod-id-association.html) - [Configure your pods, Deployments, etc to use the Service Account](https://docs.aws.amazon.com/eks/latest/userguide/pod-configuration.html) - As soon as the pods/deployments are updated, you will see the couple of Env Variables listed below in the pods. - - `AWS_CONTAINER_CREDENTIALS_FULL_URI` - Contains the Uri of the EKS Pod Identity Agent that will provide the credentials + - `AWS_CONTAINER_CREDENTIALS_FULL_URI` - Contains the URI of the EKS Pod Identity Agent that will provide the credentials - `AWS_CONTAINER_AUTHORIZATION_TOKEN_FILE` - Contains the token which will be used to create temporary credentials using the EKS Pod Identity Agent. The minimal set of resources to deploy is the same than for [Running on EKS with IAM roles for service accounts](#running-on-eks-with-iam-roles-for-service-accounts), except there is no need to annotate the service account: