awscli 1.42.7__py3-none-any.whl → 1.44.26__py3-none-any.whl

awscli/examples/opsworks/describe-permissions.rst

@@ -1,26 +0,0 @@
-**To obtain a user's per-stack AWS OpsWorks permission level**
-
-The following example shows how to to obtain an AWS Identity and Access Management (IAM) user's permission level on a specified stack. ::
-
-  aws opsworks --region us-east-1 describe-permissions --iam-user-arn arn:aws:iam::123456789012:user/cli-user-test --stack-id d72553d4-8727-448c-9b00-f024f0ba1b06
-
-*Output*::
-
-  {
-    "Permissions": [
-      {
-        "StackId": "d72553d4-8727-448c-9b00-f024f0ba1b06", 
-        "IamUserArn": "arn:aws:iam::123456789012:user/cli-user-test", 
-        "Level": "manage", 
-        "AllowSudo": true, 
-        "AllowSsh": true
-      }
-    ]
-  }
-
-
-**More Information**
-
-For more information, see `Granting Per-Stack Permissions Levels`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Granting Per-Stack Permissions Levels`: http://docs.aws.amazon.com/opsworks/latest/userguide/opsworks-security-users-console.html

awscli/examples/opsworks/describe-raid-arrays.rst

@@ -1,31 +0,0 @@
-**To describe RAID arrays**
-
-The following example describes the RAID arrays attached to the instances in a specified stack. ::
-
-  aws opsworks --region us-east-1 describe-raid-arrays --stack-id d72553d4-8727-448c-9b00-f024f0ba1b06
-
-*Output*: The following is the output for a stack with one RAID array. ::
-
-  {
-    "RaidArrays": [
-      {
-        "StackId": "d72553d4-8727-448c-9b00-f024f0ba1b06", 
-        "AvailabilityZone": "us-west-2a", 
-        "Name": "Created for php-app1", 
-        "NumberOfDisks": 2, 
-        "InstanceId": "9f14adbc-ced5-43b6-bf01-e7d0db6cf2f7", 
-        "RaidLevel": 0, 
-        "VolumeType": "standard", 
-        "RaidArrayId": "f2d4e470-5972-4676-b1b8-bae41ec3e51c", 
-        "Device": "/dev/md0", 
-        "MountPoint": "/mnt/workspace", 
-        "CreatedAt": "2015-02-26T23:53:09+00:00", 
-        "Size": 100
-      } 
-    ]
-  }
-
-For more information, see `EBS Volumes`_ in the *AWS OpsWorks User Guide*.
-
-.. _`EBS Volumes`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinglayers-basics-edit.html#workinglayers-basics-edit-ebs
-

awscli/examples/opsworks/describe-rds-db-instances.rst

@@ -1,29 +0,0 @@
-**To describe a stack's registered Amazon RDS instances**
-
-The following example describes the Amazon RDS instances registered with a specified stack. ::
-
-  aws opsworks --region us-east-1 describe-rds-db-instances --stack-id d72553d4-8727-448c-9b00-f024f0ba1b06
-
-*Output*: The following is the output for a stack with one registered RDS instance. ::
-
-  {
-    "RdsDbInstances": [
-      {
-        "Engine": "mysql", 
-        "StackId": "d72553d4-8727-448c-9b00-f024f0ba1b06", 
-        "MissingOnRds": false, 
-        "Region": "us-west-2", 
-        "RdsDbInstanceArn": "arn:aws:rds:us-west-2:123456789012:db:clitestdb", 
-        "DbPassword": "*****FILTERED*****", 
-        "Address": "clitestdb.cdlqlk5uwd0k.us-west-2.rds.amazonaws.com", 
-        "DbUser": "cliuser", 
-        "DbInstanceIdentifier": "clitestdb"
-      }
-    ]
-  }
-
-
-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/describe-stack-provisioning-parameters.rst

@@ -1,32 +0,0 @@
-**To return the provisioning parameters for a stack**
-
-The following ``describe-stack-provisioning-parameters`` example returns the provisioning parameters for a specified stack. Provisioning parameters include settings such as the agent installation location and public key that OpsWorks uses to manage the agent on instances in a stack. ::
-
-    aws opsworks describe-stack-provisioning-parameters \
-        --stack-id 62744d97-6faf-4ecb-969b-a086fEXAMPLE
-
-Output::
-
-    {
-        "AgentInstallerUrl": "https://opsworks-instance-agent-us-west-2.s3.amazonaws.com/ID_number/opsworks-agent-installer.tgz",
-        "Parameters": {
-            "agent_installer_base_url": "https://opsworks-instance-agent-us-west-2.s3.amazonaws.com",
-            "agent_installer_tgz": "opsworks-agent-installer.tgz",
-            "assets_download_bucket": "opsworks-instance-assets-us-west-2.s3.amazonaws.com",
-            "charlie_public_key": "-----BEGIN PUBLIC KEY-----PUBLIC_KEY_EXAMPLE\n-----END PUBLIC KEY-----",
-            "instance_service_endpoint": "opsworks-instance-service.us-west-2.amazonaws.com",
-            "instance_service_port": "443",
-            "instance_service_region": "us-west-2",
-            "instance_service_ssl_verify_peer": "true",
-            "instance_service_use_ssl": "true",
-            "ops_works_endpoint": "opsworks.us-west-2.amazonaws.com",
-            "ops_works_port": "443",
-            "ops_works_region": "us-west-2",
-            "ops_works_ssl_verify_peer": "true",
-            "ops_works_use_ssl": "true",
-            "verbose": "false",
-            "wait_between_runs": "30"
-        }
-    }
-
-For more information, see `Run Stack Commands <https://docs.aws.amazon.com/opsworks/latest/userguide/workingstacks-commands.html>`__ in the *AWS OpsWorks User Guide*.

