Closed leopoldogodines closed 2 years ago
Hello, can this PR be prioritised? Right now this issue is blocking not only customers on codebuild and fargate but every customer that use ECS and blocks instance metadata access from containers (as AWS suggests https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html#task-iam-role-considerations)
Thanks very much @leopoldogodines!
Some AWS services built on top of ECS such as codebuild and fargate will provide
AWS_CONTAINER_CREDENTIALS_RELATIVE_URI
env variable, that should be used with a different host to access the task credentials token, but the newInstanceMetaTokenProvider
was ignoring this. If that env variable is present, it will build the token URL using it instead.Fixes #869