AWS bedrock-agentcore documentation change
Summary
Removed preview disclaimer and adjusted formatting (colons to dashes in example scenarios)
Security assessment
Formatting changes and disclaimer removal do not alter security documentation. Existing OAuth 2.0 security context remains unchanged.
Diff
diff --git a/bedrock-agentcore/latest/devguide/common-use-cases.md b/bedrock-agentcore/latest/devguide/common-use-cases.md index 9c3e0592e..0e7f3ac8b 100644 --- a//bedrock-agentcore/latest/devguide/common-use-cases.md +++ b//bedrock-agentcore/latest/devguide/common-use-cases.md @@ -7,2 +6,0 @@ User-delegated accessMachine-to-machine authChoosing the right authentication pa -Amazon Bedrock AgentCore is in preview release and is subject to change. - @@ -30 +28 @@ The OAuth 2.0 authorization code grant flow enables agents to access user-specif -**Key characteristics:** +**Key characteristics** @@ -43 +41 @@ The OAuth 2.0 authorization code grant flow enables agents to access user-specif -**Example scenario:** A productivity agent needs to access a user's Google Calendar to schedule meetings, their Gmail to send emails, and their Google Drive to store documents. The agent uses the OAuth 2.0 authorization code grant to obtain user consent for each service, with specific scopes that limit access to only the necessary data. The user explicitly authorizes the agent through Google's consent screen, and AgentCore Identity securely stores the resulting credentials for future use. +**Example scenario** – A productivity agent needs to access a user's Google Calendar to schedule meetings, their Gmail to send emails, and their Google Drive to store documents. The agent uses the OAuth 2.0 authorization code grant to obtain user consent for each service, with specific scopes that limit access to only the necessary data. The user explicitly authorizes the agent through Google's consent screen, and AgentCore Identity securely stores the resulting credentials for future use. @@ -51 +49 @@ The OAuth 2.0 client credentials grant flow enables direct authentication betwee -**Key characteristics:** +**Key characteristics** @@ -64 +62 @@ The OAuth 2.0 client credentials grant flow enables direct authentication betwee -**Example scenario:** An enterprise data processing agent needs to collect data from multiple internal systems, process it, and store the results in a data warehouse. The agent uses the OAuth 2.0 client credentials grant to authenticate directly with each system using its own identity and pre-configured permissions. No user interaction is required, and the agent can operate when agents act themselves with pre-authorized user consent on scheduled intervals. +**Example scenario** – An enterprise data processing agent needs to collect data from multiple internal systems, process it, and store the results in a data warehouse. The agent uses the OAuth 2.0 client credentials grant to authenticate directly with each system using its own identity and pre-configured permissions. No user interaction is required, and the agent can operate when agents act themselves with pre-authorized user consent on scheduled intervals.