This article addresses an issue where AWS IAM Roles from connected AWS accounts display the account's ID instead of the account's name (alias) within Okta. This occurs when attempting to add a new connected AWS account.
- Lifecycle Management
- Amazon Web Services (AWS)
The root cause of this issue is that an alias has not been created for the AWS account. Without an alias, Okta defaults to displaying the unique AWS account ID.
To resolve this issue, an alias must be created for the AWS account.
- Follow the instructions provided in the AWS documentation to create an account alias: Create, remove, and list AWS account aliases.
- Once the alias is created, return to Okta and refresh the connection to the AWS account. The account name will now appear instead of the account ID.
