awscli 1.42.18__py3-none-any.whl → 1.42.19__py3-none-any.whl

awscli/examples/opsworks/disassociate-elastic-ip.rst

@@ -1,14 +0,0 @@
-**To disassociate an Elastic IP address from an instance**
-
-The following example disassociates an Elastic IP address from a specified instance. ::
-
-  aws opsworks --region us-east-1 disassociate-elastic-ip --elastic-ip 54.148.130.96
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Resource Management`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Resource Management`: http://docs.aws.amazon.com/opsworks/latest/userguide/resources.html
-

awscli/examples/opsworks/get-hostname-suggestion.rst

@@ -1,21 +0,0 @@
-**To get the next hostname for a layer**
-
-The following example gets the next generated hostname for a specified layer. The layer used for
-this example is a Java Application Server layer with one instance. The stack's hostname theme is
-the default, Layer_Dependent. ::
-
-  aws opsworks --region us-east-1 get-hostname-suggestion --layer-id 888c5645-09a5-4d0e-95a8-812ef1db76a4
-
-*Output*::
-
-  {
-    "Hostname": "java-app2", 
-    "LayerId": "888c5645-09a5-4d0e-95a8-812ef1db76a4"
-  }
-
-**More Information**
-
-For more information, see `Create a New Stack`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Create a New Stack`: http://docs.aws.amazon.com/opsworks/latest/userguide/workingstacks-creating.html
-

awscli/examples/opsworks/reboot-instance.rst

@@ -1,14 +0,0 @@
-**To reboot an instance**
-
-The following example reboots an instance. ::
-
-  aws opsworks --region us-east-1 reboot-instance --instance-id dfe18b02-5327-493d-91a4-c5c0c448927f
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Rebooting an Instance`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Rebooting an Instance`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-starting.html#workinginstances-starting-reboot
-

awscli/examples/opsworks/register-elastic-ip.rst

@@ -1,19 +0,0 @@
-**To register an Elastic IP address with a stack**
-
-The following example registers an Elastic IP address, identified by its IP address, with a specified stack.
-
-**Note:** The Elastic IP address must be in the same region as the stack. ::
-
-  aws opsworks register-elastic-ip --region us-east-1 --stack-id d72553d4-8727-448c-9b00-f024f0ba1b06 --elastic-ip 54.148.130.96 
-
-*Output* ::
-
-  {
-    "ElasticIp": "54.148.130.96"
-  }
-
-**More Information**
-
-For more information, see `Registering Elastic IP Addresses with a Stack`_ in the *OpsWorks User Guide*.
-
-.. _`Registering Elastic IP Addresses with a Stack`: http://docs.aws.amazon.com/opsworks/latest/userguide/resources-reg.html#resources-reg-eip

awscli/examples/opsworks/register-rds-db-instance.rst

@@ -1,15 +0,0 @@
-**To register an Amazon RDS instance with a stack**
-
-The following example registers an Amazon RDS DB instance, identified by its Amazon Resource Name (ARN), with a specified stack.
-It also specifies the instance's master username and password. Note that AWS OpsWorks does not validate either of these
-values. If either one is incorrect, your application will not be able to connect to the database. ::
-
-  aws opsworks register-rds-db-instance --region us-east-1 --stack-id d72553d4-8727-448c-9b00-f024f0ba1b06 --rds-db-instance-arn arn:aws:rds:us-west-2:123456789012:db:clitestdb  --db-user cliuser --db-password some23!pwd
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Registering Amazon RDS Instances with a Stack`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Registering Amazon RDS Instances with a Stack`: http://docs.aws.amazon.com/opsworks/latest/userguide/resources-reg.html#resources-reg-rds

awscli/examples/opsworks/register-volume.rst

@@ -1,18 +0,0 @@
-**To register an Amazon EBS volume with a stack**
-
-The following example registers an Amazon EBS volume, identified by its volume ID, with a specified stack. ::
-
-  aws opsworks register-volume --region us-east-1 --stack-id d72553d4-8727-448c-9b00-f024f0ba1b06 --ec-2-volume-id vol-295c1638
-
-*Output*::
-
-  {
-    "VolumeId": "ee08039c-7cb7-469f-be10-40fb7f0c05e8"
-  }
-
-
-**More Information**
-
-For more information, see `Registering Amazon EBS Volumes with a Stack`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Registering Amazon EBS Volumes with a Stack`: http://docs.aws.amazon.com/opsworks/latest/userguide/resources-reg.html#resources-reg-ebs

