Deployment of Fargate Batch tasks with EFS volumes incorrectly fails when FargatePlatform set to LATEST

[tcutts]

Name of the resource

AWS::Batch::JobDefinition

Resource Name

No response

Issue Description

If a job needs to run on a Fargate compute environment, using an EFS volume, support for this was added with Fargate 1.4.0.

This does not work if you specify LATEST as the PlatformVersion, which it should. It does work if you specify 1.4.0

Expected Behavior

The resource should deploy correctly whether the PlatformVersion is set to LATEST or 1.4.0.

Observed Behavior

If you specify 1.4.0, all works well. If you specify LATEST, you get the following error:

Failed to register job definition
Error: Error executing request, Exception : EFS is supported for Fargate platform version 1.4.0.

Test Cases

Create a Fargate ComputeEnvironment, EFS filesystem, and a job definition which attaches an EFS volume. An example can be see in the Batch/EFS integration test for CDK, starting from line 133: https://github.com/aws/aws-cdk/blob/main/packages/%40aws-cdk/aws-batch/test/integ.batch-with-efs.ts

Other Details

While I discovered it there, I do not think this is not a CDK problem; other users have reported it in other contexts: https://repost.aws/questions/QUNxKFSBgPQQOybinQWYSNdQ/efs-volume-in-batch-job-running-on-fargate

[luisantonioa]

I confirmed this issue also occurs in the AWS Batch console which is outside of Cloudformation handlers which this project represents.

[luisantonioa]

Will track the fix internally since it is not caused by the AWS Batch cloud formation handlers.