feat(agentcore): update resources on grantInvokeXXX for runtime #35864
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.
Issue # (if applicable)
Reason for this change
The
grantInvoke,grantInvokeRuntime, andgrantInvokeRuntimeForUsermethods in the BedrockAgentRuntime were only granting permissions to the runtime ARN itself, but not to its sub-resources. This caused permission issues when trying to invoke runtime endpoints from an AWS resource like lambda, as the actual invocation happens on sub-resources (e.g., arn:aws:bedrock-agentcore:region:account:runtime/runtime-id/*).Description of changes
Updated the
resourceArnsparameter in three grant methods withinruntime-base.ts:Describe any new or updated permissions being added
The IAM permissions granted by these methods now include:
bedrock-agentcore:InvokeAgentRuntimeon both the runtime ARN and its sub-resourcesbedrock-agentcore:InvokeAgentRuntimeForUseron both the runtime ARN and its sub-resourcesDescription of how you validated changes
Manual and Integration test
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license