Deploy a stack using STS tokens instead of fixed credentials to access aws resource
Opened this issue ยท 1 comments
jeduden commented
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.
rquitales commented
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.