AWS::Pipes::Pipe BatchContainerOverrides
The overrides that are sent to a container.
Syntax
To declare this entity in your AWS CloudFormation template, use the following syntax:
JSON
{ "Command" :
[ String, ... ]
, "Environment" :[ BatchEnvironmentVariable, ... ]
, "InstanceType" :String
, "ResourceRequirements" :[ BatchResourceRequirement, ... ]
}
YAML
Command:
- String
Environment:- BatchEnvironmentVariable
InstanceType:String
ResourceRequirements:- BatchResourceRequirement
Properties
Command
-
The command to send to the container that overrides the default command from the Docker image or the task definition.
Required: No
Type: Array of String
Update requires: No interruption
Environment
-
The environment variables to send to the container. You can add new environment variables, which are added to the container at launch, or you can override the existing environment variables from the Docker image or the task definition.
Note
Environment variables cannot start with "
AWS Batch
". This naming convention is reserved for variables that AWS Batch sets.Required: No
Type: Array of BatchEnvironmentVariable
Update requires: No interruption
InstanceType
-
The instance type to use for a multi-node parallel job.
Note
This parameter isn't applicable to single-node container jobs or jobs that run on Fargate resources, and shouldn't be provided.
Required: No
Type: String
Update requires: No interruption
ResourceRequirements
-
The type and amount of resources to assign to a container. This overrides the settings in the job definition. The supported resources include
GPU
,MEMORY
, andVCPU
.Required: No
Type: Array of BatchResourceRequirement
Update requires: No interruption