awscli/examples/opsworks/register.rst

@@ -1,105 +0,0 @@
-**To register instances with a stack**
-
-The following examples show a variety of ways to register instances with a stack that were created outside of AWS Opsworks.
-You can run ``register`` from the instance to be registered, or from a separate workstation.
-For more information, see `Registering Amazon EC2 and On-premises Instances`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Registering Amazon EC2 and On-premises Instances`: http://docs.aws.amazon.com/opsworks/latest/userguide/registered-instances-register-registering.html
-
-
-**Note**: For brevity, the examples omit the ``region`` argument.
-
-*To register an Amazon EC2 instance*
-
-To indicate that you are registering an EC2 instance, set the ``--infrastructure-class`` argument
-to ``ec2``.
-
-The following example registers an EC2 instance with the specified stack from a separate workstation.
-The instance is identified by its EC2 ID, ``i-12345678``. The example uses the workstation's default SSH username and attempts
-to log in to the instance using authentication techniques that do not require a password,
-such as a default private SSH key. If that fails, ``register`` queries for the password. ::
-
-  aws opsworks register --infrastructure-class=ec2 --stack-id 935450cc-61e0-4b03-a3e0-160ac817d2bb i-12345678
-
-The following example registers an EC2 instance with the specifed stack from a separate workstation.
-It uses the ``--ssh-username`` and ``--ssh-private-key`` arguments to explicitly
-specify the SSH username and private key file that the command uses to log into the instance.
-``ec2-user`` is the standard username for Amazon Linux instances. Use ``ubuntu`` for Ubuntu instances. ::
-
-  aws opsworks register --infrastructure-class=ec2 --stack-id 935450cc-61e0-4b03-a3e0-160ac817d2bb --ssh-username ec2-user --ssh-private-key ssh_private_key i-12345678
-
-The following example registers the EC2 instance that is running the ``register`` command.
-Log in to the instance with SSH and run ``register`` with the ``--local`` argument instead of an instance ID or hostname. ::
-
-  aws opsworks register --infrastructure-class ec2 --stack-id 935450cc-61e0-4b03-a3e0-160ac817d2bb --local
-
-*To register an on-premises instance*
-
-To indicate that you are registering an on-premises instance, set the ``--infrastructure-class`` argument
-to ``on-premises``.
-
-The following example registers an existing on-premises instance with a specified stack from a separate workstation.
-The instance is identified by its IP address, ``192.0.2.3``. The example uses the workstation's default SSH username and attempts
-to log in to the instance using authentication techniques that do not require a password,
-such as a default private SSH key. If that fails, ``register`` queries for the password. ::
-
-  aws opsworks register --infrastructure-class on-premises --stack-id 935450cc-61e0-4b03-a3e0-160ac817d2bb 192.0.2.3
-
-The following example registers an on-premises instance with a specified stack from a separate workstation.
-The instance is identified by its hostname, ``host1``. The ``--override-...`` arguments direct AWS OpsWorks
-to display ``webserver1`` as the host name and ``192.0.2.3`` and ``10.0.0.2`` as the instance's public and
-private IP addresses, respectively. ::
-
-  aws opsworks register --infrastructure-class on-premises --stack-id 935450cc-61e0-4b03-a3e0-160ac817d2bb --override-hostname webserver1 --override-public-ip 192.0.2.3 --override-private-ip 10.0.0.2 host1
-
-The following example registers an on-premises instance with a specified stack from a separate workstation.
-The instance is identified by its IP address. ``register`` logs into the instance using the specified SSH username and private key file. ::
-
-  aws opsworks register --infrastructure-class on-premises --stack-id 935450cc-61e0-4b03-a3e0-160ac817d2bb --ssh-username admin --ssh-private-key ssh_private_key 192.0.2.3
-
-The following example registers an existing on-premises instance with a specified stack from a separate workstation.
-The command logs into the instance using a custom SSH command string that specifies
-the SSH password and the instance's IP address. ::
-
-  aws opsworks register --infrastructure-class on-premises --stack-id 935450cc-61e0-4b03-a3e0-160ac817d2bb --override-ssh "sshpass -p 'mypassword' ssh your-user@192.0.2.3" 
-
-The following example registers the on-premises instance that is running the ``register`` command.
-Log in to the instance with SSH and run ``register`` with the ``--local`` argument instead of an instance ID or hostname. ::
-
-  aws opsworks register --infrastructure-class on-premises --stack-id 935450cc-61e0-4b03-a3e0-160ac817d2bb --local
-  
-*Output*: The following is typical output for registering an EC2 instance.
-
-::
-
-  Warning: Permanently added '52.11.41.206' (ECDSA) to the list of known hosts.
-  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
-                                 Dload  Upload   Total   Spent    Left  Speed
-  100 6403k  100 6403k    0     0  2121k      0  0:00:03  0:00:03 --:--:-- 2121k
-  [Tue, 24 Feb 2015 20:48:37 +0000] opsworks-init: Initializing AWS OpsWorks environment
-  [Tue, 24 Feb 2015 20:48:37 +0000] opsworks-init: Running on Ubuntu
-  [Tue, 24 Feb 2015 20:48:37 +0000] opsworks-init: Checking if OS is supported
-  [Tue, 24 Feb 2015 20:48:37 +0000] opsworks-init: Running on supported OS
-  [Tue, 24 Feb 2015 20:48:37 +0000] opsworks-init: Setup motd
-  [Tue, 24 Feb 2015 20:48:37 +0000] opsworks-init: Executing: ln -sf --backup /etc/motd.opsworks-static /etc/motd
-  [Tue, 24 Feb 2015 20:48:37 +0000] opsworks-init: Enabling multiverse repositories
-  [Tue, 24 Feb 2015 20:48:37 +0000] opsworks-init: Customizing APT environment
-  [Tue, 24 Feb 2015 20:48:37 +0000] opsworks-init: Installing system packages
-  [Tue, 24 Feb 2015 20:48:37 +0000] opsworks-init: Executing: dpkg --configure -a
-  [Tue, 24 Feb 2015 20:48:37 +0000] opsworks-init: Executing with retry: apt-get update
-  [Tue, 24 Feb 2015 20:49:13 +0000] opsworks-init: Executing: apt-get install -y ruby ruby-dev libicu-dev libssl-dev libxslt-dev libxml2-dev libyaml-dev monit
-  [Tue, 24 Feb 2015 20:50:13 +0000] opsworks-init: Using assets bucket from environment: 'opsworks-instance-assets-us-east-1.s3.amazonaws.com'.
-  [Tue, 24 Feb 2015 20:50:13 +0000] opsworks-init: Installing Ruby for the agent
-  [Tue, 24 Feb 2015 20:50:13 +0000] opsworks-init: Executing: /tmp/opsworks-agent-installer.YgGq8wF3UUre6yDy/opsworks-agent-installer/opsworks-agent/bin/installer_wrapper.sh -r -R opsworks-instance-assets-us-east-1.s3.amazonaws.com
-  [Tue, 24 Feb 2015 20:50:44 +0000] opsworks-init: Starting the installer
-  Instance successfully registered. Instance ID: 4d6d1710-ded9-42a1-b08e-b043ad7af1e2
-  Connection to 52.11.41.206 closed.
-
-**More Information**
-
-For more information, see `Registering an Instance with an AWS OpsWorks Stack`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Registering an Instance with an AWS OpsWorks Stack`: http://docs.aws.amazon.com/opsworks/latest/userguide/registered-instances-register.html
-
-
-

