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
This ticket, has the steps to set the ENV for /grant-aws-access discord command, this command grants AWS access of mentioned groupId to the user, so for granting this access programatically we needed the access keys, secret keys with permission to add user to the AWS account and add them to the mentioned group.
They are basically 4 ENVs
AWS_REGION
AWS_ACCESS_KEY
AWS_SECRET_KEY
IDENTITY_STORE_ID
Steps to fetch the first 3 variables
In order to create a access and secret key with required permissions
To set the identity store Id
a. click on the IAM Identity center and click on settings
b. Scroll down and we can find the identity store Id
Note : Important step
We need to check the AWS group is linked to an AWS account if not the users, will see a blank screen like this
- To assign an AWS account to the group, we can go to **IAM Identity center** > Groups
- Selecting the group whose Group Id we have set in the discord slash commands, click on the **AWS Accounts** tab
and assign to an AWS account, the user will see this like screen post assigning group to the AWS account.
This ticket, has the steps to set the ENV for
/grant-aws-access
discord command, this command grants AWS access of mentioned groupId to the user, so for granting this access programatically we needed the access keys, secret keys with permission to add user to the AWS account and add them to the mentioned group.They are basically 4 ENVs
Steps to fetch the first 3 variables
We can either check this document https://k21academy.com/amazon-web-services/create-access-and-secret-keys-in-aws/
a. On top right corner select security credentials
b. select create access keys
c. Setting these access and secret keys in the ENV variables in github
a. click on the IAM Identity center and click on settings
cc : @prakashchoudhary07
The text was updated successfully, but these errors were encountered: