AWS bedrock-agentcore documentation change
Summary
Removed references to 'Amazon Bedrock AgentCore Gateway Authorizer' and deleted section about OAuth authorizer requirements
Security assessment
Removal of OAuth authorizer documentation does not directly address a security issue but may reduce clarity on security practices. However, there is no explicit evidence of a security vulnerability being remediated.
Diff
diff --git a/bedrock-agentcore/latest/devguide/policy-core-concepts.md b/bedrock-agentcore/latest/devguide/policy-core-concepts.md index d77cd33e7..5359b4c3a 100644 --- a//bedrock-agentcore/latest/devguide/policy-core-concepts.md +++ b//bedrock-agentcore/latest/devguide/policy-core-concepts.md @@ -5 +5 @@ -GatewayGateway TargetAmazon Bedrock AgentCore Gateway AuthorizerCedarCedar PolicyPolicy engineCedar SchemaCedar validationCedar analysisPolicy authoring service +GatewayGateway TargetCedarCedar PolicyPolicy engineCedar SchemaCedar validationCedar analysisPolicy authoring service @@ -17,2 +16,0 @@ Before using Policy in Amazon Bedrock AgentCore, it's important to understand th - * Amazon Bedrock AgentCore Gateway Authorizer - @@ -44,4 +41,0 @@ A target defines the APIs or Lambda function that a Gateway will provide as tool -## Amazon Bedrock AgentCore Gateway Authorizer - -Since MCP only supports OAuth, each Gateway must have an attached OAuth authorizer. If you don't have an OAuth authorization server already, you will be able to create one in this guide using Cognito. -