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

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

awscli/examples/opsworkscm/create-server.rst

@@ -1,48 +0,0 @@
-**To create a server**
-
-The following ``create-server`` example creates a new Chef Automate server named ``automate-06`` in your default region. Note that defaults are used for most other settings, such as number of backups to retain, and maintenance and backup start times. Before you run a ``create-server`` command, complete prerequisites in `Getting Started with AWS OpsWorks for Chef Automate <https://docs.aws.amazon.com/opsworks/latest/userguide/gettingstarted-opscm.html>`__ in the *AWS Opsworks for Chef Automate User Guide*. ::
-
-    aws opsworks-cm create-server \
-        --engine "Chef" \
-        --engine-model "Single" \
-        --engine-version "12" \
-        --server-name "automate-06" \
-        --instance-profile-arn "arn:aws:iam::1019881987024:instance-profile/aws-opsworks-cm-ec2-role" \
-        --instance-type "t2.medium" \
-        --key-pair "amazon-test" \
-        --service-role-arn "arn:aws:iam::044726508045:role/aws-opsworks-cm-service-role"
-
-The output shows you information similar to the following about the new server::
-
-    {
-        "Server": { 
-            "BackupRetentionCount": 10,
-            "CreatedAt": 2016-07-29T13:38:47.520Z,
-            "DisableAutomatedBackup": FALSE,
-            "Endpoint": "https://opsworks-cm.us-east-1.amazonaws.com",
-            "Engine": "Chef",
-            "EngineAttributes": [ 
-                { 
-                    "Name": "CHEF_DELIVERY_ADMIN_PASSWORD",
-                    "Value": "1Password1"
-                }
-            ],
-            "EngineModel": "Single",
-            "EngineVersion": "12",
-            "InstanceProfileArn": "arn:aws:iam::1019881987024:instance-profile/aws-opsworks-cm-ec2-role",
-            "InstanceType": "t2.medium",
-            "KeyPair": "amazon-test",
-            "MaintenanceStatus": "",
-            "PreferredBackupWindow": "Sun:02:00",
-            "PreferredMaintenanceWindow": "00:00",
-            "SecurityGroupIds": [ "sg-1a24c270" ],
-            "ServerArn": "arn:aws:iam::1019881987024:instance/automate-06-1010V4UU2WRM2",
-            "ServerName": "automate-06",
-            "ServiceRoleArn": "arn:aws:iam::1019881987024:role/aws-opsworks-cm-service-role",
-            "Status": "CREATING",
-            "StatusReason": "",
-            "SubnetIds": [ "subnet-49436a18" ]
-        }
-    }
-
-For more information, see `UpdateServer <https://docs.aws.amazon.com/opsworks-cm/latest/APIReference/API_UpdateServer.html>`_ in the *AWS OpsWorks for Chef Automate API Reference*.

awscli/examples/opsworkscm/delete-backup.rst

@@ -1,17 +0,0 @@
-**To delete backups**
-
-The following ``delete-backup`` command deletes a manual or automated backup of
-a Chef Automate server, identified by the backup ID. This command is useful when
-you are approaching the maximum number of backups that you can save, or you want
-to minimize your Amazon S3 storage costs.::
-
-  aws opsworks-cm delete-backup --backup-id "automate-06-2016-11-19T23:42:40.240Z"
-
-The output shows whether the backup deletion succeeded.
-
-**More Information**
-
-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
-

awscli/examples/opsworkscm/delete-server.rst

