AWS bedrock documentation change
Summary
Added documentation for pausing/resuming agents via aliasInvocationState field in UpdateAgentAlias API
Security assessment
The change adds operational controls for agent state management but doesn't address security vulnerabilities or introduce security features. While it mentions IAM policy modifications aren't required, this relates to operational permissions rather than security hardening.
Diff
diff --git a/bedrock/latest/userguide/deploy-agent.md b/bedrock/latest/userguide/deploy-agent.md index ada8168c3..913b863c7 100644 --- a//bedrock/latest/userguide/deploy-agent.md +++ b//bedrock/latest/userguide/deploy-agent.md @@ -4,0 +5,2 @@ +Pausing a deployed agent + @@ -18,0 +21,6 @@ With aliases, you can switch efficiently between different versions of your agen +## Pausing a deployed agent + +You might need to temporarily pause the running of an agent. For example, during maintenance, updates, or when addressing performance issues. To pause an agent, you use the alias for the agent with the [UpdateAgentAlias](bedrock/latest/APIReference/API_agent_UpdateAgentAlias.html) operation. To pause an agent, set the `aliasInvocationState` field to `REJECT_INVOCATIONS`. To start the agent running again, set `aliasInvocationState` to `ACCEPT_INVOCATIONS`. You don't need to make any IAM policy modifications to pause the agent. + +To check if an agent is currently paused, call [GetAgentAlias](bedrock/latest/APIReference/API_agent_GetAgentAlias.html) and check the `aliasInvocationState` field. You can also check the `aliasInvocationState` field for an alias in the response from [ListAgentAliases](bedrock/latest/APIReference/API_agent_ListAgentAliases.html). +