awscli/examples/opsworks/set-load-based-auto-scaling.rst

@@ -1,38 +0,0 @@
-**To set the load-based scaling configuration for a layer**
-
-The following example enables load-based scaling for a specified layer and sets the configuration
-for that layer.
-You must use ``create-instance`` to add load-based instances to the layer. ::
-
-  aws opsworks --region us-east-1 set-load-based-auto-scaling --layer-id 523569ae-2faf-47ac-b39e-f4c4b381f36d --enable --up-scaling file://upscale.json --down-scaling file://downscale.json
-
-The example puts the upscaling threshold settings in a separate file in the working directory named ``upscale.json``, which contains the following. ::
-
-  {
-    "InstanceCount": 2,
-    "ThresholdsWaitTime": 3,
-    "IgnoreMetricsTime": 3,
-    "CpuThreshold": 85,
-    "MemoryThreshold": 85,
-    "LoadThreshold": 85
-  }
-  
-The example puts the downscaling threshold settings in a separate file in the working directory named ``downscale.json``, which contains the following. ::
-
-  {
-  "InstanceCount": 2,
-  "ThresholdsWaitTime": 3,
-  "IgnoreMetricsTime": 3,
-  "CpuThreshold": 35,
-  "MemoryThreshold": 30,
-  "LoadThreshold": 30
-  }
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Using Automatic Load-based Scaling`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Using Automatic Load-based Scaling`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-autoscaling-loadbased.html
-