@@ -1,16 +0,0 @@
-**To delete servers**
-
-The following ``delete-server`` command deletes a Chef Automate server, identified
-by the server's name. After the server is deleted, it is no longer returned by
-``DescribeServer`` requests.::
-
-  aws opsworks-cm delete-server --server-name "automate-06"
-
-The output shows whether the server deletion succeeded.
-
-**More Information**
-
-For more information, see `Delete an AWS OpsWorks for Chef Automate Server`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Delete an AWS OpsWorks for Chef Automate Server`: http://docs.aws.amazon.com/opsworks/latest/userguide/opscm-delete-server.html
-

awscli/examples/opsworkscm/describe-account-attributes.rst

@@ -1,26 +0,0 @@
-**To describe account attributes**
-
-The following ``describe-account-attributes`` command returns information about your
-account's usage of AWS OpsWorks for Chef Automate resources.::
-
-  aws opsworks-cm describe-account-attributes
-
-The output for each account attribute entry returned by the command resembles the following.
-*Output*::
-
-  {
-   "Attributes": [ 
-      { 
-         "Maximum": 5,
-         "Name": "ServerLimit",
-         "Used": 2
-      }
-   ]
-  }
-
-**More Information**
-
-For more information, see `DescribeAccountAttributes`_ in the *AWS OpsWorks for Chef Automate API Reference*.
-
-.. _`DescribeAccountAttributes`: http://docs.aws.amazon.com/opsworks-cm/latest/APIReference/API_DescribeAccountAttributes.html
-

awscli/examples/opsworkscm/describe-backups.rst

@@ -1,44 +0,0 @@
-**To describe backups**
-
-The following ``describe-backups`` command returns information about all backups
-associated with your account in your default region. ::
-
-    aws opsworks-cm describe-backups
-
-The output for each backup entry returned by the command resembles the following.
-
-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": "Successful",
-                "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
-

awscli/examples/opsworkscm/describe-events.rst

@@ -1,21 +0,0 @@
-**To describe events**
-
-The following ``describe-events`` example returns information about all events that are associated with the specified Chef Automate server. ::
-
-    aws opsworks-cm describe-events \
-        --server-name 'automate-06'
-
-The output for each event entry returned by the command resembles the following example::
-
-    {
-        "ServerEvents": [ 
-            { 
-                "CreatedAt": 2016-07-29T13:38:47.520Z,
-                "LogUrl": "https://s3.amazonaws.com/<bucket-name>/automate-06-20160729133847520",
-                "Message": "Updates successfully installed.",
-                "ServerName": "automate-06"
-            }
-        ]
-    }
-
-For more information, see `General Troubleshooting Tips <https://docs.aws.amazon.com/opsworks/latest/userguide/troubleshoot-opscm.html#d0e4561>`_ in the *AWS OpsWorks User Guide*.

awscli/examples/opsworkscm/describe-node-association-status.rst

@@ -1,20 +0,0 @@
-**To describe node association status**
-
-The following ``describe-node-association-status`` command returns the status of a
-request to associate a node with a Chef Automate server named ``automate-06``.::
-
-  aws opsworks-cm describe-node-association-status --server-name "automate-06" --node-association-status-token "AflJKl+/GoKLZJBdDQEx0O65CDi57blQe9nKM8joSok0pQ9xr8DqApBN9/1O6sLdSvlfDEKkEx+eoCHvjoWHaOs="
-
-The output for each account attribute entry returned by the command resembles the following.
-*Output*::
-
-  {
-   "NodeAssociationStatus": "IN_PROGRESS"
-  }
-
-**More Information**
-
-For more information, see `DescribeNodeAssociationStatus`_ in the *AWS OpsWorks for Chef Automate API Reference*.
-
-.. _`DescribeNodeAssociationStatus`: http://docs.aws.amazon.com/opsworks-cm/latest/APIReference/API_DescribeNodeAssociationStatus.html
-

awscli/examples/opsworkscm/describe-servers.rst

@@ -1,48 +0,0 @@
-**To describe servers**
-
-The following ``describe-servers`` command returns information about all servers 
-that are associated with your account, and in your default region.::
-
-  aws opsworks-cm describe-servers
-
-The output for each server entry returned by the command resembles the following.
-*Output*::
-
-  {
-   "Servers": [ 
-      { 
-         "BackupRetentionCount": 8,
-         "CreatedAt": 2016-07-29T13:38:47.520Z,
-         "DisableAutomatedBackup": FALSE,
-         "Endpoint": "https://opsworks-cm.us-east-1.amazonaws.com",
-         "Engine": "Chef",
-         "EngineAttributes": [ 
-            { 
-               "Name": "CHEF_DELIVERY_ADMIN_PASSWORD",
-               "Value": "1Password1"
-            }
-         ],
-         "EngineModel": "Single",
-         "EngineVersion": "12",
-         "InstanceProfileArn": "arn:aws:iam::1019881987024:instance-profile/automate-06-1010V4UU2WRM2",
-         "InstanceType": "m4.large",
-         "KeyPair": "",
-         "MaintenanceStatus": "SUCCESS",
-         "PreferredBackupWindow": "03:00",
-         "PreferredMaintenanceWindow": "Mon:09:00",
-         "SecurityGroupIds": [ "sg-1a24c270" ],
-         "ServerArn": "arn:aws:iam::1019881987024:instance/automate-06-1010V4UU2WRM2",
-         "ServerName": "automate-06",
-         "ServiceRoleArn": "arn:aws:iam::1019881987024:role/aws-opsworks-cm-service-role.1114810729735",
-         "Status": "HEALTHY",
-         "StatusReason": "",
-         "SubnetIds": [ "subnet-49436a18" ]
-      }
-   ]
-  }
-
-**More Information**
-
-For more information, see `DescribeServers`_ in the *AWS OpsWorks for Chef Automate API Guide*.
-
-.. _`DescribeServers`: http://docs.aws.amazon.com/opsworks-cm/latest/APIReference/API_DescribeServers.html