awscli/examples/opsworks/describe-stack-summary.rst

@@ -1,27 +0,0 @@
-**To describe a stack's configuration**
-
-The following ``describe-stack-summary`` command returns a summary of the specified stack's configuration. ::
-
-  aws opsworks --region us-east-1 describe-stack-summary --stack-id 8c428b08-a1a1-46ce-a5f8-feddc43771b8
-
-*Output*::
-
-  {
-    "StackSummary": {
-      "StackId": "8c428b08-a1a1-46ce-a5f8-feddc43771b8",
-      "InstancesCount": {
-        "Booting": 1
-      },
-      "Name": "CLITest",
-      "AppsCount": 1,
-      "LayersCount": 1,
-      "Arn": "arn:aws:opsworks:us-west-2:123456789012:stack/8c428b08-a1a1-46ce-a5f8-feddc43771b8/"
-    }
-  }
-
-**More Information**
-
-For more information, see `Stacks`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Stacks`: http://docs.aws.amazon.com/opsworks/latest/userguide/workingstacks.html
-

awscli/examples/opsworks/describe-stacks.rst

@@ -1,65 +0,0 @@
-**To describe stacks**
-
-The following ``describe-stacks`` command describes an account's stacks. ::
-
-  aws opsworks --region us-east-1 describe-stacks
-
-*Output*::
-
-  {
-    "Stacks": [
-      {
-        "ServiceRoleArn": "arn:aws:iam::444455556666:role/aws-opsworks-service-role",
-        "StackId": "aeb7523e-7c8b-49d4-b866-03aae9d4fbcb",
-        "DefaultRootDeviceType": "instance-store",
-        "Name": "TomStack-sd",
-        "ConfigurationManager": {
-          "Version": "11.4",
-          "Name": "Chef"
-        },
-        "UseCustomCookbooks": true,
-        "CustomJson": "{\n  \"tomcat\": {\n    \"base_version\": 7,\n    \"java_opts\": \"-Djava.awt.headless=true -Xmx256m\"\n  },\n  \"datasources\": {\n    \"ROOT\": \"jdbc/mydb\"\n  }\n}",
-        "Region": "us-east-1",
-        "DefaultInstanceProfileArn": "arn:aws:iam::444455556666:instance-profile/aws-opsworks-ec2-role",
-        "CustomCookbooksSource": {
-          "Url": "git://github.com/example-repo/tomcustom.git",
-          "Type": "git"
-        },
-        "DefaultAvailabilityZone": "us-east-1a",
-        "HostnameTheme": "Layer_Dependent",
-        "Attributes": {
-          "Color": "rgb(45, 114, 184)"
-        },
-        "DefaultOs": "Amazon Linux",
-        "CreatedAt": "2013-08-01T22:53:42+00:00"
-      },
-      {
-        "ServiceRoleArn": "arn:aws:iam::444455556666:role/aws-opsworks-service-role",
-        "StackId": "40738975-da59-4c5b-9789-3e422f2cf099",
-        "DefaultRootDeviceType": "instance-store",
-        "Name": "MyStack",
-        "ConfigurationManager": {
-          "Version": "11.4",
-          "Name": "Chef"
-        },
-        "UseCustomCookbooks": false,
-        "Region": "us-east-1",
-        "DefaultInstanceProfileArn": "arn:aws:iam::444455556666:instance-profile/aws-opsworks-ec2-role",
-        "CustomCookbooksSource": {},
-        "DefaultAvailabilityZone": "us-east-1a",
-        "HostnameTheme": "Layer_Dependent",
-        "Attributes": {
-          "Color": "rgb(45, 114, 184)"
-        },
-        "DefaultOs": "Amazon Linux",
-        "CreatedAt": "2013-10-25T19:24:30+00:00"
-      }
-    ]
-  }
-
-**More Information**
-
-For more information, see `Stacks`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Stacks`: http://docs.aws.amazon.com/opsworks/latest/userguide/workingstacks.html
-

