Add Support for Container Credentials in AWS Federated Auth

Open
#18,996 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@chrisguitarguy is already working on this.

Since Nov 5, 2026.

  • #18997 by @chrisguitarguy — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, python

Research direction

Start by reviewing the linked pull request #18997 and the AWS container credentials documentation linked in the issue. The request is to support container credentials for federated authentication in ECS or EKS through an external credentials file or JSON, without extra configuration. Done means that flow works without a custom security credentials provider.

Written by the indexing model from the issue text.

Description

triage me type: feature request
Determine this is the right repository
  • I determined this is the correct repository in which to report this feature request.
Summary of the feature request

We use gcloud federated auth quite a bit and it works well in lambdas, but a lot of our workloads are in ECS where container credentials are used. https://docs.aws.amazon.com/sdkref/latest/guide/feature-container-credentials.html

It would be nice to have that supported out of the box.

Desired code experience

Just be able to use an external credentials file that points to aws and have it jsut work in containers, no additional configuration necessary or custom security credentials providers necessary.

Expected results

Again, having an AWS federated authentication just work in ECS or EKS (via a credentials file or JSON) without any extra configuration or custom security credentials providers.

API client name and version

No response

Use case

This would be helpful for folks using federated authentication in workloads running in ECS or EKS.

Additional context
Dominant language
Python
Stars
5.4k
Forks
1.8k
Avg merge
2d 7h
Merged PRs (30d)
173

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-cloud-python

All issues in googleapis/google-cloud-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.