awscli/examples/opsworks/set-permission.rst

@@ -1,23 +0,0 @@
-**To grant per-stack AWS OpsWorks permission levels**
-
-When you import an AWS Identity and Access Management (IAM) user into AWS OpsWorks by calling ``create-user-profile``, the user has only those
-permissions that are granted by the attached IAM policies.
-You can grant AWS OpsWorks permissions by modifying a user's policies.
-However, it is often easier to import a user and then use the ``set-permission`` command to grant
-the user one of the standard permission levels for each stack to which the user will need access.
-
-The following example grants permission for the specified stack for a user, who
-is identified by Amazon Resource Name (ARN). The example grants the user a Manage permissions level, with sudo and SSH privileges on the stack's
-instances. ::
-
-  aws opsworks set-permission --region us-east-1 --stack-id 71c7ca72-55ae-4b6a-8ee1-a8dcded3fa0f --level manage  --iam-user-arn arn:aws:iam::123456789102:user/cli-user-test --allow-ssh --allow-sudo
-  
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Granting AWS OpsWorks Users Per-Stack Permissions`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Granting AWS OpsWorks Users Per-Stack Permissions`: http://docs.aws.amazon.com/opsworks/latest/userguide/opsworks-security-users-console.html
-

awscli/examples/opsworks/set-time-based-auto-scaling.rst

@@ -1,33 +0,0 @@
-**To set the time-based scaling configuration for a layer**
-
-The following example sets the time-based configuration for a specified instance.
-You must first use ``create-instance`` to add the instance to the layer. ::
-
-  aws opsworks --region us-east-1 set-time-based-auto-scaling --instance-id 69b6237c-08c0-4edb-a6af-78f3d01cedf2 --auto-scaling-schedule file://schedule.json
-
-The example puts the schedule in a separate file in the working directory named ``schedule.json``.
-For this example, the instance is on for a few hours around midday UTC (Coordinated Universal Time) on Monday and Tuesday. ::
-
-  {
-    "Monday": {
-      "10": "on",
-      "11": "on",
-      "12": "on",
-      "13": "on"
-    }, 
-    "Tuesday": {
-      "10": "on",
-      "11": "on",
-      "12": "on",
-      "13": "on" 
-    }
-  }
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Using Automatic Time-based Scaling`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Using Automatic Time-based Scaling`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-autoscaling-timebased.html
-

