Terraform-provider-aws: Add support for EFS File Systems configuration in Amazon ECS and AWS Fargate

[marcincuber]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, 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

Description

Add support for new feature EFSVolumeConfiguration which is available for ECS + Fargate running platform version 1.4.

References

• https://aws.amazon.com/about-aws/whats-new/2020/04/amazon-ecs-aws-fargate-support-amazon-efs-filesystems-generally-available/

[DrFaust92]

EFSVolumeConfiguration support is already present but was not tested with fargate (there is no particular fargate config for this block)

the IAM and Access Point configs needs to be added

[marcincuber]

@DrFaust92 I tried upgrading my ECS Fargate services using latest terraform provider and it didn't upgrade it to platform version 1.4. Could it be that it requires SDK upgrade as well?

[DrFaust92]

Can you share your config?

The changes are for ecs task definition and the platform version is part of ecs service (may be needed to specify explicitly 1.4 and not the default)

I'll try to test it but I don't see anything in the new sdk version that's related

[marcincuber]

Hi I am using my module which you can find here together with the ecs_service resources. https://github.com/umotif-public/terraform-aws-ecs-fargate/blob/master/main.tf#L220

I am not specifying platform_version which means that for FARGATE it should default to LATEST which is 1.4. You could be right that explicitly specifying version would work but then that means LATEST option doesn't work.

[DrFaust92]

tested it, does not work in either config. well have to wait for the new sdk version merge and try again then.

[bflad]

LATEST not being "latest" may be confirmed here: https://github.com/aws/containers-roadmap/issues/53#issuecomment-611165795 (e.g. an API issue)

[tabletcorry]

LATEST still points to 1.3.0 per the docs: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html

To use a specific platform version, specify the version number when creating or updating your service. If you specify LATEST, your tasks use platform version 1.3.0.

So to test this, you must specify 1.4.0 at the moment.

[DrFaust92]

Argh, I user 1.4 and not 1.4.0 so it might the reason it failed on my side.

I'll check again.

On Thu, Apr 9, 2020, 21:10 Corry Haines [e-mail] wrote:

LATEST still points to 1.3.0 per the docs:
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html

To use a specific platform version, specify the version number when
creating or updating your service. If you specify LATEST, your tasks use
platform version 1.3.0.

So to test this, you must specify 1.4.0 at the moment.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/terraform-providers/terraform-provider-aws/issues/12741#issuecomment-611674478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIA2W7UWZ4ETCY7TB3PTXSDRLYFSJANCNFSM4MEPPHGQ
.

[travisz]

Thanks @tabletcorry! Just tested with 1.4.0 and confirmed it worked :)

[marcincuber]

So to wrap up this issue. This feature is already supported and to use the latest version of fargate we need to specify the following:

resource "aws_ecs_service" "service" {
  ...
  platform_version = "1.4.0"
}

and for some random reason LATEST version still points at 1.3.0 version.

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!