AWS bedrock-agentcore documentation change
Summary
Reorganized content sections, moved AWS CLI examples to appropriate sections, added tag management documentation, and updated section titles from 'Security' to 'Versioning and endpoints' and 'Environment and Skills' to 'Environment and filesystem'.
Security assessment
The change adds documentation about using tags for access control ('Apply tags to your harness for cost allocation and access control'), which is a security feature. However, there's no evidence this addresses a specific security vulnerability. The other changes are structural/organizational improvements without security implications.
Diff
diff --git a/bedrock-agentcore/latest/devguide/harness-operations.md b/bedrock-agentcore/latest/devguide/harness-operations.md index c1c3f3c32..a1e70aabf 100644 --- a//bedrock-agentcore/latest/devguide/harness-operations.md +++ b//bedrock-agentcore/latest/devguide/harness-operations.md @@ -18,0 +19,7 @@ Every harness invocation automatically generates traces, logs, and metrics throu +AWS CLI/boto3 + + +Traces, logs, and metrics flow to CloudWatch through the harness execution role. View them in the [AgentCore Observability dashboard](https://us-west-2.console.aws.amazon.com/cloudwatch/home?region=us-west-2#/gen-ai-observability/agent-core/agents), or query programmatically through the CloudWatch Logs and X-Ray APIs. + +Before you see traces, [enable Transaction Search in CloudWatch](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Enable-Lambda-TransactionSearch.html) (one-time per account). See [AgentCore Observability getting started](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-get-started.html) for setup details. + @@ -35,7 +41,0 @@ AgentCore CLI -AWS CLI/boto3 - - -Traces, logs, and metrics flow to CloudWatch through the harness execution role. View them in the [AgentCore Observability dashboard](https://us-west-2.console.aws.amazon.com/cloudwatch/home?region=us-west-2#/gen-ai-observability/agent-core/agents), or query programmatically through the CloudWatch Logs and X-Ray APIs. - -Before you see traces, [enable Transaction Search in CloudWatch](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Enable-Lambda-TransactionSearch.html) (one-time per account). See [AgentCore Observability getting started](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-get-started.html) for setup details. - @@ -81,0 +82,12 @@ All limits are optional; omit them to use service defaults. Because harness is b +AWS CLI/boto3 + + + + aws bedrock-agentcore-control update-harness \ + --harness-id "MyHarness-UuFdkQoXSL" \ + --max-iterations 50 \ + --timeout-seconds 1800 \ + --max-tokens 8192 + +Or override on a single invocation by passing `maxIterations`, `timeoutSeconds`, or `maxTokens` in `invoke_harness`. + @@ -102,2 +114 @@ Override on a single call: -AWS CLI/boto3 - +## Tags @@ -104,0 +116 @@ AWS CLI/boto3 +Apply tags to your harness for cost allocation and access control. @@ -106,5 +118 @@ AWS CLI/boto3 - aws bedrock-agentcore-control update-harness \ - --harness-id "MyHarness-UuFdkQoXSL" \ - --max-iterations 50 \ - --timeout-seconds 1800 \ - --max-tokens 8192 +###### Example @@ -112 +120 @@ AWS CLI/boto3 -Or override on a single invocation by passing `maxIterations`, `timeoutSeconds`, or `maxTokens` in `invoke_harness`. +AWS CLI/boto3 @@ -114 +121,0 @@ Or override on a single invocation by passing `maxIterations`, `timeoutSeconds`, -## Tags @@ -116 +122,0 @@ Or override on a single invocation by passing `maxIterations`, `timeoutSeconds`, -Apply tags to your harness for cost allocation and access control. @@ -118 +124,4 @@ Apply tags to your harness for cost allocation and access control. -###### Example + aws bedrock-agentcore-control create-harness \ + --harness-name "MyHarness" \ + --execution-role-arn "arn:aws:iam::123456789012:role/MyHarnessRole" \ + --tags '{"team": "platform", "environment": "staging"}' @@ -135,9 +143,0 @@ Run `agentcore deploy` to apply. -AWS CLI/boto3 - - - - aws bedrock-agentcore-control create-harness \ - --harness-name "MyHarness" \ - --execution-role-arn "arn:aws:iam::123456789012:role/MyHarnessRole" \ - --tags '{"team": "platform", "environment": "staging"}' - @@ -148 +148 @@ Tags flow through to deployed CloudFormation resources. - * [Persist memory and filesystem](./harness-memory.html) \- memory persists conversation context across sessions + * [Memory](./harness-memory.html) \- memory persists conversation context across sessions @@ -150 +150 @@ Tags flow through to deployed CloudFormation resources. - * [Environment and Skills](./harness-environment.html) \- environment variables and custom containers + * [Environment and filesystem](./harness-environment.html) \- environment variables and custom containers @@ -165 +165 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Environment and Skills +Environment and filesystem @@ -167 +167 @@ Environment and Skills -Security +Versioning and endpoints