amazonka-batch-2.0: Amazon Batch SDK.
Copyright(c) 2013-2023 Brendan Hay
LicenseMozilla Public License, v. 2.0.
MaintainerBrendan Hay
Stabilityauto-generated
Portabilitynon-portable (GHC extensions)
Safe HaskellSafe-Inferred
LanguageHaskell2010

Amazonka.Batch.Types.LaunchTemplateSpecification

Description

 
Synopsis

Documentation

data LaunchTemplateSpecification Source #

An object that represents a launch template that's associated with a compute resource. You must specify either the launch template ID or launch template name in the request, but not both.

If security groups are specified using both the securityGroupIds parameter of CreateComputeEnvironment and the launch template, the values in the securityGroupIds parameter of CreateComputeEnvironment will be used.

This object isn't applicable to jobs that are running on Fargate resources.

See: newLaunchTemplateSpecification smart constructor.

Constructors

LaunchTemplateSpecification' 

Fields

  • launchTemplateId :: Maybe Text

    The ID of the launch template.

  • launchTemplateName :: Maybe Text

    The name of the launch template.

  • version :: Maybe Text

    The version number of the launch template, $Latest, or $Default.

    If the value is $Latest, the latest version of the launch template is used. If the value is $Default, the default version of the launch template is used.

    If the AMI ID that's used in a compute environment is from the launch template, the AMI isn't changed when the compute environment is updated. It's only changed if the updateToLatestImageVersion parameter for the compute environment is set to true. During an infrastructure update, if either $Latest or $Default is specified, Batch re-evaluates the launch template version, and it might use a different version of the launch template. This is the case even if the launch template isn't specified in the update. When updating a compute environment, changing the launch template requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.

    Default: $Default.

Instances

Instances details
FromJSON LaunchTemplateSpecification Source # 
Instance details

Defined in Amazonka.Batch.Types.LaunchTemplateSpecification

ToJSON LaunchTemplateSpecification Source # 
Instance details

Defined in Amazonka.Batch.Types.LaunchTemplateSpecification

Generic LaunchTemplateSpecification Source # 
Instance details

Defined in Amazonka.Batch.Types.LaunchTemplateSpecification

Associated Types

type Rep LaunchTemplateSpecification :: Type -> Type #

Read LaunchTemplateSpecification Source # 
Instance details

Defined in Amazonka.Batch.Types.LaunchTemplateSpecification

Show LaunchTemplateSpecification Source # 
Instance details

Defined in Amazonka.Batch.Types.LaunchTemplateSpecification

NFData LaunchTemplateSpecification Source # 
Instance details

Defined in Amazonka.Batch.Types.LaunchTemplateSpecification

Eq LaunchTemplateSpecification Source # 
Instance details

Defined in Amazonka.Batch.Types.LaunchTemplateSpecification

Hashable LaunchTemplateSpecification Source # 
Instance details

Defined in Amazonka.Batch.Types.LaunchTemplateSpecification

type Rep LaunchTemplateSpecification Source # 
Instance details

Defined in Amazonka.Batch.Types.LaunchTemplateSpecification

type Rep LaunchTemplateSpecification = D1 ('MetaData "LaunchTemplateSpecification" "Amazonka.Batch.Types.LaunchTemplateSpecification" "amazonka-batch-2.0-Ey2VZ5obnq65VwmlrJ2r2K" 'False) (C1 ('MetaCons "LaunchTemplateSpecification'" 'PrefixI 'True) (S1 ('MetaSel ('Just "launchTemplateId") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe Text)) :*: (S1 ('MetaSel ('Just "launchTemplateName") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe Text)) :*: S1 ('MetaSel ('Just "version") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe Text)))))

newLaunchTemplateSpecification :: LaunchTemplateSpecification Source #

Create a value of LaunchTemplateSpecification with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:launchTemplateId:LaunchTemplateSpecification', launchTemplateSpecification_launchTemplateId - The ID of the launch template.

$sel:launchTemplateName:LaunchTemplateSpecification', launchTemplateSpecification_launchTemplateName - The name of the launch template.

$sel:version:LaunchTemplateSpecification', launchTemplateSpecification_version - The version number of the launch template, $Latest, or $Default.

If the value is $Latest, the latest version of the launch template is used. If the value is $Default, the default version of the launch template is used.

If the AMI ID that's used in a compute environment is from the launch template, the AMI isn't changed when the compute environment is updated. It's only changed if the updateToLatestImageVersion parameter for the compute environment is set to true. During an infrastructure update, if either $Latest or $Default is specified, Batch re-evaluates the launch template version, and it might use a different version of the launch template. This is the case even if the launch template isn't specified in the update. When updating a compute environment, changing the launch template requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.

Default: $Default.

launchTemplateSpecification_version :: Lens' LaunchTemplateSpecification (Maybe Text) Source #

The version number of the launch template, $Latest, or $Default.

If the value is $Latest, the latest version of the launch template is used. If the value is $Default, the default version of the launch template is used.

If the AMI ID that's used in a compute environment is from the launch template, the AMI isn't changed when the compute environment is updated. It's only changed if the updateToLatestImageVersion parameter for the compute environment is set to true. During an infrastructure update, if either $Latest or $Default is specified, Batch re-evaluates the launch template version, and it might use a different version of the launch template. This is the case even if the launch template isn't specified in the update. When updating a compute environment, changing the launch template requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.

Default: $Default.