AWS bedrock-agentcore documentation change
Summary
Formatting changes including heading style adjustments (changing 'Best practice' to 'Important', policy headings to bold), removing backticks from a permission statement, and updating an apostrophe character.
Security assessment
Changes are stylistic and formatting improvements. The removal of backticks from `bedrock-agentcore:*` does not alter the meaning of the IAM permission. The document already discusses IAM roles and KMS permissions for encrypted resources, but no new security content is added. No evidence of addressing a security vulnerability.
Diff
diff --git a/bedrock-agentcore/latest/devguide/memory-self-managed-strategies.md b/bedrock-agentcore/latest/devguide/memory-self-managed-strategies.md index 67077d904..ad68afebb 100644 --- a//bedrock-agentcore/latest/devguide/memory-self-managed-strategies.md +++ b//bedrock-agentcore/latest/devguide/memory-self-managed-strategies.md @@ -89 +89 @@ Create an S3 bucket in your account where Amazon Bedrock AgentCore will deliver -###### Best practice +###### Important @@ -101 +101 @@ Create an IAM role that Amazon Bedrock AgentCore can assume to access your resou -###### Trust policy +**Trust policy** @@ -119 +119 @@ Use the following trust policy: -###### Permissions policy +**Permissions policy** @@ -151 +151 @@ Use the following permissions policy: -###### Additional KMS permissions (if using encrypted resources) +**Additional KMS permissions (if using encrypted resources)** @@ -174 +174 @@ Your IAM user or role needs: - * `bedrock-agentcore:*` permissions + * bedrock-agentcore:* permissions @@ -377 +377 @@ Follow these best practices for performance, reliability, cost optimization, and - * **Trigger optimization** : Configure trigger conditions based on your use case requirements - balance between processing efficiency and memory freshness by considering your application's tolerance for latency versus processing costs. + * **Trigger optimization** : Configure trigger conditions based on your use case requirements - balance between processing efficiency and memory freshness by considering your application’s tolerance for latency versus processing costs.