awscli/examples/opsworks/start-instance.rst

@@ -1,20 +0,0 @@
-**To start an instance**
-
-The following ``start-instance`` command starts a specified 24/7 instance. ::
-
-  aws opsworks start-instance --instance-id f705ee48-9000-4890-8bd3-20eb05825aaf
-
-*Output*: None. Use describe-instances_ to check the instance's status.
-
-.. _describe-instances: http://docs.aws.amazon.com/cli/latest/reference/opsworks/describe-instances.html
-
-**Tip** You can start every offline instance in a stack with one command by calling start-stack_.
-
-.. _start-stack: http://docs.aws.amazon.com/cli/latest/reference/opsworks/start-stack.html
-
-**More Information**
-
-For more information, see `Manually Starting, Stopping, and Rebooting 24/7 Instances`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Manually Starting, Stopping, and Rebooting 24/7 Instances`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-starting.html
-

awscli/examples/opsworks/start-stack.rst

@@ -1,15 +0,0 @@
-**To start a stack's instances**
-
-The following example starts all of a stack's 24/7 instances.
-To start a particular instance, use ``start-instance``. ::
-
-  aws opsworks --region us-east-1 start-stack --stack-id 8c428b08-a1a1-46ce-a5f8-feddc43771b8
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Starting an Instance`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Starting an Instance`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-starting.html#workinginstances-starting-start
-

awscli/examples/opsworks/stop-instance.rst

@@ -1,20 +0,0 @@
-**To stop an instance**
-
-The following example stops a specified instance, which is identified by its instance ID.
-You can obtain an instance ID by going to the instance's details page on the AWS OpsWorks console or by
-running the ``describe-instances`` command. ::
-
-  aws opsworks stop-instance --region us-east-1 --instance-id 3a21cfac-4a1f-4ce2-a921-b2cfba6f7771
-
-You can restart a stopped instance by calling ``start-instance`` or by deleting the instance by calling
-``delete-instance``.
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Stopping an Instance`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Stopping an Instance`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-starting.html#workinginstances-starting-stop
-
-

awscli/examples/opsworks/stop-stack.rst

@@ -1,15 +0,0 @@
-**To stop a stack's instances**
-
-The following example stops all of a stack's 24/7 instances.
-To stop a particular instance, use ``stop-instance``. ::
-
-  aws opsworks --region us-east-1 stop-stack --stack-id 8c428b08-a1a1-46ce-a5f8-feddc43771b8
-
-*Output*: No output.
-
-**More Information**
-
-For more information, see `Stopping an Instance`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Stopping an Instance`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-starting.html#workinginstances-starting-stop
-

awscli/examples/opsworks/unassign-instance.rst

