feat: enable Amazon Bedrock AgentCore services #67
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add bedrock-agent, bedrock-agent-runtime, and bedrock-agentcore to SCP allowlist to enable sandbox users to deploy and manage Bedrock agents. Upgrade aws-nuke from v3.60.1 to v3.62.0 which adds support for cleaning up bedrock-agentcore resources during sandbox cleanup.
marcpeiser
force-pushed
the
feature/enable-bedrock-agentcore-services
branch
from
75db3de to
c41bcfa
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Enable Amazon Bedrock AgentCore services in sandbox accounts by:
Adding bedrock-agent services to SCP allowlist - Allows
bedrock-agent:*,bedrock-agent-runtime:*, andbedrock-agentcore:*actions in sandbox accountsUpdating aws-nuke to v3.62.0 - Adds support for cleaning up BedrockAgentCore resources (AgentRuntime, Gateway, Memory, etc.)
Excluding BedrockAgentCoreWorkloadIdentity from cleanup - These resources cannot be deleted directly; they are automatically deleted when the parent AgentRuntime is deleted
Changes
isb-aws-nuke-supported-services-scp.json- Add bedrock-agent services to NotAction listDockerfile- Update aws-nuke v3.60.1 → v3.62.0nuke-config.yaml- Exclude BedrockAgentCoreWorkloadIdentity from cleanupTechnical Details
AWS Bedrock AgentCore creates a WorkloadIdentity resource when an AgentRuntime is created. This WorkloadIdentity is linked to the AgentRuntime and cannot be deleted directly via API - attempting to do so returns:
The fix excludes this resource type from aws-nuke cleanup. When aws-nuke deletes the parent AgentRuntime, AWS automatically cascade-deletes the associated WorkloadIdentity.