AWS Security ChangesHomeSearch

AWS cli high security documentation change

Service: cli · 2026-05-16 · Security-related high

File: cli/latest/reference/bedrock-agentcore-control/get-harness.md

Summary

Added TOKEN_EXCHANGE authorization method and requireServiceS3Endpoint field documentation for VPC network isolation changes

Security assessment

The change documents a new authorization method (TOKEN_EXCHANGE) and significant network security changes for VPC isolation. Specifically, it details how starting May 2026, new agent runtimes will have stricter network isolation without service-managed S3 gateways, requiring customers to manage S3 access through their VPC. This addresses potential security risks from unintended S3 access vectors.

Diff

diff --git a/cli/latest/reference/bedrock-agentcore-control/get-harness.md b/cli/latest/reference/bedrock-agentcore-control/get-harness.md
index 4d5396ed4..24c547027 100644
--- a//cli/latest/reference/bedrock-agentcore-control/get-harness.md
+++ b//cli/latest/reference/bedrock-agentcore-control/get-harness.md
@@ -15 +15 @@
-  * [AWS CLI 2.34.45 Command Reference](../../index.html) »
+  * [AWS CLI 2.34.48 Command Reference](../../index.html) »
@@ -664,0 +665 @@ harness -> (structure)
+>>>>>>>>   * `TOKEN_EXCHANGE` \- Authorization using on-behalf-of token exchange. An inbound user token is exchanged for a downstream access token scoped to the target audience.
@@ -917,0 +919,14 @@ harness -> (structure)
+>>>>> 
+>>>>> requireServiceS3Endpoint -> (boolean)
+>>>>>
+>>>>>> ### Note
+>>>>>> 
+>>>>>> This field applies only to Agent Runtimes. It is not applicable to Browsers or Code Interpreters.
+>>>>>> 
+>>>>>> Controls whether a service-managed Amazon S3 gateway endpoint is provisioned in the VPC network topology for the agent runtime. This gateway is used by Amazon Bedrock AgentCore Runtime to download code and container images during agent startup.
+>>>>>> 
+>>>>>> Starting May 5, 2026, Amazon Bedrock AgentCore Runtime is gradually rolling out a change to how network isolation is configured for VPC mode agents. Agent runtimes created on or after this rollout will no longer include the service-managed Amazon S3 gateway. Instead, all network access, including to Amazon S3, is governed exclusively by your VPC configuration. This field cannot be set on agent runtimes created after the rollout. Passing this field in an `UpdateAgentRuntime` request for these agent runtimes returns a `ValidationException` .
+>>>>>> 
+>>>>>> Agent runtimes created before the rollout are not affected and continue to operate with the service-managed Amazon S3 gateway. To enforce full VPC network isolation on these existing agent runtimes, set this field to `false` via the `UpdateAgentRuntime` API. Before opting out, ensure your VPC provides the Amazon S3 access required for agent startup. If this field is not specified or is set to `true` , the service-managed Amazon S3 gateway remains provisioned.
+>>>>>> 
+>>>>>> This field is only supported in the `UpdateAgentRuntime` API for pre-rollout agent runtimes. Passing this field in a `CreateAgentRuntime` request returns a `ValidationException` .
@@ -1583 +1598 @@ harness -> (structure)
-  * [AWS CLI 2.34.45 Command Reference](../../index.html) »
+  * [AWS CLI 2.34.48 Command Reference](../../index.html) »