(aws-ecs): vpc networking not possible with windows clusters
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
[docs.aws.amazon.com/AmazonECS/latest/developerguide/bootstrap_windows_container_instance.html](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/bootstrap_windows_container_instance.html)
In order to enable vpc networking on windows clusters `-EnableTaskENI` needs to be added to the `Initialize-ECSAgent` command that is run as part of the user data.
The line in the user data of the launch configuration needs to look like so
Initialize-ECSAgent -Cluster 'xxxxx' -EnableTaskIAMRole -EnableTaskENI
### Use Case
atm, can't use vpc networking with this flag
### Proposed Solution
_No response_
### Other Information
_No response_
### Acknowledgements
- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CDK version used
latest
### Environment details (OS name and version, etc.)
2019 full
Contributor guide
Research direction
Search the AWS CDK repository for the Windows user-data generation and the Initialize-ECSAgent command used by launch configurations. Confirm how the generated command is tested, then ensure Windows cluster user data includes -EnableTaskENI and verify the rendered user data for Windows 2019.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100