404

[ Avaa Bypassed ]




Upload:

Command:

botdev@18.188.190.28: ~ $
**Example 1: To create a launch configuration**

This example creates a simple launch configuration. ::

    aws autoscaling create-launch-configuration \
        --launch-configuration-name my-lc \
        --image-id ami-04d5cc9b88example \
        --instance-type m5.large

This command produces no output.

For more information, see `Creating a launch configuration <https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-config.html>`__ in the *Amazon EC2 Auto Scaling User Guide*.

**Example 2: To create a launch configuration with a security group, key pair, and bootrapping script**

This example creates a launch configuration with a security group, a key pair, and a bootrapping script contained in the user data. ::

    aws autoscaling create-launch-configuration \
        --launch-configuration-name my-lc \
        --image-id ami-04d5cc9b88example \
        --instance-type m5.large \
        --security-groups sg-eb2af88example \
        --key-name my-key-pair \
        --user-data file://myuserdata.txt

This command produces no output.

For more information, see `Creating a launch configuration <https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-config.html>`__ in the *Amazon EC2 Auto Scaling User Guide*.

**Example 3: To create a launch configuration with an IAM role**

This example creates a launch configuration with the instance profile name of an IAM role. ::

    aws autoscaling create-launch-configuration \
        --launch-configuration-name my-lc \
        --image-id ami-04d5cc9b88example \
        --instance-type m5.large \
        --iam-instance-profile my-autoscaling-role 

This command produces no output.

For more information, see `IAM role for applications that run on Amazon EC2 instances <https://docs.aws.amazon.com/autoscaling/ec2/userguide/us-iam-role.html>`__ in the *Amazon EC2 Auto Scaling User Guide*.

**Example 4: To create a launch configuration with detailed monitoring enabled**

This example creates a launch configuration with EC2 detailed monitoring enabled, which sends EC2 metrics to CloudWatch in 1-minute periods. ::

    aws autoscaling create-launch-configuration \
        --launch-configuration-name my-lc \
        --image-id ami-04d5cc9b88example \
        --instance-type m5.large \
        --instance-monitoring Enabled=true 

This command produces no output.

For more information, see `Configuring monitoring for Auto Scaling instances  <https://docs.aws.amazon.com/autoscaling/ec2/userguide/enable-as-instance-metrics.html>`__ in the *Amazon EC2 Auto Scaling User Guide*.

**Example 5: To create a launch configuration that launches Spot Instances**

This example creates a launch configuration that uses Spot Instances as the only purchase option. ::

    aws autoscaling create-launch-configuration \
        --launch-configuration-name my-lc \
        --image-id ami-04d5cc9b88example \
        --instance-type m5.large \
        --spot-price "0.50"

This command produces no output.

For more information, see `Requesting Spot Instances <https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-launch-spot-instances.html>`__ in the *Amazon EC2 Auto Scaling User Guide*.

**Example 6: To create a launch configuration using an EC2 instance**

This example creates a launch configuration based on the attributes of an existing instance. It overrides the placement tenancy and whether a public IP address is set by including the ``--placement-tenancy`` and ``--no-associate-public-ip-address`` options. ::

    aws autoscaling create-launch-configuration \
        --launch-configuration-name my-lc-from-instance \
        --instance-id i-0123a456700123456 \
        --instance-type m5.large \
        --no-associate-public-ip-address \
        --placement-tenancy dedicated 

This command produces no output.

For more information, see `Creating a launch configuration using an EC2 instance <https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-lc-with-instanceID.html>`__ in the *Amazon EC2 Auto Scaling User Guide*.

**Example 7: To create a launch configuration with a block device mapping for an Amazon EBS volume**

This example creates a launch configuration with a block device mapping for an Amazon EBS ``gp3`` volume with the device name ``/dev/sdh`` and a volume size of 20. ::

    aws autoscaling create-launch-configuration \
        --launch-configuration-name my-lc \
        --image-id ami-04d5cc9b88example \
        --instance-type m5.large \
        --block-device-mappings '[{"DeviceName":"/dev/sdh","Ebs":{"VolumeSize":20,"VolumeType":"gp3"}}]'

This command produces no output.

For more information, see `EBS <https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_Ebs.html>`__ in the *Amazon EC2 Auto Scaling API Reference*.

For information about the syntax for quoting JSON-formatted parameter values, see `Using quotation marks with strings in the AWS CLI <https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-parameters-quoting-strings.html>`__ in the *AWS Command Line Interface User Guide*. 

**Example 8: To create a launch configuration with a block device mapping for an instance store volume**

This example creates a launch configuration with ``ephemeral1`` as an instance store volume with the device name ``/dev/sdc``. ::

    aws autoscaling create-launch-configuration \
        --launch-configuration-name my-lc \
        --image-id ami-04d5cc9b88example \
        --instance-type m5.large \
        --block-device-mappings '[{"DeviceName":"/dev/sdc","VirtualName":"ephemeral1"}]'

