Is there an existing issue for this?

• I have searched the existing issues
• bug: Secrets not passed to ECS Fargate task as environment variable #8492
• But, the different thing is this Issue is for Aws Batch.

Current Behavior

Job Definition is setting with EcsFargateContainerDefinition.
The option of EcsFargateContainerDefinitionProp environment is passed to environment variables, but, the option secrets isn't passed to environment variables.

I attempted to access the container directly to check the environment variables by searching for the cluster and task ID. While the compute environment contained an ecsClusterArn, when I checked the actual cluster, it was in a failures state with the reason: MISSING, making it impossible to verify the cluster and access the container.

If this is not a bug, please let me know the example how to set up.

Expected Behavior

Aws Batch with Job definition of EcsFargateContainerDefinition pass secrets to environment variables.

How are you starting LocalStack?

With a docker-compose file

Environment

- OS:
- LocalStack:localstack/localstack-pro
  LocalStack version:latest

Anything else?

No response