AWS bedrock-agentcore documentation change
Summary
Formatting changes including code example reorganization, table formatting, and minor text adjustments.
Security assessment
Changes are purely formatting and do not address any security vulnerability or weakness. The content is about using custom root CA certificates, which is a security feature, but the changes are presentational.
Diff
diff --git a/bedrock-agentcore/latest/devguide/browser-root-ca-certificates.md b/bedrock-agentcore/latest/devguide/browser-root-ca-certificates.md index 4aba5d33c..e20897e6b 100644 --- a//bedrock-agentcore/latest/devguide/browser-root-ca-certificates.md +++ b//bedrock-agentcore/latest/devguide/browser-root-ca-certificates.md @@ -11 +11 @@ By default, Amazon Bedrock AgentCore Browser sessions trust only publicly recogn -Amazon Bedrock AgentCore retrieves the PEM-encoded certificate content from AWS Secrets Manager using your caller credentials, validates the X.509 format and expiry, and installs the certificates into the session's OS trust store. This enables the browser to establish trusted HTTPS connections to your internal resources. +Amazon Bedrock AgentCore retrieves the PEM-encoded certificate content from AWS Secrets Manager using your caller credentials, validates the X.509 format and expiry, and installs the certificates into the session’s OS trust store. This enables the browser to establish trusted HTTPS connections to your internal resources. @@ -23 +23 @@ Root Certificate Authority for Amazon Bedrock AgentCore Browser works as follows - 4. Valid certificates are deployed to the session's OS trust store, making them available to the browser and any network clients within the sandbox. + 4. Valid certificates are deployed to the session’s OS trust store, making them available to the browser and any network clients within the sandbox. @@ -65 +65 @@ Before you can use a root CA certificate with Amazon Bedrock AgentCore Browser, -AWS CLI +###### Example @@ -66,0 +67 @@ AWS CLI +AWS CLI @@ -69 +70 @@ AWS CLI - aws secretsmanager create-secret \ + 1. aws secretsmanager create-secret \ @@ -75 +75,0 @@ AWS CLI -Boto3 @@ -79 +79,4 @@ Boto3 - import boto3 +Boto3 + + + 1. import boto3 @@ -105 +111 @@ To start a browser session that trusts your custom root CA certificates, include -AWS CLI +###### Example @@ -106,0 +113 @@ AWS CLI +AWS CLI @@ -109 +116 @@ AWS CLI - aws bedrock-agentcore start-browser-session \ + 1. aws bedrock-agentcore start-browser-session \ @@ -122 +128,0 @@ AWS CLI -Boto3 @@ -126 +132,4 @@ Boto3 - import boto3 +Boto3 + + + 1. import boto3 @@ -147 +155,0 @@ Boto3 -API @@ -151 +159,4 @@ API - { +API + + + 1. { @@ -168 +182 @@ You can provide multiple root CA certificates in a single browser session. This -AWS CLI +###### Example @@ -169,0 +184 @@ AWS CLI +AWS CLI @@ -172 +187 @@ AWS CLI - aws bedrock-agentcore start-browser-session \ + 1. aws bedrock-agentcore start-browser-session \ @@ -192 +206,0 @@ AWS CLI -Boto3 @@ -196 +210,4 @@ Boto3 - response = client.start_browser_session( +Boto3 + + + 1. response = client.start_browser_session( @@ -223 +243 @@ This is useful for organization-wide certificates that should be trusted by all -Boto3 +###### Example @@ -224,0 +245 @@ Boto3 +Boto3 @@ -227 +248 @@ Boto3 - response = client.create_browser( + 1. response = client.create_browser( @@ -250 +274 @@ Certificates must meet the following requirements: -Certificate requirements Requirement | Details +Requirement | Details @@ -256 +280 @@ Maximum certificates per session | 10 per session and 10 per tool. A session can -Secret ARN format | `arn:aws:secretsmanager:`region`:`account-id`:secret:`secret-name`` +Secret ARN format | `arn:aws:secretsmanager:region:account-id:secret:secret-name` @@ -267 +291 @@ Browser Enterprise Policies -Troubleshoot AgentCore Browser +Browser OS action