AWS bedrock-agentcore documentation change
Summary
Formatting changes including punctuation updates (straight to curly apostrophes), removal of JSON example formatting markers, and minor link formatting adjustments for confused deputy prevention documentation.
Security assessment
These are purely formatting and typographical changes. The security content about preventing confused deputy attacks using aws:SourceArn and aws:SourceAccount remains substantively unchanged. No new security vulnerabilities, incidents, or security features are introduced.
Diff
diff --git a/bedrock-agentcore/latest/devguide/cross-service-confused-deputy-prevention.md b/bedrock-agentcore/latest/devguide/cross-service-confused-deputy-prevention.md index 0671ad04d..4dd159675 100644 --- a//bedrock-agentcore/latest/devguide/cross-service-confused-deputy-prevention.md +++ b//bedrock-agentcore/latest/devguide/cross-service-confused-deputy-prevention.md @@ -7 +7 @@ -The confused deputy problem is a security issue where an entity that doesn't have permission to perform an action can coerce a more-privileged entity to perform the action. In AWS, cross-service impersonation can result in the confused deputy problem. Cross-service impersonation can occur when one service (the _calling service_) calls another service (the _called service_). The calling service can be manipulated to use its permissions to act on another customer's resources in a way it should not otherwise have permission to access. To prevent this, AWS provides tools that help you protect your data for all services with service principals that have been given access to resources in your account. +The confused deputy problem is a security issue where an entity that doesn’t have permission to perform an action can coerce a more-privileged entity to perform the action. In AWS, cross-service impersonation can result in the confused deputy problem. Cross-service impersonation can occur when one service (the _calling service_ ) calls another service (the _called service_ ). The calling service can be manipulated to use its permissions to act on another customer’s resources in a way it should not otherwise have permission to access. To prevent this, AWS provides tools that help you protect your data for all services with service principals that have been given access to resources in your account. @@ -9 +9 @@ The confused deputy problem is a security issue where an entity that doesn't hav -We recommend using the [`aws:SourceArn`](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourcearn) and [`aws:SourceAccount`](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourceaccount) global condition context keys in resource policies to limit the permissions that Amazon Bedrock AgentCore gives another service to the resource. Use `aws:SourceArn` if you want only one resource to be associated with the cross-service access. Use `aws:SourceAccount` if you want to allow any resource in that account to be associated with the cross-service use. +We recommend using the [aws:SourceArn](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourcearn) and [aws:SourceAccount](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourceaccount) global condition context keys in resource policies to limit the permissions that Amazon Bedrock AgentCore gives another service to the resource. Use `aws:SourceArn` if you want only one resource to be associated with the cross-service access. Use `aws:SourceAccount` if you want to allow any resource in that account to be associated with the cross-service use. @@ -11 +11 @@ We recommend using the [`aws:SourceArn`](https://docs.aws.amazon.com/IAM/latest/ -The most effective way to protect against the confused deputy problem is to use the `aws:SourceArn` global condition context key with the full ARN of the resource. If you don't know the full ARN of the resource or if you are specifying multiple resources, use the `aws:SourceArn` global context condition key with wildcard characters (`*`) for the unknown portions of the ARN. For example, `arn:aws:`servicename`:*:`123456789012`:*`. +The most effective way to protect against the confused deputy problem is to use the `aws:SourceArn` global condition context key with the full ARN of the resource. If you don’t know the full ARN of the resource or if you are specifying multiple resources, use the `aws:SourceArn` global context condition key with wildcard characters ( * ) for the unknown portions of the ARN. For example, arn:aws:servicename:*:123456789012:*. @@ -17,6 +16,0 @@ The following example shows how you can use the `aws:SourceArn` and `aws:SourceA -JSON - - -**** - -