|
4966 | 4966 | "enum":[
|
4967 | 4967 | "lowestPrice",
|
4968 | 4968 | "diversified",
|
4969 |
| - "capacityOptimized" |
| 4969 | + "capacityOptimized", |
| 4970 | + "capacityOptimizedPrioritized" |
4970 | 4971 | ]
|
4971 | 4972 | },
|
4972 | 4973 | "AllowedPrincipal":{
|
|
5641 | 5642 | "AssociateSubnetCidrBlockRequest":{
|
5642 | 5643 | "type":"structure",
|
5643 | 5644 | "required":[
|
5644 |
| - "Ipv6CidrBlock", |
5645 |
| - "SubnetId" |
| 5645 | + "SubnetId", |
| 5646 | + "Ipv6CidrBlock" |
5646 | 5647 | ],
|
5647 | 5648 | "members":{
|
5648 |
| - "Ipv6CidrBlock":{ |
5649 |
| - "shape":"String", |
5650 |
| - "documentation":"<p>The IPv6 CIDR block for your subnet. The subnet must have a /64 prefix length.</p>", |
5651 |
| - "locationName":"ipv6CidrBlock" |
5652 |
| - }, |
5653 | 5649 | "SubnetId":{
|
5654 | 5650 | "shape":"SubnetId",
|
5655 | 5651 | "documentation":"<p>The ID of your subnet.</p>",
|
5656 | 5652 | "locationName":"subnetId"
|
| 5653 | + }, |
| 5654 | + "Ipv6CidrBlock":{ |
| 5655 | + "shape":"String", |
| 5656 | + "documentation":"<p>The IPv6 CIDR block for your subnet. The subnet must have a /64 prefix length.</p>", |
| 5657 | + "locationName":"ipv6CidrBlock" |
5657 | 5658 | }
|
5658 | 5659 | }
|
5659 | 5660 | },
|
|
9563 | 9564 | "CreateNatGatewayRequest":{
|
9564 | 9565 | "type":"structure",
|
9565 | 9566 | "required":[
|
9566 |
| - "AllocationId", |
9567 |
| - "SubnetId" |
| 9567 | + "SubnetId", |
| 9568 | + "AllocationId" |
9568 | 9569 | ],
|
9569 | 9570 | "members":{
|
9570 |
| - "AllocationId":{ |
9571 |
| - "shape":"AllocationId", |
9572 |
| - "documentation":"<p>The allocation ID of an Elastic IP address to associate with the NAT gateway. If the Elastic IP address is associated with another resource, you must first disassociate it.</p>" |
9573 |
| - }, |
9574 | 9571 | "ClientToken":{
|
9575 | 9572 | "shape":"String",
|
9576 | 9573 | "documentation":"<p>Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/Run_Instance_Idempotency.html\">How to Ensure Idempotency</a>.</p> <p>Constraint: Maximum 64 ASCII characters.</p>",
|
|
9588 | 9585 | "shape":"TagSpecificationList",
|
9589 | 9586 | "documentation":"<p>The tags to assign to the NAT gateway.</p>",
|
9590 | 9587 | "locationName":"TagSpecification"
|
| 9588 | + }, |
| 9589 | + "AllocationId":{ |
| 9590 | + "shape":"AllocationId", |
| 9591 | + "documentation":"<p>The allocation ID of an Elastic IP address to associate with the NAT gateway. If the Elastic IP address is associated with another resource, you must first disassociate it.</p>" |
9591 | 9592 | }
|
9592 | 9593 | }
|
9593 | 9594 | },
|
|
10221 | 10222 | "CreateSubnetRequest":{
|
10222 | 10223 | "type":"structure",
|
10223 | 10224 | "required":[
|
10224 |
| - "CidrBlock", |
10225 |
| - "VpcId" |
| 10225 | + "VpcId", |
| 10226 | + "CidrBlock" |
10226 | 10227 | ],
|
10227 | 10228 | "members":{
|
10228 | 10229 | "TagSpecifications":{
|
|
10238 | 10239 | "shape":"String",
|
10239 | 10240 | "documentation":"<p>The AZ ID or the Local Zone ID of the subnet.</p>"
|
10240 | 10241 | },
|
10241 |
| - "CidrBlock":{ |
10242 |
| - "shape":"String", |
10243 |
| - "documentation":"<p>The IPv4 network range for the subnet, in CIDR notation. For example, <code>10.0.0.0/24</code>. We modify the specified CIDR block to its canonical form; for example, if you specify <code>100.68.0.18/18</code>, we modify it to <code>100.68.0.0/18</code>.</p>" |
10244 |
| - }, |
10245 | 10242 | "Ipv6CidrBlock":{
|
10246 | 10243 | "shape":"String",
|
10247 | 10244 | "documentation":"<p>The IPv6 network range for the subnet, in CIDR notation. The subnet size must use a /64 prefix length.</p>"
|
|
10258 | 10255 | "shape":"Boolean",
|
10259 | 10256 | "documentation":"<p>Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is <code>DryRunOperation</code>. Otherwise, it is <code>UnauthorizedOperation</code>.</p>",
|
10260 | 10257 | "locationName":"dryRun"
|
| 10258 | + }, |
| 10259 | + "CidrBlock":{ |
| 10260 | + "shape":"String", |
| 10261 | + "documentation":"<p>The IPv4 network range for the subnet, in CIDR notation. For example, <code>10.0.0.0/24</code>. We modify the specified CIDR block to its canonical form; for example, if you specify <code>100.68.0.18/18</code>, we modify it to <code>100.68.0.0/18</code>.</p>" |
10261 | 10262 | }
|
10262 | 10263 | }
|
10263 | 10264 | },
|
|
14693 | 14694 | "members":{
|
14694 | 14695 | "Attribute":{
|
14695 | 14696 | "shape":"ImageAttributeName",
|
14696 |
| - "documentation":"<p>The AMI attribute.</p> <p> <b>Note</b>: Depending on your account privileges, the <code>blockDeviceMapping</code> attribute may return a <code>Client.AuthFailure</code> error. If this happens, use <a>DescribeImages</a> to get information about the block device mapping for the AMI.</p>" |
| 14697 | + "documentation":"<p>The AMI attribute.</p> <p> <b>Note</b>: The <code>blockDeviceMapping</code> attribute is deprecated. Using this attribute returns the <code>Client.AuthFailure</code> error. To get information about the block device mappings for an AMI, use the <a>DescribeImages</a> action.</p>" |
14697 | 14698 | },
|
14698 | 14699 | "ImageId":{
|
14699 | 14700 | "shape":"ImageId",
|
|
21062 | 21063 | },
|
21063 | 21064 | "Priority":{
|
21064 | 21065 | "shape":"Double",
|
21065 |
| - "documentation":"<p>The priority for the launch template override. If <b>AllocationStrategy</b> is set to <code>prioritized</code>, EC2 Fleet uses priority to determine which launch template override to use first in fulfilling On-Demand capacity. The highest priority is launched first. Valid values are whole numbers starting at <code>0</code>. The lower the number, the higher the priority. If no number is set, the override has the lowest priority.</p>", |
| 21066 | + "documentation":"<p>The priority for the launch template override. The highest priority is launched first.</p> <p>If the On-Demand <code>AllocationStrategy</code> is set to <code>prioritized</code>, EC2 Fleet uses priority to determine which launch template override to use first in fulfilling On-Demand capacity.</p> <p>If the Spot <code>AllocationStrategy</code> is set to <code>capacity-optimized-prioritized</code>, EC2 Fleet uses priority on a best-effort basis to determine which launch template override to use first in fulfilling Spot capacity, but optimizes for capacity first.</p> <p>Valid values are whole numbers starting at <code>0</code>. The lower the number, the higher the priority. If no number is set, the override has the lowest priority. You can set the same priority for different launch template overrides.</p>", |
21066 | 21067 | "locationName":"priority"
|
21067 | 21068 | },
|
21068 | 21069 | "Placement":{
|
|
21114 | 21115 | },
|
21115 | 21116 | "Priority":{
|
21116 | 21117 | "shape":"Double",
|
21117 |
| - "documentation":"<p>The priority for the launch template override. If <b>AllocationStrategy</b> is set to <code>prioritized</code>, EC2 Fleet uses priority to determine which launch template override to use first in fulfilling On-Demand capacity. The highest priority is launched first. Valid values are whole numbers starting at <code>0</code>. The lower the number, the higher the priority. If no number is set, the launch template override has the lowest priority.</p>" |
| 21118 | + "documentation":"<p>The priority for the launch template override. The highest priority is launched first.</p> <p>If the On-Demand <code>AllocationStrategy</code> is set to <code>prioritized</code>, EC2 Fleet uses priority to determine which launch template override to use first in fulfilling On-Demand capacity.</p> <p>If the Spot <code>AllocationStrategy</code> is set to <code>capacity-optimized-prioritized</code>, EC2 Fleet uses priority on a best-effort basis to determine which launch template override to use first in fulfilling Spot capacity, but optimizes for capacity first.</p> <p>Valid values are whole numbers starting at <code>0</code>. The lower the number, the higher the priority. If no number is set, the launch template override has the lowest priority. You can set the same priority for different launch template overrides.</p>" |
21118 | 21119 | },
|
21119 | 21120 | "Placement":{
|
21120 | 21121 | "shape":"Placement",
|
|
27215 | 27216 | },
|
27216 | 27217 | "Priority":{
|
27217 | 27218 | "shape":"Double",
|
27218 |
| - "documentation":"<p>The priority for the launch template override. If <b>OnDemandAllocationStrategy</b> is set to <code>prioritized</code>, Spot Fleet uses priority to determine which launch template override to use first in fulfilling On-Demand capacity. The highest priority is launched first. Valid values are whole numbers starting at <code>0</code>. The lower the number, the higher the priority. If no number is set, the launch template override has the lowest priority.</p>", |
| 27219 | + "documentation":"<p>The priority for the launch template override. The highest priority is launched first.</p> <p>If <code>OnDemandAllocationStrategy</code> is set to <code>prioritized</code>, Spot Fleet uses priority to determine which launch template override to use first in fulfilling On-Demand capacity.</p> <p>If the Spot <code>AllocationStrategy</code> is set to <code>capacityOptimizedPrioritized</code>, Spot Fleet uses priority on a best-effort basis to determine which launch template override to use first in fulfilling Spot capacity, but optimizes for capacity first.</p> <p>Valid values are whole numbers starting at <code>0</code>. The lower the number, the higher the priority. If no number is set, the launch template override has the lowest priority. You can set the same priority for different launch template overrides.</p>", |
27219 | 27220 | "locationName":"priority"
|
27220 | 27221 | }
|
27221 | 27222 | },
|
|
36807 | 36808 | "enum":[
|
36808 | 36809 | "lowest-price",
|
36809 | 36810 | "diversified",
|
36810 |
| - "capacity-optimized" |
| 36811 | + "capacity-optimized", |
| 36812 | + "capacity-optimized-prioritized" |
36811 | 36813 | ]
|
36812 | 36814 | },
|
36813 | 36815 | "SpotCapacityRebalance":{
|
|
37004 | 37006 | "members":{
|
37005 | 37007 | "AllocationStrategy":{
|
37006 | 37008 | "shape":"AllocationStrategy",
|
37007 |
| - "documentation":"<p>Indicates how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the Spot Fleet request.</p> <p>If the allocation strategy is <code>lowestPrice</code>, Spot Fleet launches instances from the Spot Instance pools with the lowest price. This is the default allocation strategy.</p> <p>If the allocation strategy is <code>diversified</code>, Spot Fleet launches instances from all the Spot Instance pools that you specify.</p> <p>If the allocation strategy is <code>capacityOptimized</code>, Spot Fleet launches instances from Spot Instance pools with optimal capacity for the number of instances that are launching.</p>", |
| 37009 | + "documentation":"<p>Indicates how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the Spot Fleet request.</p> <p>If the allocation strategy is <code>lowestPrice</code>, Spot Fleet launches instances from the Spot Instance pools with the lowest price. This is the default allocation strategy.</p> <p>If the allocation strategy is <code>diversified</code>, Spot Fleet launches instances from all the Spot Instance pools that you specify.</p> <p>If the allocation strategy is <code>capacityOptimized</code> (recommended), Spot Fleet launches instances from Spot Instance pools with optimal capacity for the number of instances that are launching. To give certain instance types a higher chance of launching first, use <code>capacityOptimizedPrioritized</code>. Set a priority for each instance type by using the <code>Priority</code> parameter for <code>LaunchTemplateOverrides</code>. You can assign the same priority to different <code>LaunchTemplateOverrides</code>. EC2 implements the priorities on a best-effort basis, but optimizes for capacity first. <code>capacityOptimizedPrioritized</code> is supported only if your Spot Fleet uses a launch template. Note that if the <code>OnDemandAllocationStrategy</code> is set to <code>prioritized</code>, the same priority is applied when fulfilling On-Demand capacity.</p>", |
37008 | 37010 | "locationName":"allocationStrategy"
|
37009 | 37011 | },
|
37010 | 37012 | "OnDemandAllocationStrategy":{
|
|
37383 | 37385 | "members":{
|
37384 | 37386 | "AllocationStrategy":{
|
37385 | 37387 | "shape":"SpotAllocationStrategy",
|
37386 |
| - "documentation":"<p>Indicates how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the EC2 Fleet.</p> <p>If the allocation strategy is <code>lowest-price</code>, EC2 Fleet launches instances from the Spot Instance pools with the lowest price. This is the default allocation strategy.</p> <p>If the allocation strategy is <code>diversified</code>, EC2 Fleet launches instances from all of the Spot Instance pools that you specify.</p> <p>If the allocation strategy is <code>capacity-optimized</code>, EC2 Fleet launches instances from Spot Instance pools with optimal capacity for the number of instances that are launching.</p>", |
| 37388 | + "documentation":"<p>Indicates how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the EC2 Fleet.</p> <p>If the allocation strategy is <code>lowest-price</code>, EC2 Fleet launches instances from the Spot Instance pools with the lowest price. This is the default allocation strategy.</p> <p>If the allocation strategy is <code>diversified</code>, EC2 Fleet launches instances from all of the Spot Instance pools that you specify.</p> <p>If the allocation strategy is <code>capacity-optimized</code> (recommended), EC2 Fleet launches instances from Spot Instance pools with optimal capacity for the number of instances that are launching. To give certain instance types a higher chance of launching first, use <code>capacity-optimized-prioritized</code>. Set a priority for each instance type by using the <code>Priority</code> parameter for <code>LaunchTemplateOverrides</code>. You can assign the same priority to different <code>LaunchTemplateOverrides</code>. EC2 implements the priorities on a best-effort basis, but optimizes for capacity first. <code>capacity-optimized-prioritized</code> is supported only if your fleet uses a launch template. Note that if the On-Demand <code>AllocationStrategy</code> is set to <code>prioritized</code>, the same priority is applied when fulfilling On-Demand capacity.</p>", |
37387 | 37389 | "locationName":"allocationStrategy"
|
37388 | 37390 | },
|
37389 | 37391 | "MaintenanceStrategies":{
|
|
37429 | 37431 | "members":{
|
37430 | 37432 | "AllocationStrategy":{
|
37431 | 37433 | "shape":"SpotAllocationStrategy",
|
37432 |
| - "documentation":"<p>Indicates how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the EC2 Fleet.</p> <p>If the allocation strategy is <code>lowest-price</code>, EC2 Fleet launches instances from the Spot Instance pools with the lowest price. This is the default allocation strategy.</p> <p>If the allocation strategy is <code>diversified</code>, EC2 Fleet launches instances from all of the Spot Instance pools that you specify.</p> <p>If the allocation strategy is <code>capacity-optimized</code>, EC2 Fleet launches instances from Spot Instance pools with optimal capacity for the number of instances that are launching.</p>" |
| 37434 | + "documentation":"<p>Indicates how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the EC2 Fleet.</p> <p>If the allocation strategy is <code>lowest-price</code>, EC2 Fleet launches instances from the Spot Instance pools with the lowest price. This is the default allocation strategy.</p> <p>If the allocation strategy is <code>diversified</code>, EC2 Fleet launches instances from all of the Spot Instance pools that you specify.</p> <p>If the allocation strategy is <code>capacity-optimized</code> (recommended), EC2 Fleet launches instances from Spot Instance pools with optimal capacity for the number of instances that are launching. To give certain instance types a higher chance of launching first, use <code>capacity-optimized-prioritized</code>. Set a priority for each instance type by using the <code>Priority</code> parameter for <code>LaunchTemplateOverrides</code>. You can assign the same priority to different <code>LaunchTemplateOverrides</code>. EC2 implements the priorities on a best-effort basis, but optimizes for capacity first. <code>capacity-optimized-prioritized</code> is supported only if your fleet uses a launch template. Note that if the On-Demand <code>AllocationStrategy</code> is set to <code>prioritized</code>, the same priority is applied when fulfilling On-Demand capacity.</p>" |
37433 | 37435 | },
|
37434 | 37436 | "MaintenanceStrategies":{
|
37435 | 37437 | "shape":"FleetSpotMaintenanceStrategiesRequest",
|
|
0 commit comments