InstanceLaunchTemplate¶
Structure Class¶
InstanceLaunchTemplate
dataclass
¶
Bases: _SerdeShape
The launch template configuration for Amazon ECS Managed Instances. This defines how Amazon ECS launches Amazon EC2 instances, including the instance profile for your tasks, network and storage configuration, capacity options, and instance requirements for flexible instance type selection.
Attributes¶
capacity_option_type
class-attribute
instance-attribute
¶
capacity_option_type: str | None = ...
The capacity option type. This determines whether Amazon ECS launches On-Demand, Spot or Capacity Reservation Instances for your managed instance capacity provider.
Valid values are:
-
ON_DEMAND- Launches standard On-Demand Instances. On-Demand Instances provide predictable pricing and availability. -
SPOT- Launches Spot Instances that use spare Amazon EC2 capacity at reduced cost. Spot Instances can be interrupted by Amazon EC2 with a two-minute notification when the capacity is needed back. -
RESERVED- Launches Instances using Amazon EC2 Capacity Reservations. Capacity Reservations allow you to reserve compute capacity for Amazon EC2 instances in a specific Availability Zone.
The default is On-Demand
For more information about Amazon EC2 capacity options, see Instance purchasing options in the Amazon EC2 User Guide.
capacity_reservations
class-attribute
instance-attribute
¶
capacity_reservations: CapacityReservationRequest | None = ...
Capacity reservation specifications. You can specify:
-
Capacity reservation preference
-
Reservation resource group to be used for targeted capacity reservations
Amazon ECS will launch instances according to the specified criteria.
ec2_instance_profile_arn
instance-attribute
¶
ec2_instance_profile_arn: str
The Amazon Resource Name (ARN) of the instance profile that Amazon ECS applies to Amazon ECS Managed Instances. This instance profile must include the necessary permissions for your tasks to access Amazon Web Services services and resources.
For more information, see Amazon ECS instance profile for Managed Instances in the Amazon ECS Developer Guide.
fips_enabled
class-attribute
instance-attribute
¶
fips_enabled: bool | None = ...
Determines whether to enable FIPS 140-2 validated cryptographic modules
on EC2 instances launched by the capacity provider. If true, instances
use FIPS-compliant cryptographic algorithms and modules for enhanced
security compliance. If false, instances use standard cryptographic
implementations.
If not specified, instances are launched with FIPS enabled in Amazon Web Services GovCloud (US) regions and FIPS disabled in other regions.
instance_metadata_tags_propagation
class-attribute
instance-attribute
¶
instance_metadata_tags_propagation: bool | None = ...
Determines whether tags are propagated to the instance metadata service (IMDS) for Amazon EC2 instances launched by the Managed Instances capacity provider. When enabled, all tags associated with the instance are available through the instance metadata service. When disabled, tags are not propagated to IMDS.
Disable this setting if your tags contain characters that are not
compatible with IMDS, such as /. IMDS requires tag keys to match the
pattern [0-9a-zA-Z\-_+=,.@:]{1,255}.
The default value is true.
For more information, see Work with instance tags in instance metadata in the Amazon EC2 User Guide.
instance_requirements
class-attribute
instance-attribute
¶
instance_requirements: InstanceRequirementsRequest | None = ...
The instance requirements. You can specify:
-
The instance types
-
Instance requirements such as vCPU count, memory, network performance, and accelerator specifications
Amazon ECS automatically selects the instances that match the specified criteria.
local_storage_configuration
class-attribute
instance-attribute
¶
local_storage_configuration: ManagedInstancesLocalStorageConfiguration | None = ...
The local storage configuration for Amazon ECS Managed Instances. This defines how ECS uses instance store volumes available on the container instance.
monitoring
class-attribute
instance-attribute
¶
monitoring: str | None = ...
CloudWatch provides two categories of monitoring: basic monitoring and detailed monitoring. By default, your managed instance is configured for basic monitoring. You can optionally enable detailed monitoring to help you more quickly identify and act on operational issues. You can enable or turn off detailed monitoring at launch or when the managed instance is running or stopped. For more information, see Detailed monitoring for Amazon ECS Managed Instances in the Amazon ECS Developer Guide.
network_configuration
instance-attribute
¶
network_configuration: ManagedInstancesNetworkConfiguration
The network configuration for Amazon ECS Managed Instances. This specifies the subnets and security groups that instances use for network connectivity.
nitro_enclaves_enabled
class-attribute
instance-attribute
¶
nitro_enclaves_enabled: bool | None = ...
Specifies whether instances that this capacity provider launches have
Nitro
Sandbox
enabled. Enable this setting to run tasks that use the
ISOLATED_SANDBOX or CONFIDENTIAL_SANDBOX isolation mode.
When you enable this setting, the capacity provider must include at
least one instance type that supports Nitro Sandbox. You can't enable
this setting together with local storage (the useLocalStorage setting
in localStorageConfiguration).
The default value is false.
For more information, see Isolated and confidential tasks in Amazon Elastic Container Service Developer Guide.
storage_configuration
class-attribute
instance-attribute
¶
storage_configuration: ManagedInstancesStorageConfiguration | None = ...
The storage configuration for Amazon ECS Managed Instances. This defines the data volume properties for the instances.