AWS bedrock-agentcore documentation change
Summary
Added documentation about principal types (OAuthUser and IamEntity) to core concepts, explaining how different authentication methods map to Cedar policy principals
Security assessment
This change adds foundational security documentation about principal types in the authorization system, explaining how OAuth and IAM authentication map to different Cedar principal types. It enhances understanding of the security model but does not address any specific security vulnerability or incident. The documentation helps users properly implement authentication and authorization controls.
Diff
diff --git a/bedrock-agentcore/latest/devguide/policy-core-concepts.md b/bedrock-agentcore/latest/devguide/policy-core-concepts.md index 5359b4c3a..ca74b1dff 100644 --- a//bedrock-agentcore/latest/devguide/policy-core-concepts.md +++ b//bedrock-agentcore/latest/devguide/policy-core-concepts.md @@ -5 +5 @@ -GatewayGateway TargetCedarCedar PolicyPolicy engineCedar SchemaCedar validationCedar analysisPolicy authoring service +GatewayGateway TargetPrincipal typesCedarCedar PolicyPolicy engineCedar SchemaCedar validationCedar analysisPolicy authoring service @@ -16,0 +17,2 @@ Before using Policy in Amazon Bedrock AgentCore, it's important to understand th + * Principal types + @@ -41,0 +44,11 @@ A target defines the APIs or Lambda function that a Gateway will provide as tool +## Principal types + +Cedar policies use principals to represent the entity making an authorization request. Policy in AgentCore supports two principal types depending on how your AgentCore Gateway is configured for authentication: + + * **AgentCore::OAuthUser** \- Represents OAuth-authenticated users. When a AgentCore Gateway uses OAuth authorization, the principal is created from the JWT token's `sub` claim. OAuth principals support tags that contain JWT claims such as username, scope, role, etc. + + * **AgentCore::IamEntity** \- Represents IAM-authenticated callers. When a AgentCore Gateway uses AWS_IAM authorization, the principal is created from the caller's IAM ARN. IAM principals have an `id` attribute containing the full IAM ARN, which can be used for account-based or role-based access control. + + + +