AWS bedrock-agentcore documentation change
Summary
Updated auth terminology to authorization in workflow steps
Security assessment
Consistently changes 'Auth' to 'Authorization' in security context descriptions. Reinforces existing security patterns but doesn't introduce new security features or address vulnerabilities.
Diff
diff --git a/bedrock-agentcore/latest/devguide/gateway-building.md b/bedrock-agentcore/latest/devguide/gateway-building.md index 5e1db8b6a..bf7adf8ac 100644 --- a//bedrock-agentcore/latest/devguide/gateway-building.md +++ b//bedrock-agentcore/latest/devguide/gateway-building.md @@ -19 +19 @@ The Gateway workflow involves the following steps to connect your agents to exte - 2. **Create a Gateway endpoint** \- Use the AWS console or AWS SDK to create the gateway that will serve as the MCP entry point. Each API endpoint or function will become an MCP-compatible tool, and will be made available through your MCP server URL. To secure the gateway, you can use Inbound Auth to control the ingress to the gateway. + 2. **Create a Gateway endpoint** \- Use the AWS console or AWS SDK to create the gateway that will serve as the MCP entry point. Each API endpoint or function will become an MCP-compatible tool, and will be made available through your MCP server URL. To secure the gateway, you can use inbound authorization to control the ingress to the gateway. @@ -21 +21 @@ The Gateway workflow involves the following steps to connect your agents to exte - 3. **Add targets to your Gateway** \- Configure targets that define how the gateway routes requests to specific tools. To securely connect to backend resources on behalf of authenticated users, use Outbound Auth. Together, Inbound and Outbound Auth create a secure bridge between users and their target resources, supporting both IAM credentials and OAuth-based authentication flows. + 3. **Add targets to your Gateway** \- Configure targets that define how the gateway routes requests to specific tools. To securely connect to backend resources on behalf of authenticated users, use Outbound Authorization. Together, Inbound and Outbound Authorization create a secure bridge between users and their target resources, supporting both IAM credentials and OAuth-based authentication flows.