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
Describe the bug
I'm using the standard config template:
[organization name]
role_arn = arn:aws:iam::XXXXXXXXXXXX:role/Role_Name
color = ffaaee
It loads into my key just fine.
When I select the role, the AWS Switch Role window displays.
I have checked the role name
I have checked the account number
I have checked for spaces
I'm testing now, I'm not in a customer environment.
I can see my role in my target account and the names match
If I manually fill in the fields for Account ID and IAM Role Name, I get this error
Invalid information in one or more fields
Check your information or contact your administrator.
Expected behavior
I am expecting to Launch directly into the AWS account and not have to enter the information.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Browser Chrome and Edge
Windows 10 Enterprise
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm using the standard config template:
[organization name]
role_arn = arn:aws:iam::XXXXXXXXXXXX:role/Role_Name
color = ffaaee
It loads into my key just fine.
When I select the role, the AWS Switch Role window displays.
I have checked the role name
I have checked the account number
I have checked for spaces
I'm testing now, I'm not in a customer environment.
I can see my role in my target account and the names match
If I manually fill in the fields for Account ID and IAM Role Name, I get this error
Invalid information in one or more fields
Check your information or contact your administrator.
Expected behavior
I am expecting to Launch directly into the AWS account and not have to enter the information.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Additional context
The text was updated successfully, but these errors were encountered: