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

awscli/examples/ds-data/list-users.rst

@@ -0,0 +1,57 @@
+**To list a directory's users**
+
+The following ``list-users`` example lists users in the specified directory. ::
+
+    aws ds-data list-users \
+        --directory-id d-1234567890
+
+Output::
+
+    {
+        "Users": [
+            {
+                "Enabled": true,
+                "SAMAccountName": "Administrator",
+                "SID": "S-1-2-34-5678910123-4567895012-3456789012-345"
+            },
+            {
+                "Enabled": false,
+                "SAMAccountName": "Guest",
+                "SID": "S-1-2-34-5678910123-4567895012-3456789012-345"
+            },
+            {
+                "Enabled": false,
+                "SAMAccountName": "krbtgt",
+                "SID": "S-1-2-34-5678910123-4567895012-3456789012-346"
+            },
+            {
+                "Enabled": true,
+                "SAMAccountName": "Admin",
+                "SID": "S-1-2-34-5678910123-4567895012-3456789012-347"
+            },
+            {
+                "Enabled": true,
+                "SAMAccountName": "Richard Roe",
+                "SID": "S-1-2-34-5678910123-4567895012-3456789012-348"
+            },
+            {
+                "Enabled": true,
+                "SAMAccountName": "Jane Doe",
+                "SID": "S-1-2-34-5678910123-4567895012-3456789012-349"
+            },
+            {
+                "Enabled": true,
+                "SAMAccountName": "AWS_WGnzYlN6YyY",
+                "SID": "S-1-2-34-5678901234-5678901234-5678910123-4567"
+            },
+            {
+                "Enabled": true,
+                "SAMAccountName": "john.doe",
+                "SID": "S-1-2-34-5678901234-5678901234-5678910123-4568"
+            }
+        ],
+        "DirectoryId": "d-1234567890",
+        "Realm": "corp.example.com"
+    }
+
+For more information, see `Viewing and updating an AWS Managed Microsoft AD user <https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_view_update_user.html>`__ in the *AWS Directory Service Administration Guide*.

awscli/examples/ds-data/remove-group-member.rst

@@ -0,0 +1,12 @@
+**To remove a group member from a directory**
+
+The following ``remove-group-member`` example removes the specified group member from the specified group in the specified directory. ::
+
+    aws ds-data remove-group-member \
+        --directory-id d-1234567890 \
+        --group-name 'sales' \
+        --member-name 'john.doe'
+
+This command produces no output.
+
+For more information, see `Adding and removing AWS Managed Microsoft AD members to groups and groups to groups <https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_add_remove_user_group.html>`__ in the *AWS Directory Service Administration Guide*.

awscli/examples/ds-data/reset-user-password.rst

@@ -0,0 +1,12 @@
+**To reset a user password in a directory**
+
+The following ``reset-user-password`` example resets and enables the specified user in the specified directory. ::
+
+    aws ds reset-user-password \
+        --directory-id d-1234567890 \
+        --user-name 'john.doe' \
+        --new-password 'password'
+
+This command produces no output.
+
+For more information, see `Resetting and enabling an AWS Managed Microsoft AD user's password <https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_reset_user_pswd.html>`__ in the *AWS Directory Service Administration Guide*.

awscli/examples/ds-data/search-groups.rst

@@ -0,0 +1,25 @@
+**To search for a group in a directory**
+
+The following ``search-groups`` example searches for the specified group in the specified directory. ::
+
+    aws ds-data search-groups \
+        --directory-id d-1234567890 \
+        --search-attributes 'SamAccountName' \
+        --search-string 'sales'
+
+Output::
+
+    {
+        "Groups": [
+            {
+                "GroupScope": "Global",
+                "GroupType": "Distribution",
+                "SAMAccountName": "sales",
+                "SID": "S-1-2-34-5678901234-5678901234-5678910123-4567"
+            }
+        ],
+        "DirectoryId": "d-1234567890",
+        "Realm": "corp.example.com"
+    }
+
+For more information, see `Viewing and updating an AWS Managed Microsoft AD group's details <https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_view_update_group.html>`__ in the *AWS Directory Service Administration Guide*.

awscli/examples/ds-data/search-users.rst

@@ -0,0 +1,24 @@
+**To search for a user in a directory**
+
+The following ``search-users`` example searches for the specified user in the specified directory. ::
+
+    aws ds-data search-users \
+        --directory-id d-1234567890 \
+        --search-attributes 'SamAccountName' \
+        --Search-string 'john.doe'
+
+Output::
+
+    {
+        "Users": [
+            {
+                "Enabled": true,
+                "SAMAccountName": "john.doe",
+                "SID": "S-1-2-34-5678901234-5678901234-5678910123-4567"
+            }
+        ],
+        "DirectoryId": "d-1234567890",
+        "Realm": "corp.example.com"
+    }
+
+For more information, see `Viewing and updating an AWS Managed Microsoft AD user <https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_view_update_user.html>`__ in the *AWS Directory Service Administration Guide*.

awscli/examples/ds-data/update-group.rst

@@ -0,0 +1,13 @@
+**To update a group's attribute in a directory**
+
+The following ``update-group`` example updates the specified attribute for the specified group in the specified directory. ::
+
+    aws ds-data update-group \
+        --directory-id d-1234567890 \
+        --sam-account-name 'sales' \
+        --update-type 'REPLACE' \
+        --group-type 'Distribution'
+
+This command produces no output.
+
+For more information, see `Viewing and updating an AWS Managed Microsoft AD group's details <https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_view_update_group.html>`__ in the *AWS Directory Service Administration Guide*.

awscli/examples/ds-data/update-user.rst

@@ -0,0 +1,13 @@
+**To update a user's attribute in a directory**
+
+The following ``update-user`` example updates the specified attribute for the specified user in the specified directory. ::
+
+    aws ds-data update-user \
+        --directory-id d-1234567890 \
+        --sam-account-name 'john.doe' \
+        --update-type 'ADD' \
+        --email-address 'example.corp.com'
+
+This command produces no output.
+
+For more information, see `Viewing and updating an AWS Managed Microsoft AD user <https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_view_update_user.html>`__ in the *AWS Directory Service Administration Guide*.

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*.