awscli 1.37.3__py3-none-any.whl → 1.37.4__py3-none-any.whl

awscli/__init__.py

@@ -18,7 +18,7 @@ A Universal Command Line Environment for Amazon Web Services.
 
 import os
 
-__version__ = '1.37.3'
+__version__ = '1.37.4'
 
 #
 # Get our data path to be added to botocore's search path

awscli/examples/cloudfront/create-distribution-with-tags.rst

@@ -1,20 +1,16 @@
 **To create a CloudFront distribution with tags**
 
-The following example creates a distribution with two tags by providing the
-distribution configuration and tags in a JSON file named
-``dist-config-with-tags.json``::
+The following ``create-distribution-with-tags`` example creates a distribution with two tags by providing the distribution configuration and tags in a JSON file named ``dist-config-with-tags.json``. ::
 
     aws cloudfront create-distribution-with-tags \
         --distribution-config-with-tags file://dist-config-with-tags.json
 
-The file ``dist-config-with-tags.json`` is a JSON document in the current
-folder that contains the following. Note the ``Tags`` object at the top of
-the file, which contains two tags:
+The file ``dist-config-with-tags.json`` is a JSON document in the current folder. Note the ``Tags`` object at the top of the file, which contains two tags:
 
 - ``Name = ExampleDistribution``
 - ``Project = ExampleProject``
 