This command produces no output.

For more information, see `BlockDeviceMapping <https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_BlockDeviceMapping.html>`__ in the *Amazon EC2 Auto Scaling API Reference*.

For information about the syntax for quoting JSON-formatted parameter values, see `Using quotation marks with strings in the AWS CLI <https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-parameters-quoting-strings.html>`__ in the *AWS Command Line Interface User Guide*. 

**Example 9: To create a launch configuration and suppress a block device from attaching at launch time**

This example creates a launch configuration that suppresses a block device specified by the block device mapping of the AMI (for example, ``/dev/sdf``). ::

    aws autoscaling create-launch-configuration \
        --launch-configuration-name my-lc \
        --image-id ami-04d5cc9b88example \
        --instance-type m5.large \
        --block-device-mappings '[{"DeviceName":"/dev/sdf","NoDevice":""}]'

This command produces no output.

For more information, see `BlockDeviceMapping <https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_BlockDeviceMapping.html>`__ in the *Amazon EC2 Auto Scaling API Reference*.

For information about the syntax for quoting JSON-formatted parameter values, see `Using quotation marks with strings in the AWS CLI <https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-parameters-quoting-strings.html>`__ in the *AWS Command Line Interface User Guide*. 

Filemanager

Name Type Size Permission Actions
attach-instances.rst File 306 B 0644
attach-load-balancer-target-groups.rst File 622 B 0755
attach-load-balancers.rst File 554 B 0644
cancel-instance-refresh.rst File 545 B 0644
complete-lifecycle-action.rst File 690 B 0644
create-auto-scaling-group.rst File 8.71 KB 0644
create-launch-configuration.rst File 7.03 KB 0644
create-or-update-tags.rst File 619 B 0644
delete-auto-scaling-group.rst File 1006 B 0644
delete-launch-configuration.rst File 445 B 0644
delete-lifecycle-hook.rst File 263 B 0644
delete-notification-configuration.rst File 573 B 0644
delete-policy.rst File 270 B 0644
delete-scheduled-action.rst File 338 B 0644
delete-tags.rst File 496 B 0644
delete-warm-pool.rst File 961 B 0644
describe-account-limits.rst File 596 B 0644
describe-adjustment-types.rst File 700 B 0644
describe-auto-scaling-groups.rst File 3.61 KB 0644
describe-auto-scaling-instances.rst File 2.01 KB 0644
describe-auto-scaling-notification-types.rst File 745 B 0644
describe-instance-refreshes.rst File 2.21 KB 0644
describe-launch-configurations.rst File 2.46 KB 0644
describe-lifecycle-hook-types.rst File 345 B 0644
describe-lifecycle-hooks.rst File 972 B 0644
describe-load-balancer-target-groups.rst File 570 B 0755
describe-load-balancers.rst File 443 B 0644
describe-metric-collection-types.rst File 1.57 KB 0644
describe-notification-configurations.rst File 2.49 KB 0644
describe-policies.rst File 4.7 KB 0644
describe-scaling-activities.rst File 4.95 KB 0644
describe-scaling-process-types.rst File 1.11 KB 0644
describe-scheduled-actions.rst File 6.92 KB 0644
describe-tags.rst File 1.96 KB 0644
describe-termination-policy-types.rst File 727 B 0644
describe-warm-pool.rst File 1.56 KB 0644
detach-instances.rst File 1015 B 0644
detach-load-balancer-target-groups.rst File 654 B 0755
detach-load-balancers.rst File 559 B 0644
disable-metrics-collection.rst File 581 B 0644
enable-metrics-collection.rst File 1.11 KB 0644
enter-standby.rst File 1.25 KB 0644
execute-policy.rst File 578 B 0644
exit-standby.rst File 1.15 KB 0644
put-lifecycle-hook.rst File 2.5 KB 0644
put-notification-configuration.rst File 637 B 0644
put-scaling-policy.rst File 1.94 KB 0644
put-scheduled-update-group-action.rst File 1.54 KB 0644
put-warm-pool.rst File 509 B 0644
record-lifecycle-action-heartbeat.rst File 596 B 0644
resume-processes.rst File 518 B 0644
rollback-instance-refresh.rst File 559 B 0644
set-desired-capacity.rst File 341 B 0644
set-instance-health.rst File 290 B 0644
set-instance-protection.rst File 714 B 0644
start-instance-refresh.rst File 1.96 KB 0644
suspend-processes.rst File 514 B 0644
terminate-instance-in-auto-scaling-group.rst File 1005 B 0644
update-auto-scaling-group.rst File 4.9 KB 0644