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

Deploy a stack using STS tokens instead of fixed credentials to access aws resource #591

Open
jeduden opened this issue Jun 11, 2024 · 1 comment
Labels
area/authentication kind/enhancement Improvements or new features

Comments

@jeduden
Copy link

jeduden commented Jun 11, 2024

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Currently, it seems the operator is not supporting a process that using STS tokens to access aws resource.
Like for example described in this article about using a google cloud platform access aws resources

Affected area/feature

simplest resolution would be to add a new configuration to configure the required "assume-role-with-web-identity" call and then use the produced aws credentials for the remainder of the pulumi stack deployment.

@jeduden jeduden added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Jun 11, 2024
@rquitales
Copy link
Contributor

Thanks for reporting this enhancement request and will be adding this to our backlog. I agree that we might want to improve our overall authorization user journeys within this operator.

@rquitales rquitales added area/authentication and removed needs-triage Needs attention from the triage team labels Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/authentication kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

2 participants