-::
+Contents of ``dist-config-with-tags.json``::
 
     {
         "Tags": {
@@ -39,8 +35,8 @@ the file, which contains two tags:
                 "Quantity": 1,
                 "Items": [
                     {
-                        "Id": "awsexamplebucket.s3.amazonaws.com-cli-example",
-                        "DomainName": "awsexamplebucket.s3.amazonaws.com",
+                        "Id": "amzn-s3-demo-bucket.s3.amazonaws.com-cli-example",
+                        "DomainName": "amzn-s3-demo-bucket.s3.amazonaws.com",
                         "OriginPath": "",
                         "CustomHeaders": {
                             "Quantity": 0
@@ -55,7 +51,7 @@ the file, which contains two tags:
                 "Quantity": 0
             },
             "DefaultCacheBehavior": {
-                "TargetOriginId": "awsexamplebucket.s3.amazonaws.com-cli-example",
+                "TargetOriginId": "amzn-s3-demo-bucket.s3.amazonaws.com-cli-example",
                 "ForwardedValues": {
                     "QueryString": false,
                     "Cookies": {
@@ -155,8 +151,8 @@ Output::
                     "Quantity": 1,
                     "Items": [
                         {
-                            "Id": "awsexamplebucket.s3.amazonaws.com-cli-example",
-                            "DomainName": "awsexamplebucket.s3.amazonaws.com",
+                            "Id": "amzn-s3-demo-bucket.s3.amazonaws.com-cli-example",
+                            "DomainName": "amzn-s3-demo-bucket.s3.amazonaws.com",
                             "OriginPath": "",
                             "CustomHeaders": {
                                 "Quantity": 0
@@ -171,7 +167,7 @@ Output::
                     "Quantity": 0
                 },
                 "DefaultCacheBehavior": {
-                    "TargetOriginId": "awsexamplebucket.s3.amazonaws.com-cli-example",
+                    "TargetOriginId": "amzn-s3-demo-bucket.s3.amazonaws.com-cli-example",
                     "ForwardedValues": {
                         "QueryString": false,
                         "Cookies": {

awscli/examples/cloudfront/get-distribution.rst

@@ -1,13 +1,9 @@
 **To get a CloudFront distribution**
 
-The following example gets the CloudFront distribution with the ID
-``EDFDVBD6EXAMPLE``, including its ``ETag``. The distribution ID is returned in
-the `create-distribution <create-distribution.html>`_ and `list-distributions
-<list-distributions.html>`_ commands.
+The following ``get-distribution`` example gets the CloudFront distribution with the ID ``EDFDVBD6EXAMPLE``, including its ``ETag``. The distribution ID is returned in the `create-distribution <create-distribution.html>`__ and `list-distributions <list-distributions.html>`__ commands. ::
 
-::
-
-    aws cloudfront get-distribution --id EDFDVBD6EXAMPLE
+    aws cloudfront get-distribution \
+        --id EDFDVBD6EXAMPLE
 
 Output::
 
@@ -34,8 +30,8 @@ Output::
                     "Quantity": 1,
                     "Items": [
                         {
-                            "Id": "awsexamplebucket.s3.amazonaws.com-cli-example",
-                            "DomainName": "awsexamplebucket.s3.amazonaws.com",
+                            "Id": "amzn-s3-demo-bucket.s3.amazonaws.com-cli-example",
+                            "DomainName": "amzn-s3-demo-bucket.s3.amazonaws.com",
                             "OriginPath": "",
                             "CustomHeaders": {
                                 "Quantity": 0
@@ -50,7 +46,7 @@ Output::
                     "Quantity": 0
                 },
                 "DefaultCacheBehavior": {
-                    "TargetOriginId": "awsexamplebucket.s3.amazonaws.com-cli-example",
+                    "TargetOriginId": "amzn-s3-demo-bucket.s3.amazonaws.com-cli-example",
                     "ForwardedValues": {
                         "QueryString": false,
                         "Cookies": {

awscli/examples/cloudtrail/put-event-selectors.rst

@@ -119,7 +119,7 @@ The following example creates an event selector for a trail named ``TrailName``
 
     aws cloudtrail put-event-selectors \
         --trail-name TrailName \
-        --event-selectors '[{"ReadWriteType": "All","IncludeManagementEvents": true,"DataResources": [{"Type":"AWS::S3::Object", "Values": ["arn:aws:s3:::mybucket/prefix","arn:aws:s3:::mybucket2/prefix2"]},{"Type": "AWS::Lambda::Function","Values": ["arn:aws:lambda:us-west-2:999999999999:function:hello-world-python-function"]}]}]'
+        --event-selectors '[{"ReadWriteType": "All","IncludeManagementEvents": true,"DataResources": [{"Type":"AWS::S3::Object", "Values": ["arn:aws:s3:::mybucket/prefix","arn:aws:s3:::amzn-s3-demo-bucket2/prefix2"]},{"Type": "AWS::Lambda::Function","Values": ["arn:aws:lambda:us-west-2:999999999999:function:hello-world-python-function"]}]}]'
 
 Output::
 
@@ -131,7 +131,7 @@ Output::
                     {
                         "Values": [
                             "arn:aws:s3:::mybucket/prefix",
-                            "arn:aws:s3:::mybucket2/prefix2"
+                            "arn:aws:s3:::amzn-s3-demo-bucket2/prefix2"
                         ],
                         "Type": "AWS::S3::Object"
                     },

awscli/examples/deploy/batch-get-deployments.rst

@@ -26,7 +26,7 @@ Output::
                     "s3Location": {
                     "bundleType": "zip",
                     "version": "uTecLusEXAMPLEFXtfUcyfV8bEXAMPLE",
-                    "bucket": "CodeDeployDemoBucket",
+                    "bucket": "amzn-s3-demo-bucket",
                     "key": "WordPressApp.zip"
                     }
                 },
@@ -56,7 +56,7 @@ Output::
                     "s3Location": {
                     "bundleType": "zip",
                     "eTag": "\"dd56cfdEXAMPLE8e768f9d77fEXAMPLE\"",
-                    "bucket": "CodeDeployDemoBucket",
+                    "bucket": "amzn-s3-demo-bucket",
                     "key": "MyOtherApp.zip"
                     }
                 },

awscli/examples/deploy/create-deployment.rst

@@ -7,7 +7,7 @@ The following ``create-deployment`` example creates a deployment and associates
         --deployment-config-name CodeDeployDefault.OneAtATime \
         --deployment-group-name WordPress_DG \
         --description "My demo deployment" \
-        --s3-location bucket=CodeDeployDemoBucket,bundleType=zip,eTag=dd56cfdEXAMPLE8e768f9d77fEXAMPLE,key=WordPressApp.zip
+        --s3-location bucket=amzn-s3-demo-bucket,bundleType=zip,eTag=dd56cfdEXAMPLE8e768f9d77fEXAMPLE,key=WordPressApp.zip
 
 Output::
 

awscli/examples/deploy/get-application-revision.rst

@@ -4,7 +4,7 @@ The following ``get-application-revision`` example displays information about an
 
     aws deploy get-application-revision \
         --application-name WordPress_App \
-        --s3-location bucket=CodeDeployDemoBucket,bundleType=zip,eTag=dd56cfdEXAMPLE8e768f9d77fEXAMPLE,key=WordPressApp.zip
+        --s3-location bucket=amzn-s3-demo-bucket,bundleType=zip,eTag=dd56cfdEXAMPLE8e768f9d77fEXAMPLE,key=WordPressApp.zip
 
 Output::
 
@@ -22,7 +22,7 @@ Output::
             "s3Location": {
                 "bundleType": "zip",
                 "eTag": "dd56cfdEXAMPLE8e768f9d77fEXAMPLE",
-                "bucket": "CodeDeployDemoBucket",
+                "bucket": "amzn-s3-demo-bucket",
                 "key": "WordPressApp.zip"
             }
         }

awscli/examples/deploy/get-deployment.rst

@@ -25,7 +25,7 @@ Output::
                 "s3Location":  {
                 "bundleType": "zip",
                 "eTag": "\"dd56cfdEXAMPLE8e768f9d77fEXAMPLE\"",
-                "bucket": "CodeDeployDemoBucket",
+                "bucket": "amzn-s3-demo-bucket",
                 "key": "WordPressApp.zip"
                 }
             },

awscli/examples/deploy/list-application-revisions.rst

@@ -4,7 +4,7 @@ The following ``list-application-revisions`` example displays information about
 
     aws deploy list-application-revisions \
         --application-name WordPress_App \
-        --s-3-bucket CodeDeployDemoBucket \
+        --s-3-bucket amzn-s3-demo-bucket \
         --deployed exclude \
         --s-3-key-prefix WordPress_ \
         --sort-by lastUsedTime \
@@ -18,7 +18,7 @@ Output::
                 "revisionType": "S3",
                 "s3Location": {
                     "version": "uTecLusvCB_JqHFXtfUcyfV8bEXAMPLE",
-                    "bucket": "CodeDeployDemoBucket",
+                    "bucket": "amzn-s3-demo-bucket",
                     "key": "WordPress_App.zip",
                     "bundleType": "zip"
                 }
@@ -27,7 +27,7 @@ Output::
                 "revisionType": "S3",
                 "s3Location": {
                     "version": "tMk.UxgDpMEVb7V187ZM6wVAWEXAMPLE",
-                    "bucket": "CodeDeployDemoBucket",
+                    "bucket": "amzn-s3-demo-bucket",
                     "key": "WordPress_App_2-0.zip",
                     "bundleType": "zip"
                 }

awscli/examples/deploy/push.rst

@@ -6,10 +6,10 @@ The following ``push`` example bundles and deploys an application revision to Am
         --application-name WordPress_App \
         --description "This is my deployment" \
         --ignore-hidden-files \
-        --s3-location s3://CodeDeployDemoBucket/WordPressApp.zip \
+        --s3-location s3://amzn-s3-demo-bucket/WordPressApp.zip \
         --source /tmp/MyLocalDeploymentFolder/
 
 The output describes how to use the ``create-deployment`` command to create a deployment that uses the uploaded application revision. ::
 
     To deploy with this revision, run: 
-    aws deploy create-deployment --application-name WordPress_App --deployment-config-name <deployment-config-name> --deployment-group-name <deployment-group-name> --s3-location bucket=CodeDeployDemoBucket,key=WordPressApp.zip,bundleType=zip,eTag="cecc9b8EXAMPLE50a6e71fdb88EXAMPLE",version=LFsJAUdEXAMPLEfvKtvi79L8EXAMPLE
+    aws deploy create-deployment --application-name WordPress_App --deployment-config-name <deployment-config-name> --deployment-group-name <deployment-group-name> --s3-location bucket=amzn-s3-demo-bucket,key=WordPressApp.zip,bundleType=zip,eTag="cecc9b8EXAMPLE50a6e71fdb88EXAMPLE",version=LFsJAUdEXAMPLEfvKtvi79L8EXAMPLE

awscli/examples/deploy/register-application-revision.rst

@@ -5,6 +5,6 @@ The following ``register-application-revision`` example registers information ab
     aws deploy register-application-revision \
         --application-name WordPress_App \
         --description "Revised WordPress application" \
-        --s3-location bucket=CodeDeployDemoBucket,key=RevisedWordPressApp.zip,bundleType=zip,eTag=cecc9b8a08eac650a6e71fdb88EXAMPLE
+        --s3-location bucket=amzn-s3-demo-bucket,key=RevisedWordPressApp.zip,bundleType=zip,eTag=cecc9b8a08eac650a6e71fdb88EXAMPLE
 
 This command produces no output.

awscli/examples/ec2/accept-address-transfer.rst

@@ -18,4 +18,4 @@ Output::
         }
     }
 
-For more information, see `Transfer Elastic IP addresses <https://docs.aws.amazon.com/vpc/latest/userguide/vpc-eips.html#transfer-EIPs-intro>`__ in the *Amazon VPC User Guide*.
+For more information, see `Transfer Elastic IP addresses <https://docs.aws.amazon.com/vpc/latest/userguide/WorkWithEIPs.html#transfer-EIPs-intro>`__ in the *Amazon VPC User Guide*.

awscli/examples/ec2/allocate-hosts.rst

@@ -1,55 +1,55 @@
-**Example 1: To allocate a Dedicated Host**
-
-The following ``allocate-hosts`` example allocates a single Dedicated Host in the ``eu-west-1a`` Availability Zone, onto which you can launch ``m5.large`` instances. By default, the Dedicated Host accepts only target instance launches, and does not support host recovery. ::
-
-    aws ec2 allocate-hosts \
-        --instance-type m5.large \
-        --availability-zone eu-west-1a \
-        --quantity 1
-
-Output::
-
-    {
-        "HostIds": [
-            "h-07879acf49EXAMPLE"
-        ]
-    }
-
-**Example 2: To allocate a Dedicated Host with auto-placement and host recovery enabled**
-
-The following ``allocate-hosts`` example allocates a single Dedicated Host in the ``eu-west-1a`` Availability Zone with auto-placement and host recovery enabled. ::
-
-    aws ec2 allocate-hosts \
-        --instance-type m5.large \
-        --availability-zone eu-west-1a \
-        --auto-placement on \
-        --host-recovery on \
-        --quantity 1
-
-Output::
-
-   {
-        "HostIds": [
-            "h-07879acf49EXAMPLE"
-        ]
-   }
-
-**Example 3: To allocate a Dedicated Host with tags**
-
-The following ``allocate-hosts`` example allocates a single Dedicated Host and applies a tag with a key named ``purpose`` and a value of ``production``. ::
-
-    aws ec2 allocate-hosts \
-        --instance-type m5.large \
-        --availability-zone eu-west-1a \
-        --quantity 1 \
-        --tag-specifications 'ResourceType=dedicated-host,Tags={Key=purpose,Value=production}'
-
-Output::
-
-    {
-        "HostIds": [
-            "h-07879acf49EXAMPLE"
-        ]
-    }
-
-For more information, see `Allocating Dedicated Hosts <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/how-dedicated-hosts-work.html#dedicated-hosts-allocating>`__ in the *Amazon Elastic Compute Cloud User Guide for Linux Instances*.
+**Example 1: To allocate a Dedicated Host**
+
+The following ``allocate-hosts`` example allocates a single Dedicated Host in the ``eu-west-1a`` Availability Zone, onto which you can launch ``m5.large`` instances. By default, the Dedicated Host accepts only target instance launches, and does not support host recovery. ::
+
+    aws ec2 allocate-hosts \
+        --instance-type m5.large \
+        --availability-zone eu-west-1a \
+        --quantity 1
+
+Output::
+
+    {
+        "HostIds": [
+            "h-07879acf49EXAMPLE"
+        ]
+    }
+
+**Example 2: To allocate a Dedicated Host with auto-placement and host recovery enabled**
+
+The following ``allocate-hosts`` example allocates a single Dedicated Host in the ``eu-west-1a`` Availability Zone with auto-placement and host recovery enabled. ::
+
+    aws ec2 allocate-hosts \
+        --instance-type m5.large \
+        --availability-zone eu-west-1a \
+        --auto-placement on \
+        --host-recovery on \
+        --quantity 1
+
+Output::
+
+   {
+        "HostIds": [
+            "h-07879acf49EXAMPLE"
+        ]
+   }
+
+**Example 3: To allocate a Dedicated Host with tags**
+
+The following ``allocate-hosts`` example allocates a single Dedicated Host and applies a tag with a key named ``purpose`` and a value of ``production``. ::
+
+    aws ec2 allocate-hosts \
+        --instance-type m5.large \
+        --availability-zone eu-west-1a \
+        --quantity 1 \
+        --tag-specifications 'ResourceType=dedicated-host,Tags={Key=purpose,Value=production}'
+
+Output::
+
+    {
+        "HostIds": [
+            "h-07879acf49EXAMPLE"
+        ]
+    }
+
+For more information, see `Allocate a Dedicated Host <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-hosts-allocating.html>`__ in the *Amazon EC2 User Guide*.

awscli/examples/ec2/associate-address.rst

@@ -1,35 +1,44 @@
-**To associate an Elastic IP addresses in EC2-Classic**
-
-This example associates an Elastic IP address with an instance in EC2-Classic. If the command succeeds, no output is returned.
-
-Command::
-
-  aws ec2 associate-address --instance-id i-07ffe74c7330ebf53 --public-ip 198.51.100.0
-
-**To associate an Elastic IP address in EC2-VPC**
-
-This example associates an Elastic IP address with an instance in a VPC.
-
-Command::
-
-  aws ec2 associate-address --instance-id i-0b263919b6498b123 --allocation-id eipalloc-64d5890a
-
-Output::
-
-  {
-      "AssociationId": "eipassoc-2bebb745"
-  }
-
-This example associates an Elastic IP address with a network interface.
-
-Command::
-
-  aws ec2 associate-address --allocation-id eipalloc-64d5890a --network-interface-id eni-1a2b3c4d
-
-This example associates an Elastic IP with a private IP address that's associated with a network interface.
-
-Command::
-
-  aws ec2 associate-address --allocation-id eipalloc-64d5890a --network-interface-id eni-1a2b3c4d --private-ip-address 10.0.0.85
-
- 
+**Example 1: To associate an Elastic IP address with an instance**
+
+The following ``associate-address`` example associates an Elastic IP address with the specified EC2 instance. ::
+
+    aws ec2 associate-address \
+        --instance-id i-0b263919b6498b123 \
+        --allocation-id eipalloc-64d5890a
+
+Output::
+
+    {
+        "AssociationId": "eipassoc-2bebb745"
+    }
+
+**Example 2: To associate an Elastic IP address with a network interface**
+
+The following ``associate-address`` example associates the specified Elastic IP address with the specified network interface. ::
+
+    aws ec2 associate-address 
+        --allocation-id eipalloc-64d5890a \
+        --network-interface-id eni-1a2b3c4d
+
+Output::
+
+    {
+        "AssociationId": "eipassoc-2bebb745"
+    }
+
+**Example 3: To associate an Elastic IP address with a private IP address**
+
+The following ``associate-address`` example associates the specified Elastic IP address with the specified private IP address in the specified network interface. ::
+
+    aws ec2 associate-address \
+        --allocation-id eipalloc-64d5890a \
+        --network-interface-id eni-1a2b3c4d \
+        --private-ip-address 10.0.0.85
+
+Output::
+
+    {
+        "AssociationId": "eipassoc-2bebb745"
+    }
+
+For more information, see `Elastic IP addresses <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html>`__ in the *Amazon EC2 User Guide*.

awscli/examples/ec2/authorize-security-group-egress.rst

@@ -1,23 +1,56 @@
-**To add a rule that allows outbound traffic to a specific address range**
-
-This example command adds a rule that grants access to the specified address ranges on TCP port 80.
-
-Command (Linux)::
-
-  aws ec2 authorize-security-group-egress --group-id sg-1a2b3c4d --ip-permissions IpProtocol=tcp,FromPort=80,ToPort=80,IpRanges='[{CidrIp=10.0.0.0/16}]'
-
-Command (Windows)::
-
-  aws ec2 authorize-security-group-egress --group-id sg-1a2b3c4d --ip-permissions IpProtocol=tcp,FromPort=80,ToPort=80,IpRanges=[{CidrIp=10.0.0.0/16}]
-
-**To add a rule that allows outbound traffic to a specific security group**
-
-This example command adds a rule that grants access to the specified security group on TCP port 80.
-
-Command (Linux)::
-
-  aws ec2 authorize-security-group-egress --group-id sg-1a2b3c4d --ip-permissions IpProtocol=tcp,FromPort=80,ToPort=80,UserIdGroupPairs='[{GroupId=sg-4b51a32f}]' 
-
-Command (Windows)::
-
-  aws ec2 authorize-security-group-egress --group-id sg-1a2b3c4d --ip-permissions IpProtocol=tcp,FromPort=80,ToPort=80,UserIdGroupPairs=[{GroupId=sg-4b51a32f}]
+**Example 1: To add a rule that allows outbound traffic to a specific address range**
+
+The following ``authorize-security-group-egress`` example adds a rule that grants access to the specified address ranges on TCP port 80. ::
+
+    aws ec2 authorize-security-group-egress \
+        --group-id sg-1234567890abcdef0 \
+        --ip-permissions 'IpProtocol=tcp,FromPort=80,ToPort=80,IpRanges=[{CidrIp=10.0.0.0/16}]'
+
+Output::
+
+    {
+        "Return": true,
+        "SecurityGroupRules": [
+            {
+                "SecurityGroupRuleId": "sgr-0b15794cdb17bf29c",
+                "GroupId": "sg-1234567890abcdef0",
+                "GroupOwnerId": "123456789012",
+                "IsEgress": true,
+                "IpProtocol": "tcp",
+                "FromPort": 80,
+                "ToPort": 80,
+                "CidrIpv4": "10.0.0.0/16"
+            }
+        ]
+    }
+
+**Example 2: To add a rule that allows outbound traffic to a specific security group**
+
+The following ``authorize-security-group-egress`` example adds a rule that grants access to the specified security group on TCP port 80. ::
+
+    aws ec2 authorize-security-group-egress \
+        --group-id sg-1234567890abcdef0 \
+        --ip-permissions 'IpProtocol=tcp,FromPort=80,ToPort=80,UserIdGroupPairs=[{GroupId=sg-0aad1c26bbeec5c22}]'
+
+Output::
+
+    {
+        "Return": true,
+        "SecurityGroupRules": [
+            {
+                "SecurityGroupRuleId": "sgr-0b5dd815afcea9cc3",
+                "GroupId": "sg-1234567890abcdef0",
+                "GroupOwnerId": "123456789012",
+                "IsEgress": true,
+                "IpProtocol": "tcp",
+                "FromPort": 80,
+                "ToPort": 80,
+                "ReferencedGroupInfo": {
+                    "GroupId": "sg-0aad1c26bbeec5c22",
+                    "UserId": "123456789012"
+                }
+            }
+        ]
+    }
+
+For more information, see `Security groups <https://docs.aws.amazon.com/vpc/latest/userguide/vpc-security-groups.html>`__ in the *Amazon VPC User Guide*.

awscli/examples/ec2/authorize-security-group-ingress.rst

@@ -59,11 +59,11 @@ Output::
 
 **Example 3: To add multiple rules in the same call**
 
-The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add two inbound rules, one that enables inbound access on TCP port 3389 (RDP) and the other that enables ping/ICMP.  
+The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add two inbound rules, one that enables inbound access on TCP port 3389 (RDP) and the other that enables ping/ICMP. ::
 
     aws ec2 authorize-security-group-ingress \
         --group-id sg-1234567890abcdef0 \
-        --ip-permissions IpProtocol=tcp,FromPort=3389,ToPort=3389,IpRanges="[{CidrIp=172.31.0.0/16}]" IpProtocol=icmp,FromPort=-1,ToPort=-1,IpRanges="[{CidrIp=172.31.0.0/16}]"
+        --ip-permissions 'IpProtocol=tcp,FromPort=3389,ToPort=3389,IpRanges=[{CidrIp=172.31.0.0/16}]" "IpProtocol=icmp,FromPort=-1,ToPort=-1,IpRanges=[{CidrIp=172.31.0.0/16}]'
 
 Output::
 
@@ -92,14 +92,14 @@ Output::
             }
         ]
     }
-  
+
 **Example 4: To add a rule for ICMP traffic**
 
-The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add an inbound rule that allows the ICMP message ``Destination Unreachable: Fragmentation Needed and Don't Fragment was Set`` (Type 3, Code 4) from anywhere.
+The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add an inbound rule that allows the ICMP message ``Destination Unreachable: Fragmentation Needed and Don't Fragment was Set`` (Type 3, Code 4) from anywhere. ::
 
     aws ec2 authorize-security-group-ingress \
         --group-id sg-1234567890abcdef0 \
-        --ip-permissions IpProtocol=icmp,FromPort=3,ToPort=4,IpRanges="[{CidrIp=0.0.0.0/0}]"
+        --ip-permissions 'IpProtocol=icmp,FromPort=3,ToPort=4,IpRanges=[{CidrIp=0.0.0.0/0}]'
 
 Output::
 
@@ -121,11 +121,11 @@ Output::
 
 **Example 5: To add a rule for IPv6 traffic**
 
-The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add an inbound rule that allows SSH access (port 22) from the IPv6 range ``2001:db8:1234:1a00::/64``.  
+The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add an inbound rule that allows SSH access (port 22) from the IPv6 range ``2001:db8:1234:1a00::/64``. ::
 
     aws ec2 authorize-security-group-ingress \
         --group-id sg-1234567890abcdef0 \
-        --ip-permissions IpProtocol=tcp,FromPort=22,ToPort=22,Ipv6Ranges="[{CidrIpv6=2001:db8:1234:1a00::/64}]"
+        --ip-permissions 'IpProtocol=tcp,FromPort=22,ToPort=22,Ipv6Ranges=[{CidrIpv6=2001:db8:1234:1a00::/64}]'
 
 Output::
 
@@ -147,12 +147,12 @@ Output::
 
 **Example 6: To add a rule for ICMPv6 traffic**
 
-The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add an inbound rule that allows ICMPv6 traffic from anywhere.  
+The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add an inbound rule that allows ICMPv6 traffic from anywhere. ::
 
     aws ec2 authorize-security-group-ingress \
         --group-id sg-1234567890abcdef0 \
-        --ip-permissions IpProtocol=icmpv6,Ipv6Ranges="[{CidrIpv6=::/0}]"
-    
+        --ip-permissions 'IpProtocol=icmpv6,Ipv6Ranges=[{CidrIpv6=::/0}]'
+
 Output::
 
     {
@@ -173,11 +173,11 @@ Output::
 
 **Example 7: Add a rule with a description**
 
-The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add an inbound rule that allows RDP traffic from the specified IPv4 address range. The rule includes a description to help you identify it later.  
+The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add an inbound rule that allows RDP traffic from the specified IPv4 address range. The rule includes a description to help you identify it later. ::
 
     aws ec2 authorize-security-group-ingress \
         --group-id sg-1234567890abcdef0 \
-        --ip-permissions IpProtocol=tcp,FromPort=3389,ToPort=3389,IpRanges="[{CidrIp=203.0.113.0/24,Description='RDP access from NY office'}]"
+        --ip-permissions 'IpProtocol=tcp,FromPort=3389,ToPort=3389,IpRanges=[{CidrIp=203.0.113.0/24,Description='RDP access from NY office'}]'
 
 Output::
 
@@ -200,11 +200,11 @@ Output::
         
 **Example 8: To add an inbound rule that uses a prefix list**
 
-The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add an inbound rule that allows all traffic for the CIDR ranges in the specified prefix list.  
+The following ``authorize-security-group-ingress`` example uses the ``ip-permissions`` parameter to add an inbound rule that allows all traffic for the CIDR ranges in the specified prefix list. ::
 
     aws ec2 authorize-security-group-ingress \
         --group-id sg-04a351bfe432d4e71 \
-        --ip-permissions IpProtocol=all,PrefixListIds="[{PrefixListId=pl-002dc3ec097de1514}]"
+        --ip-permissions 'IpProtocol=all,PrefixListIds=[{PrefixListId=pl-002dc3ec097de1514}]'
 
 Output::
 
@@ -224,4 +224,4 @@ Output::
         ]
     }
 
-For more information, see `Security groups <https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html>`__ in the *Amazon VPC User Guide*.
+For more information, see `Security groups <https://docs.aws.amazon.com/vpc/latest/userguide/vpc-security-groups.html>`__ in the *Amazon VPC User Guide*.

awscli/examples/ec2/cancel-capacity-reservation.rst

@@ -1,14 +1,14 @@
-**To cancel a capacity reservation**
-
-The following ``cancel-capacity-reservation`` example cancels the specified capacity reservation. ::
-
-    aws ec2 cancel-capacity-reservation \
-        --capacity-reservation-id cr-1234abcd56EXAMPLE
-
-Output::
-
-    {
-        "Return": true
-    }
-
-For more information, see `Canceling a Capacity Reservation <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/capacity-reservations-using.html#capacity-reservations-release>`__ in the *Amazon Elastic Compute Cloud User Guide for Linux Instances*.
+**To cancel a capacity reservation**
+
+The following ``cancel-capacity-reservation`` example cancels the specified capacity reservation. ::
+
+    aws ec2 cancel-capacity-reservation \
+        --capacity-reservation-id cr-1234abcd56EXAMPLE
+
+Output::
+
+    {
+        "Return": true
+    }
+
+For more information, see `Cancel a Capacity Reservation <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/capacity-reservations-release.html>`__ in the *Amazon EC2 User Guide*.