awscli/examples/opsworkscm/disassociate-node.rst

@@ -1,19 +0,0 @@
-**To disassociate nodes**
-
-The following ``disassociate-node`` command disassociates a node named ``i-44de882p``, removing the node from
-management by a Chef Automate server named ``automate-06``. Valid node names are EC2 instance IDs.::
-
-  aws opsworks-cm disassociate-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 `Delete an AWS OpsWorks for Chef Automate Server`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Delete an AWS OpsWorks for Chef Automate Server`: http://docs.aws.amazon.com/opsworks/latest/userguide/opscm-delete-server.html

awscli/examples/opsworkscm/restore-server.rst

@@ -1,20 +0,0 @@
-**To restore a server**
-
-The following ``restore-server`` command performs an in-place restoration of a 
-Chef Automate server named ``automate-06`` in your default region from a backup
-with an ID of ``automate-06-2016-11-22T16:13:27.998Z``. Restoring a server restores
-connections to the nodes that the Chef Automate server was managing at the time 
-that the specified backup was performed.
-
-  aws opsworks-cm restore-server --backup-id "automate-06-2016-11-22T16:13:27.998Z" --server-name "automate-06"
-
-The output is the command ID only.
-*Output*::
-
-  (None)
-
-**More Information**
-
-For more information, see `Restore a Failed AWS OpsWorks for Chef Automate Server`_ in the *AWS OpsWorks User Guide*.
-
-.. _`Restore a Failed AWS OpsWorks for Chef Automate Server`: http://docs.aws.amazon.com/opsworks/latest/userguide/opscm-chef-restore.html

awscli/examples/opsworkscm/start-maintenance.rst

@@ -1,39 +0,0 @@
-**To start maintenance**
-
-The following ``start-maintenance`` example manually starts maintenance on the specified Chef Automate or Puppet Enterprise server in your default region. This command is useful if an earlier, automated maintenance attempt failed, and the underlying cause of maintenance failure has been resolved. ::
-
-    aws opsworks-cm start-maintenance \
-        --server-name 'automate-06'
-
-Output::
-
-    {
-        "Server": {
-            "AssociatePublicIpAddress": true,
-            "BackupRetentionCount": 10,
-            "ServerName": "automate-06",
-            "CreatedAt": 1569229584.842,
-            "CloudFormationStackArn": "arn:aws:cloudformation:us-west-2:123456789012:stack/aws-opsworks-cm-instance-automate-06-1606611794746/EXAMPLE0-31de-11eb-bdb0-0a5b0a1353b8",
-            "DisableAutomatedBackup": false,
-            "Endpoint": "automate-06-EXAMPLEvr8gjfk5f.us-west-2.opsworks-cm.io",
-            "Engine": "ChefAutomate",
-            "EngineModel": "Single",
-            "EngineAttributes": [],
-            "EngineVersion": "2020-07",
-            "InstanceProfileArn": "arn:aws:iam::123456789012:instance-profile/aws-opsworks-cm-ec2-role",
-            "InstanceType": "m5.large",
-            "PreferredMaintenanceWindow": "Sun:01:00",
-            "PreferredBackupWindow": "Sun:15:00",
-            "SecurityGroupIds": [
-                "sg-EXAMPLE"
-            ],
-            "ServiceRoleArn": "arn:aws:iam::123456789012:role/service-role/aws-opsworks-cm-service-role",
-            "Status": "UNDER_MAINTENANCE",
-            "SubnetIds": [
-                "subnet-EXAMPLE"
-            ],
-            "ServerArn": "arn:aws:opsworks-cm:us-west-2:123456789012:server/automate-06/0148382d-66b0-4196-8274-d1a2b6dff8d1"
-        }
-    }
-
-For more information, see `System Maintenance (Puppet Enterprise servers) <https://docs.aws.amazon.com/opsworks/latest/userguide/opspup-maintenance.html>`_ or `System Maintenance (Chef Automate servers) <https://docs.aws.amazon.com/opsworks/latest/userguide/opscm-maintenance.html>`_ in the *AWS OpsWorks User Guide*.