@@ -1,14 +0,0 @@
-**To unassign a registered instance from its layers**
-
-The following ``unassign-instance`` command unassigns an instance from its attached layers. ::
-
-  aws opsworks --region us-east-1 unassign-instance --instance-id 4d6d1710-ded9-42a1-b08e-b043ad7af1e2
-
-**Output**: None.
-
-**More Information**
-
-For more information, see `Unassigning a Registered Instance`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Unassigning a Registered Instance`: http://docs.aws.amazon.com/opsworks/latest/userguide/registered-instances-unassign.html
-

awscli/examples/opsworks/unassign-volume.rst

@@ -1,16 +0,0 @@
-**To unassign a volume from its instance**
-
-The following example unassigns a registered Amazon Elastic Block Store (Amazon EBS) volume from its instance.
-The volume is identified by its volume ID, which is the GUID that AWS OpsWorks assigns when
-you register the volume with a stack, not the Amazon Elastic Compute Cloud (Amazon EC2) volume ID. ::
-
-  aws opsworks --region us-east-1 unassign-volume --volume-id 8430177d-52b7-4948-9c62-e195af4703df
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Unassigning Amazon EBS Volumes`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Unassigning Amazon EBS Volumes`: http://docs.aws.amazon.com/opsworks/latest/userguide/resources-detach.html#resources-detach-ebs
-

awscli/examples/opsworks/update-app.rst

@@ -1,14 +0,0 @@
-**To update an app**
-
-The following example updates a specified app to change its name. ::
-
-  aws opsworks --region us-east-1 update-app --app-id 26a61ead-d201-47e3-b55c-2a7c666942f8 --name NewAppName
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Editing Apps`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Editing Apps`: http://docs.aws.amazon.com/opsworks/latest/userguide/workingapps-editing.html
-

awscli/examples/opsworks/update-elastic-ip.rst

@@ -1,14 +0,0 @@
-**To update an Elastic IP address name**
-
-The following example updates the name of a specified Elastic IP address. ::
-
-  aws opsworks --region us-east-1 update-elastic-ip --elastic-ip 54.148.130.96 --name NewIPName
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Resource Management`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Resource Management`: http://docs.aws.amazon.com/opsworks/latest/userguide/resources.html
-

awscli/examples/opsworks/update-instance.rst

@@ -1,14 +0,0 @@
-**To update an instance**
-
-The following example updates a specified instance's type. ::
-
-  aws opsworks --region us-east-1 update-instance --instance-id dfe18b02-5327-493d-91a4-c5c0c448927f --instance-type c3.xlarge
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Editing the Instance Configuration`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Editing the Instance Configuration`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-properties.html
-

awscli/examples/opsworks/update-layer.rst

@@ -1,14 +0,0 @@
-**To update a layer**
-
-The following example updates a specified layer to use Amazon EBS-optimized instances. ::
-
-  aws opsworks --region us-east-1 update-layer --layer-id 888c5645-09a5-4d0e-95a8-812ef1db76a4 --use-ebs-optimized-instances
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Editing an OpsWorks Layer's Configuration`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Editing an OpsWorks Layer's Configuration`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinglayers-basics-edit.html
-

awscli/examples/opsworks/update-my-user-profile.rst

@@ -1,16 +0,0 @@
-**To update a user's profile**
-
-The following example updates the ``development`` user's profile to use a specified SSH public key.
-The user's AWS credentials are represented by the ``development`` profile in the ``credentials`` file
-(``~\.aws\credentials``), and the key is in a ``.pem`` file in the working directory. ::
-
-  aws opsworks --region us-east-1 --profile development update-my-user-profile --ssh-public-key file://development_key.pem
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Editing AWS OpsWorks User Settings`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Editing AWS OpsWorks User Settings`: http://docs.aws.amazon.com/opsworks/latest/userguide/opsworks-security-users-manage-edit.html
-

awscli/examples/opsworks/update-rds-db-instance.rst

@@ -1,18 +0,0 @@
-**To update a registered Amazon RDS DB instance**
-
-The following example updates an Amazon RDS instance's master password value.
-Note that this command does not change the RDS instance's master password, just the password that
-you provide to AWS OpsWorks.
-If this password does not match the RDS instance's password,
-your application will not be able to connect to the database. ::
-
-  aws opsworks --region us-east-1 update-rds-db-instance --db-password 123456789
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Registering Amazon RDS Instances with a Stack`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Registering Amazon RDS Instances with a Stack`: http://docs.aws.amazon.com/opsworks/latest/userguide/resources-reg.html#resources-reg-rds
-

awscli/examples/opsworks/update-volume.rst

