[ECS] [EFS]: Support for 'awsvpc', 'ecs-init', and 'ecs-volume-driver-plugin' with Debian based systems
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
Currently the `awsvpc` network mode (as confirmed in [documentation](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html#task-networking-considerations)), 'ecs-init' [package](https://github.com/aws/amazon-ecs-init#amazon-elastic-container-service-rpm) (support for agent updates), 'ecs-volume-plugin' are only officially supported with Amazon Linux variants. Support should be extended for use with Ubuntu AMIs vended by Amazon.
**Which service(s) is this request for?**
**ECS**
**Are you currently working around this issue?**
Custom AMI and building the `ecs-init` from source.
Contributor guide
Research direction
Begin with the linked ECS task-networking and ecs-init documentation, then inspect the ecs-init source and build process referenced by the workaround. Done means official support is defined for Ubuntu AMIs covering awsvpc, ecs-init updates, and the ECS volume driver plugin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, ubuntu
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100