awscli/examples/opsworks/describe-timebased-auto-scaling.rst

@@ -1,39 +0,0 @@
-**To describe the time-based scaling configuration of an instance**
-
-The following example describes a specified instance's time-based scaling configuration.
-The instance is identified by its instance ID, which you can find on the instances's
-details page or by running ``describe-instances``. ::
-
-  aws opsworks describe-time-based-auto-scaling --region us-east-1 --instance-ids 701f2ffe-5d8e-4187-b140-77b75f55de8d
-
-*Output*: The example has a single time-based instance. :: 
-
-  {
-    "TimeBasedAutoScalingConfigurations": [
-     {
-        "InstanceId": "701f2ffe-5d8e-4187-b140-77b75f55de8d", 
-        "AutoScalingSchedule": {
-          "Monday": {
-            "11": "on", 
-            "10": "on", 
-            "13": "on", 
-            "12": "on" 
-          }, 
-          "Tuesday": {
-            "11": "on", 
-            "10": "on", 
-            "13": "on", 
-            "12": "on" 
-          } 
-        }
-      }
-    ]
-  }
-
-
-
-**More Information**
-
-For more information, see `How Automatic Time-based Scaling Works`_ in the *AWS OpsWorks User Guide*.
-
-.. _`How Automatic Time-based Scaling Works`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-autoscaling.html#workinginstances-autoscaling-timebased

awscli/examples/opsworks/describe-user-profiles.rst

@@ -1,32 +0,0 @@
-**To describe user profiles**
-
-The following ``describe-user-profiles`` command describes the account's user profiles. ::
-
-  aws opsworks --region us-east-1 describe-user-profiles
-
-*Output*::
-
-  {
-    "UserProfiles": [
-      {
-        "IamUserArn": "arn:aws:iam::123456789012:user/someuser",
-        "SshPublicKey": "ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAQEAkOuP7i80q3Cko...",
-        "AllowSelfManagement": true,
-        "Name": "someuser",
-        "SshUsername": "someuser"
-      },
-      {
-        "IamUserArn": "arn:aws:iam::123456789012:user/cli-user-test",
-        "AllowSelfManagement": true,
-        "Name": "cli-user-test",
-        "SshUsername": "myusername"
-      }
-    ]
-  }
-
-**More Information**
-
-For more information, see `Managing AWS OpsWorks Users`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Managing AWS OpsWorks Users`: http://docs.aws.amazon.com/opsworks/latest/userguide/opsworks-security-users-manage.html
-

awscli/examples/opsworks/describe-volumes.rst

@@ -1,31 +0,0 @@
-**To describe a stack's volumes**
-
-The following example describes a stack's EBS volumes. ::
-
-  aws opsworks --region us-east-1 describe-volumes --stack-id 8c428b08-a1a1-46ce-a5f8-feddc43771b8
-
-*Output*::
-
-  {
-    "Volumes": [
-      {
-        "Status": "in-use",
-        "AvailabilityZone": "us-west-2a",
-        "Name": "CLITest",
-        "InstanceId": "dfe18b02-5327-493d-91a4-c5c0c448927f",
-        "VolumeType": "standard",
-        "VolumeId": "56b66fbd-e1a1-4aff-9227-70f77118d4c5",
-        "Device": "/dev/sdi",
-        "Ec2VolumeId": "vol-295c1638",
-        "MountPoint": "/mnt/myvolume",
-        "Size": 1
-      }
-    ]
-  }
-
-**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/detach-elastic-load-balancer.rst

@@ -1,14 +0,0 @@
-**To detach a load balancer from its layer**
-
-The following example detaches a load balancer, identified by its name, from its layer. ::
-
-  aws opsworks --region us-east-1 detach-elastic-load-balancer --elastic-load-balancer-name Java-LB --layer-id 888c5645-09a5-4d0e-95a8-812ef1db76a4 
-
-*Output*: None.
-
-**More Information**
-
-For more information, see `Elastic Load Balancing`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Elastic Load Balancing`: http://docs.aws.amazon.com/opsworks/latest/userguide/load-balancer-elb.html
-

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
-