aws-cdk-lib/aws-ecs: Add task start up error logging to cdk output
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
To log ECS task start-up errors to the logs when running `cdk deploy`
### Use Case
A cloudformation stack update can seem to hang if the update is failing to start an ECS task (for example if you forgot to give it permission to access and ECR repository). Instead of having to dig down to the ECS task, it would be great if these kind of errors were displayed when running `cdk deploy` so you can more instantly see there is an issue and do something about it.
### Proposed Solution
Detect problems on task deployment/execution and log an error to the console running cdk deploy
### Other Information
_No response_
### Acknowledgements
- [x] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### AWS CDK Library version (aws-cdk-lib)
2.195.0
### AWS CDK CLI version
2.1014.0
### Environment details (OS name and version, etc.)
Windows and Linux
Contributor guide
Research direction
Start from the cdk deploy entry point and trace how ECS task deployment and execution failures are detected. Define which startup errors should be surfaced and verify that a failed task produces a useful console error without making successful deployments noisy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100