Connecting AWS (IAM and Bedrock AgentCore)
The AWS connector reads IAM roles, users, groups, and policies, plus the Bedrock AgentCore inventory (runtimes, gateways, identities, memories, tools, harnesses, and registries). It performs read operations only, with one exception: it generates a read-only IAM credential report to enrich access-key age, last-used, and MFA data. It does not read credential secrets, Bedrock memory contents, or Bedrock events, and it never creates, modifies, or deletes AWS resources.
RSA Agent ID combines this connector with other data sources to build device- and process-level visibility; it is not an authoritative agent registry on its own.
Before you begin
Ensure you have the following:
- An AWS user with IAM write access in the target account, to create the connector's IAM user and policy
- The target AWS account's 12-digit account ID
Ask RSA to enable the AWS regions this connector should scan. Region enablement happens on the Agent ID server, not in the connector form.
Required AWS Permissions
Attach a customer-managed policy to a dedicated IAM user (the connector authenticates with a static access key; it does not assume a role):
| Permission | Purpose |
|---|---|
| iam:GetAccountAuthorizationDetails | Required. Reads roles, users, groups, and managed/inline policies; the scan fails without it. |
| iam:GenerateCredentialReport / iam:GetCredentialReport | Recommended. Enables access-key age, last-used, password, and MFA enrichment. |
| bedrock-agentcore:List* / bedrock-agentcore:Get* | Required for Bedrock AgentCore discovery. |
| sts:GetCallerIdentity | Used for proving the keys and needs no explicit grant. A broader AWS-managed policy such as IAMReadOnlyAccess also satisfies the IAM half, but grants more than the connector uses. |
AWS-side Setup
Procedure
Sign in to the AWS Console and open IAM > Users.
Click Create user and enter a recognizable name, such as agent-discovery-readonly. Leave Provide user access to the AWS Management Console unchecked.
Create a customer-managed policy with the below JSON containing the IAM and Bedrock AgentCore permissions listed above, and attach it to the new user.
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "IamRead",
"Effect": "Allow",
"Action": [
"iam:GetAccountAuthorizationDetails",
"iam:GenerateCredentialReport",
"iam:GetCredentialReport"
],
"Resource": "*"
},
{
"Sid": "BedrockAgentCoreRead",
"Effect": "Allow",
"Action": [
"bedrock-agentcore:List*",
"bedrock-agentcore:Get*"
],
"Resource": "*"
}
]
}Open the user, go to Security credentials, and click Create access key.
Choose Application running outside AWS and confirm.
Copy the Access key ID and Secret access key.
Note: The secret is shown only once. After you leave the page, it cannot be recovered, and you need to create a new key. Store it securely.
Agent ID Setup
Procedure
On the Connectors page, click Add source, then click Connect on the AWS IAM card.
Enter a Connection name and the 12-digit Account ID.
Enter the Access key ID and Secret access key you copied.
Choose a Scan frequency.
Click Test connection, confirm it succeeds, then click Save and start discovery.
Note: Test Connection validates the keys and runs one IAM read and (if Bedrock regions are enabled) one Bedrock read. It does not check credential-report permissions or verify the Account ID. An incorrect Account ID can still pass the test and will mis-attribute discovered data, so double-check it.
Troubleshooting
Test Connection fails.
Recheck the access key pair, or create a new key if the old one was deleted/deactivated.
Status showsLimited Access, IAM read missing.
Attach iam:GetAccountAuthorizationDetails and retest.
Status showsLimited Access, Bedrock read missing.
Add the bedrock-agentcore:List*/Get* actions.
No Bedrock agents appear.
Confirm RSA has enabled the required regions and that Bedrock is enabled on the account.
Access-key age/MFA columns are blank.
Add the credential-report permissions and rescan.
Data attributed to the wrong account.
Account ID does not match the keys' account. Correct the Account ID on the connector.
Connector worked, then stopped.
Access key is rotated or disabled. Create a new access key and update the connector.
Related Articles
RSA Agent ID Installation, Deployment, and Administration Guide 5Number of Views AWS IAM Identity Center - Session Tags Configuration - RSA Ready Implementation Guide 3Number of Views AWS IAM Identity Center - SAML Relying Party Configuration - RSA Ready Implementation Guide 15Number of Views AWS IAM Identity Center - SAML My Page SSO Configuration - RSA Ready Implementation Guide 21Number of Views AWS IAM Identity Center CloudWatch - RSA Ready Implementation Guide 34Number of Views