LaunchConfiguration is the Schema for the LaunchConfigurations API. Provides a resource to create a new launch configuration, used for autoscaling groups.
Type
CRD
Group
autoscaling.aws.upbound.io
Version
apiVersion: autoscaling.aws.upbound.io/v1beta1
kind: LaunchConfiguration
LaunchConfigurationSpec defines the desired state of LaunchConfiguration
No description provided.
Additional EBS block devices to attach to the instance. See Block Devices below for details.
Customize Ephemeral (also known as "Instance Store") volumes on the instance. See Block Devices below for details.
The metadata options for the instance.
Customize details about the root block device of the instance. See Block Devices below for details.
A list of associated security group IDS.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
Additional EBS block devices to attach to the instance. See Block Devices below for details.
Customize Ephemeral (also known as "Instance Store") volumes on the instance. See Block Devices below for details.
The metadata options for the instance.
Customize details about the root block device of the instance. See Block Devices below for details.
A list of associated security group IDS.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
LaunchConfigurationStatus defines the observed state of LaunchConfiguration.
No description provided.
Additional EBS block devices to attach to the instance. See Block Devices below for details.
Customize Ephemeral (also known as "Instance Store") volumes on the instance. See Block Devices below for details.
The metadata options for the instance.
Customize details about the root block device of the instance. See Block Devices below for details.
A list of associated security group IDS.
Conditions of the resource.
autoscalinggroup-example
apiVersion: autoscaling.aws.upbound.io/v1beta1
kind: LaunchConfiguration
metadata:
annotations:
meta.upbound.io/example-id: autoscaling/v1beta1/autoscalinggroup
labels:
testing.upbound.io/example-name: autoscalinggroup-example
name: autoscalinggroup-example
spec:
forProvider:
imageId: ami-0454207e5367abf01
instanceType: t2.micro
region: us-west-1
as-conf
apiVersion: autoscaling.aws.upbound.io/v1beta1
kind: LaunchConfiguration
metadata:
annotations:
meta.upbound.io/example-id: autoscaling/v1beta1/launchconfiguration
upjet.upbound.io/manual-intervention: This resource refers to an AMI ID.
labels:
testing.upbound.io/example-name: as_conf
name: as-conf
spec:
forProvider:
imageId: ami-0a1a70369f0fce06a
instanceType: t2.micro
region: us-west-1
attachment-example
apiVersion: autoscaling.aws.upbound.io/v1beta1
kind: LaunchConfiguration
metadata:
annotations:
meta.upbound.io/example-id: autoscaling/v1beta1/attachment
labels:
testing.upbound.io/example-name: attachment-example
name: attachment-example
spec:
forProvider:
imageId: ami-0454207e5367abf01
instanceType: t2.micro
region: us-west-1
as-conf
apiVersion: autoscaling.aws.upbound.io/v1beta1
kind: LaunchConfiguration
metadata:
annotations:
meta.upbound.io/example-id: autoscaling/v1beta1/launchconfiguration
labels:
testing.upbound.io/example-name: as_conf
name: as-conf
spec:
forProvider:
imageId: ami-0454207e5367abf01
instanceType: t2.micro
region: us-west-1
as-conf
apiVersion: autoscaling.aws.upbound.io/v1beta1
kind: LaunchConfiguration
metadata:
annotations:
meta.upbound.io/example-id: autoscaling/v1beta1/launchconfiguration
upjet.upbound.io/manual-intervention: This resource refers to an AMI ID.
labels:
testing.upbound.io/example-name: as_conf
name: as-conf
spec:
forProvider:
imageId: ${data.aws_ami.ubuntu.id}
instanceType: t2.micro
region: us-west-1