You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current State
Today when you register the AWS provider, it AWS Access Key ID and the AWS Secret Access Key of IAM role. This is how UCP connects to AWS in order to deploy Azure resources.
Desired State
We should also support IAM roles for service accounts which is the equivalent of workload identity for AWS
👋 @Reshrahim Thanks for filing this feature request.
A project maintainer will review this feature request and get back to you soon.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
# Description
Add model changes for supporting AWS IRSA credential
## Type of change
- This pull request adds or changes features of Radius and has an
approved issue (issue link required).
#7618
#
Partially Fixes: #7618
---------
Signed-off-by: nithyatsu <nithyasu@microsoft.com>
Overview of feature request
Current State
Today when you register the AWS provider, it AWS Access Key ID and the AWS Secret Access Key of IAM role. This is how UCP connects to AWS in order to deploy Azure resources.
Desired State
We should also support IAM roles for service accounts which is the equivalent of workload identity for AWS
Acceptance criteria
Additional context
No response
Would you like to support us?
AB#12397
The text was updated successfully, but these errors were encountered: