AWS bedrock-agentcore documentation change
Summary
Updated terminology from 'Outbound Auth' to 'Outbound Authorization' in headings and content
Security assessment
The change clarifies authorization terminology, which relates to security configurations but does not address a specific vulnerability. It improves documentation accuracy for security-related permissions.
Diff
diff --git a/bedrock-agentcore/latest/devguide/gateway-prerequisites-permissions.md b/bedrock-agentcore/latest/devguide/gateway-prerequisites-permissions.md index ae5c958c4..0738a7bdc 100644 --- a//bedrock-agentcore/latest/devguide/gateway-prerequisites-permissions.md +++ b//bedrock-agentcore/latest/devguide/gateway-prerequisites-permissions.md @@ -5 +5 @@ -Gateway Management PermissionsGateway Access Permissions or Inbound Auth ConfigurationGateway Execution Permissions or Outbound Auth configurationBest practices for Gateway permissions +Gateway Management PermissionsGateway Access Permissions or Inbound Auth ConfigurationGateway Execution Permissions or Outbound Authorization configurationBest practices for Gateway permissions @@ -19 +19 @@ When working with Gateways, there are three main categories of permissions to co - 3. Gateway Execution Permissions or Outbound Auth configuration \- Permissions that a Gateway needs to perform actions on other resources and services + 3. Gateway Execution Permissions or Outbound Authorization configuration \- Permissions that a Gateway needs to perform actions on other resources and services @@ -102 +102 @@ You'll configure these permissions when [Creating gateways](./create-gateway.htm -## Gateway Execution Permissions or Outbound Auth configuration +## Gateway Execution Permissions or Outbound Authorization configuration @@ -104 +104 @@ You'll configure these permissions when [Creating gateways](./create-gateway.htm -When creating a Gateway, you need to provide an execution role that will be used by the Gateway to access AWS resources or external services. This role defines the permissions that the Gateway has when making requests to other services. Based on the type of target, the role would either have permissions to access the AWS resources configured for the target, or for external resources, the role would have permissions to acquire the needed auth to invoke the external resources. You will configure these after you have setup your gateway while [Adding targets](./gateway-building-adding-targets.html). +When creating a Gateway, you need to provide an execution role that will be used by the Gateway to access AWS resources or external services. This role defines the permissions that the Gateway has when making requests to other services. Based on the type of target, the role would either have permissions to access the AWS resources configured for the target, or for external resources, the role would have permissions to acquire the needed authorization to invoke the external resources. You will configure these after you have setup your gateway while [Adding targets](./gateway-building-adding-targets.html).