aws / aws/containers-roadmap

[ECS] [request]: ECS Fargate supports S3 environmentFile with version ID parameter

Open
#1,263 3 comments 15 reactions 1 assignee Claimed by @vibhav-ag View on GitHub
ECS Fargate Proposed
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**

ECS Fargate wants to support S3 obejct version ID of object path on environmentFile property of task-definition.

**Which service(s) is this request for?**

ECS Fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

I've used a feature which can use S3 object as environment file on ECS Fargate that is released on 11/2020
https://aws.amazon.com/about-aws/whats-new/2020/11/aws-fargate-for-amazon-ecs-launches-features-focused-on-configuration-and-metrics/
However it doesn't support version id of S3 object path.

**Are you currently working around this issue?**

I put S3 object with new path ( includes git hash) when I deploy applications everytime via Codebuild.

It would be nice if you could support version ID for ECS Fargate enviroment files feature :)
Thanks!

Toshipon

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.