AgentRegistryFullAccess
Summary
Provides full access to AWS Agent Registry.
Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.
Identity
- ARN
arn:aws:iam::aws:policy/AgentRegistryFullAccess- Default version
- v2
- Created
- Last edited
- Services
- agent-registry, bedrock-agentcore, iam, kms, secretsmanager
Control-plane actions (37)
By access level: 4 List, 1 Permissions management, 9 Read, 2 Tagging, 21 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| Agent Registry | All 19 actions (see the Agent Registry page) | 3 List, 4 Read, 2 Tagging, 10 Write; 19 restricted, 0 conditional | agent-registry:* |
| Bedrock-Agentcore | 6 of 197 | 3 Read, 3 Write; 6 restricted, 0 conditional | bedrock-agentcore:CreateWorkloadIdentity, bedrock-agentcore:DeleteWorkloadIdentity, bedrock-agentcore:GetResourceOauth2Token, bedrock-agentcore:GetWorkloadAccessToken, bedrock-agentcore:GetWorkloadIdentity, bedrock-agentcore:ListOauth2CredentialProviders |
| IAM | 3 of 190 | 1 List, 2 Write; 3 restricted, 2 conditional | iam:CreateServiceLinkedRole, iam:ListRoles, iam:PassRole |
| KMS | 8 of 58 | 1 Permissions management, 1 Read, 6 Write; 8 restricted, 8 conditional | kms:CreateGrant, kms:Decrypt, kms:DescribeKey, kms:Encrypt, kms:GenerateDataKey, kms:GenerateDataKeyWithoutPlaintext, kms:ReEncryptFrom, kms:ReEncryptTo |
| Secrets Manager | 1 of 27 | 1 Read; 1 restricted, 0 conditional | secretsmanager:GetSecretValue |
Bedrock-Agentcore: 6 actions
- bedrock-agentcore:CreateWorkloadIdentity (Write)
- bedrock-agentcore:DeleteWorkloadIdentity (Write)
- bedrock-agentcore:GetResourceOauth2Token (Read)
- bedrock-agentcore:GetWorkloadAccessToken (Write)
- bedrock-agentcore:GetWorkloadIdentity (Read)
- bedrock-agentcore:ListOauth2CredentialProviders (Read)
IAM: 3 actions
- iam:CreateServiceLinkedRole (Write)
- iam:ListRoles (List)
- iam:PassRole (Write)
KMS: 8 actions
- kms:CreateGrant (Permissions management)
- kms:Decrypt (Write)
- kms:DescribeKey (Read)
- kms:Encrypt (Write)
- kms:GenerateDataKey (Write)
- kms:GenerateDataKeyWithoutPlaintext (Write)
- kms:ReEncryptFrom (Write)
- kms:ReEncryptTo (Write)
Secrets Manager: 1 actions
- secretsmanager:GetSecretValue (Read)
Data-plane actions (3)
By access level: 1 List, 2 Read.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| Agent Registry | All 3 actions (see the Agent Registry page) | 1 List, 2 Read; 3 restricted, 0 conditional | agent-registry:* |
Excluded and conditional actions
No patterns are excluded by NotAction or Deny statements.
Resource scope and attachment
Resource scope across granted actions: scoped.
Can be attached: Yes, to users, groups and roles.
Why this tier
- Grants 24 write, tagging or permissions-management actions, short of full control of any service.
- Grants iam:PassRole, but only for scoped roles or under conditions (for example iam:PassedToService).
Guidance
Practical scope
Twelve statements. AgentRegistryFullAccess allows agent-registry:* on arn:aws:agent-registry:*:*:*. AgentRegistryPassRoleAccess allows iam:PassRole on all roles, only when passed to agent-registry.amazonaws.com. Statements for bedrock-agentcore allow four workload identity actions, bedrock-agentcore:GetResourceOauth2Token and bedrock-agentcore:ListOauth2CredentialProviders. IAMListAccess allows iam:ListRoles. Four statements allow kms actions on keys (kms:Decrypt, kms:DescribeKey, kms:Encrypt, kms:GenerateDataKey, kms:GenerateDataKeyWithoutPlaintext, kms:ReEncryptFrom, kms:ReEncryptTo and kms:CreateGrant) under via-service, called-via or encryption context conditions. AgentRegistrySecretsManagerAccess allows secretsmanager:GetSecretValue on arn:aws:secretsmanager:*:*:secret:*. AgentRegistryServiceLinkedRoleAccess allows iam:CreateServiceLinkedRole for agent-registry.amazonaws.com.
Use cases
- Give users or roles full access to AWS Agent Registry, including the related access the policy lists for it.
Best practices
- AWS managed policies don't grant least privilege permissions. The IAM User Guide suggests using IAM Access Analyzer to see which permissions principals actually use, then writing a custom policy or generating one with only the required permissions.
Security considerations
- secretsmanager:GetSecretValue is allowed on arn:aws:secretsmanager:*:*:secret:* with no condition, so a principal with this policy can read the value of any secret that matches that pattern, which is every secret ARN, not only secrets for AWS Agent Registry.
- iam:PassRole is allowed on every role (arn:aws:iam::*:role/*) but only to agent-registry.amazonaws.com. Passing a role to a service needs iam:PassRole. The IAM User Guide says that to pass a role to an AWS service, a user must have permission to pass the role to the service, which helps administrators ensure that only approved users can configure a service with a role that grants permissions.
- agent-registry:* is full access to that service's actions on all of its resources.
- You cannot change the permissions in an AWS managed policy. If AWS updates the policy, the update affects every user, group and role it is attached to.
Assignment guidance
You can attach this policy to your users, groups and roles. The reference page also links to guidance on creating a permission set using AWS managed policies in IAM Identity Center. It fits where full access to AWS Agent Registry is intended.
Related policies
Same service
- AgentRegistryReadOnlyAccess
- AmazonAppFlowFullAccess
- AmazonAuroraDSQLConsoleFullAccess
- AmazonAuroraDSQLFullAccess
- AmazonChimeSDKMessagingServiceRolePolicy
- AmazonDataZonePreviewConsoleFullAccess
- AmazonDocDBReadOnlyAccess
- AmazonEventBridgeApiDestinationsServiceRolePolicy
Same domain
Frequently asked questions
- When should I attach AgentRegistryFullAccess?
- The reference page says you can attach AgentRegistryFullAccess to your users, groups and roles, and describes it as full access to AWS Agent Registry. Attach it only for people who administer the registry.
- What does AgentRegistryFullAccess grant?
- It allows agent-registry:* on Agent Registry resources, passing any role to agent-registry.amazonaws.com, bedrock-agentcore workload identity and OAuth2 credential actions, conditioned kms actions, secretsmanager:GetSecretValue on all secrets, iam:ListRoles and creating the Agent Registry service-linked role.
- What are the security risks of AgentRegistryFullAccess?
- secretsmanager:GetSecretValue is unconditioned on all secrets, and iam:PassRole covers every role when passed to agent-registry.amazonaws.com. AWS managed policies don't grant least privilege permissions, and you must consider the security risk of granting principals more permissions than they need. AWS updates to the policy affect every identity it is attached to.
Policy JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AgentRegistryFullAccess",
"Effect": "Allow",
"Action": "agent-registry:*",
"Resource": "arn:aws:agent-registry:*:*:*"
},
{
"Sid": "AgentRegistryPassRoleAccess",
"Effect": "Allow",
"Action": "iam:PassRole",
"Resource": "arn:aws:iam::*:role/*",
"Condition": {
"StringEquals": {
"iam:PassedToService": "agent-registry.amazonaws.com"
}
}
},
{
"Sid": "AgentRegistryWorkloadIdentityAccess",
"Effect": "Allow",
"Action": [
"bedrock-agentcore:CreateWorkloadIdentity",
"bedrock-agentcore:DeleteWorkloadIdentity",
"bedrock-agentcore:GetWorkloadAccessToken",
"bedrock-agentcore:GetWorkloadIdentity"
],
"Resource": "arn:aws:bedrock-agentcore:*:*:workload-identity-directory/*"
},
{
"Sid": "AllowGetResourceOauth2TokenForOauthBasedSynchronization",
"Effect": "Allow",
"Action": [
"bedrock-agentcore:GetResourceOauth2Token"
],
"Resource": [
"arn:aws:bedrock-agentcore:*:*:credential-provider/*",
"arn:aws:bedrock-agentcore:*:*:workload-identity-directory/*",
"arn:aws:bedrock-agentcore:*:*:token-vault/*/oauth2credentialprovider/*"
]
},
{
"Sid": "AllowListOauth2CredentialsProvidersForConsolePicker",
"Effect": "Allow",
"Action": [
"bedrock-agentcore:ListOauth2CredentialProviders"
],
"Resource": "arn:aws:bedrock-agentcore:*:*:*"
},
{
"Sid": "IAMListAccess",
"Effect": "Allow",
"Action": [
"iam:ListRoles"
],
"Resource": "arn:aws:iam::*:role/*"
},
{
"Sid": "AgentRegistryKMSDecryptKeyForSynchronization",
"Effect": "Allow",
"Action": [
"kms:Decrypt"
],
"Resource": "arn:aws:kms:*:*:key/*",
"Condition": {
"ForAnyValue:StringEquals": {
"aws:CalledVia": "bedrock-agentcore.amazonaws.com"
}
}
},
{
"Sid": "AgentRegistryKMSDescribeKey",
"Effect": "Allow",
"Action": [
"kms:DescribeKey"
],
"Resource": "arn:aws:kms:*:*:key/*",
"Condition": {
"StringLike": {
"kms:ViaService": "agent-registry.*.amazonaws.com"
}
}
},
{
"Sid": "AgentRegistryKMSCryptoOps",
"Effect": "Allow",
"Action": [
"kms:Decrypt",
"kms:Encrypt",
"kms:GenerateDataKey",
"kms:GenerateDataKeyWithoutPlaintext",
"kms:ReEncryptFrom",
"kms:ReEncryptTo"
],
"Resource": "arn:aws:kms:*:*:key/*",
"Condition": {
"StringLike": {
"kms:ViaService": "agent-registry.*.amazonaws.com",
"kms:EncryptionContext:aws:agent-registry:registry-arn": "arn:aws:agent-registry:*:*:registry/*"
}
}
},
{
"Sid": "AgentRegistryKMSCreateGrant",
"Effect": "Allow",
"Action": "kms:CreateGrant",
"Resource": "arn:aws:kms:*:*:key/*",
"Condition": {
"StringLike": {
"kms:ViaService": "agent-registry.*.amazonaws.com"
},
"ForAllValues:StringEquals": {
"kms:GrantOperations": [
"Decrypt",
"Encrypt",
"GenerateDataKey",
"GenerateDataKeyWithoutPlaintext",
"ReEncryptFrom",
"ReEncryptTo",
"DescribeKey",
"CreateGrant"
]
},
"Null": {
"kms:GrantOperations": "false"
}
}
},
{
"Sid": "AgentRegistrySecretsManagerAccess",
"Effect": "Allow",
"Action": [
"secretsmanager:GetSecretValue"
],
"Resource": "arn:aws:secretsmanager:*:*:secret:*"
},
{
"Sid": "AgentRegistryServiceLinkedRoleAccess",
"Effect": "Allow",
"Action": "iam:CreateServiceLinkedRole",
"Resource": "arn:aws:iam::*:role/aws-service-role/agent-registry.amazonaws.com/AWSServiceRoleForAgentRegistry",
"Condition": {
"StringLike": {
"iam:AWSServiceName": "agent-registry.amazonaws.com"
}
}
}
]
}
Version history
Current version v2, edited by AWS on 2026-08-31. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.
Attach snippets
AWS CLI
aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AgentRegistryFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AgentRegistryFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AgentRegistryFullAccessCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AgentRegistryFullAccessTerraform
resource "aws_iam_role_policy_attachment" "agentregistryfullaccess" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/AgentRegistryFullAccess"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("AgentRegistryFullAccess"),
);Sources
- AgentRegistryFullAccess (AWS Managed Policy Reference Guide) (retrieved ; supports summary, practicalScope, useCases, securityConsiderations, assignmentGuidance, faqs)
- Grant a user permissions to pass a role to an AWS service (IAM User Guide) (retrieved ; supports securityConsiderations)
- Managed policies and inline policies (IAM User Guide) (retrieved ; supports securityConsiderations, faqs)
- AWS managed policies for job functions (IAM User Guide) (retrieved ; supports bestPractices, faqs)