Skip to content

Commit 30722f2

Browse files
feat(batch): ecs execute command (#35341)
### Issue # (if applicable) None ### Reason for this change AWS Batch now supports for ECS execute command(ECS exec) to access to the job container. https://aws.amazon.com/about-aws/whats-new/2025/04/aws-batch-amazon-elastic-container-service-exec-firelens-log-router/?nc1=h_ls ### Description of changes - Add `enableExecuteCommand` prop ro `EcsContainerDefinitionProps` - handle batch job role to add ecs exec policies ### Describe any new or updated permissions being added - Add some permissions to the job role - "ssmmessages:CreateControlChannel", - "ssmmessages:CreateDataChannel", - "ssmmessages:OpenControlChannel", - "ssmmessages:OpenDataChannel" ### Description of how you validated changes Add both unit and integ tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
1 parent 04d8a95 commit 30722f2

File tree

15 files changed

+35574
-1
lines changed

15 files changed

+35574
-1
lines changed

packages/@aws-cdk-testing/framework-integ/test/aws-batch/test/integ.ecs-exec-batch-job.js.snapshot/EcsExecBatchStack.assets.json

Lines changed: 34 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)