@@ -1,16 +0,0 @@
-**To update a registered volume**
-
-The following example updates a registered Amazon Elastic Block Store (Amazon EBS) volume's mount point.
-The volume is identified by its volume ID, which is the GUID that AWS OpsWorks assigns to the volume when
-you register it with a stack, not the Amazon Elastic Compute Cloud (Amazon EC2) volume ID.::
-
-  aws opsworks --region us-east-1 update-volume --volume-id 8430177d-52b7-4948-9c62-e195af4703df --mount-point /mnt/myvol
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Assigning Amazon EBS Volumes to an Instance`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Assigning Amazon EBS Volumes to an Instance`: http://docs.aws.amazon.com/opsworks/latest/userguide/resources-attach.html#resources-attach-ebs
-

awscli/examples/opsworkscm/associate-node.rst

@@ -1,22 +0,0 @@
-**To associate nodes**
-
-The following ``associate-node`` command associates a node named ``i-44de882p`` with
-a Chef Automate server named ``automate-06``, meaning that the ``automate-06`` server
-manages the node, and communicates recipe commands to the node through ``chef-client`` agent software
-that is installed on the node by the associate-node command. Valid node names are EC2 instance IDs.::
-
-  aws opsworks-cm associate-node --server-name "automate-06" --node-name "i-43de882p" --engine-attributes "Name=CHEF_ORGANIZATION,Value='MyOrganization' Name=CHEF_NODE_PUBLIC_KEY,Value='Public_key_contents'"
-
-The output returned by the command resembles the following.
-*Output*::
-
-  {
-   "NodeAssociationStatusToken": "AHUY8wFe4pdXtZC5DiJa5SOLp5o14DH//rHRqHDWXxwVoNBxcEy4V7R0NOFymh7E/1HumOBPsemPQFE6dcGaiFk"
-  }
-
-**More Information**
-
-For more information, see `Adding Nodes Automatically in AWS OpsWorks for Chef Automate`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Adding Nodes Automatically in AWS OpsWorks for Chef Automate`: http://docs.aws.amazon.com/opsworks/latest/userguide/opscm-unattend-assoc.html
-

awscli/examples/opsworkscm/create-backup.rst

@@ -1,46 +0,0 @@
-**To create backups**
-
-The following ``create-backup`` command starts a manual backup of a Chef Automate server
-named ``automate-06`` in the ``us-east-1`` region. The command adds a descriptive message to
-the backup in the ``--description`` parameter. ::
-
-    aws opsworks-cm create-backup \
-        --server-name 'automate-06' \
-        --description "state of my infrastructure at launch"
-
-The output shows you information similar to the following about the new backup.
-
-Output::
-
-    {
-        "Backups": [ 
-            { 
-                "BackupArn": "string",
-                "BackupId": "automate-06-20160729133847520",
-                "BackupType": "MANUAL",
-                "CreatedAt": 2016-07-29T13:38:47.520Z,
-                "Description": "state of my infrastructure at launch",
-                "Engine": "Chef",
-                "EngineModel": "Single",
-                "EngineVersion": "12",
-                "InstanceProfileArn": "arn:aws:iam::1019881987024:instance-profile/automate-06-1010V4UU2WRM2",
-                "InstanceType": "m4.large",
-                "KeyPair": "",
-                "PreferredBackupWindow": "",
-                "PreferredMaintenanceWindow": "",
-                "S3LogUrl": "https://s3.amazonaws.com/<bucket-name>/automate-06-20160729133847520",
-                "SecurityGroupIds": [ "sg-1a24c270" ],
-                "ServerName": "automate-06",
-                "ServiceRoleArn": "arn:aws:iam::1019881987024:role/aws-opsworks-cm-service-role.1114810729735",
-                "Status": "OK",
-                "StatusDescription": "",
-                "SubnetIds": [ "subnet-49436a18" ],
-                "ToolsVersion": "string",
-                "UserArn": "arn:aws:iam::1019881987024:user/opsworks-user"
-            }
-        ],
-    }
-
-For more information, see `Back Up and Restore an AWS OpsWorks for Chef Automate Server`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Back Up and Restore an AWS OpsWorks for Chef Automate Server`: http://docs.aws.amazon.com/opsworks/latest/userguide/opscm-backup-restore.html