|
4555 | 4555 | },
|
4556 | 4556 | "input":{"shape":"MoveByoipCidrToIpamRequest"},
|
4557 | 4557 | "output":{"shape":"MoveByoipCidrToIpamResult"},
|
4558 |
| - "documentation":"<p>Move an BYOIP IPv4 CIDR to IPAM from a public IPv4 pool.</p>" |
| 4558 | + "documentation":"<p>Move an BYOIP IPv4 CIDR to IPAM from a public IPv4 pool.</p> <p>If you already have an IPv4 BYOIP CIDR with Amazon Web Services, you can move the CIDR to IPAM from a public IPv4 pool. You cannot move an IPv6 CIDR to IPAM. If you are bringing a new IP address to Amazon Web Services for the first time, complete the steps in <a href=\"/vpc/latest/ipam/tutorials-byoip-ipam.html\">Tutorial: BYOIP address CIDRs to IPAM</a>.</p>" |
4559 | 4559 | },
|
4560 | 4560 | "ProvisionByoipCidr":{
|
4561 | 4561 | "name":"ProvisionByoipCidr",
|
|
4575 | 4575 | },
|
4576 | 4576 | "input":{"shape":"ProvisionIpamPoolCidrRequest"},
|
4577 | 4577 | "output":{"shape":"ProvisionIpamPoolCidrResult"},
|
4578 |
| - "documentation":"<p>Provision a CIDR to an IPAM pool. You can use thsi action to provision new CIDRs to a top-level pool or to transfer a CIDR from a top-level pool to a pool within it.</p> <p>For more information, see <a href=\"/vpc/latest/ipam/prov-cidr-ipam.html\">Provision CIDRs to pools</a> in the <i>Amazon VPC IPAM User Guide</i>. </p>" |
| 4578 | + "documentation":"<p>Provision a CIDR to an IPAM pool. You can use this action to provision new CIDRs to a top-level pool or to transfer a CIDR from a top-level pool to a pool within it.</p> <p>For more information, see <a href=\"/vpc/latest/ipam/prov-cidr-ipam.html\">Provision CIDRs to pools</a> in the <i>Amazon VPC IPAM User Guide</i>. </p>" |
4579 | 4579 | },
|
4580 | 4580 | "ProvisionPublicIpv4PoolCidr":{
|
4581 | 4581 | "name":"ProvisionPublicIpv4PoolCidr",
|
|
4585 | 4585 | },
|
4586 | 4586 | "input":{"shape":"ProvisionPublicIpv4PoolCidrRequest"},
|
4587 | 4587 | "output":{"shape":"ProvisionPublicIpv4PoolCidrResult"},
|
4588 |
| - "documentation":"<p>Provision a CIDR to a public IPv4 pool.</p> <p>For more information about IPAM, see <a href=\"/vpc/latest/ipam/what-is-it-ipam.html\">What is IPAM?</a> in the <i>Amazon VPC IPAM User Guide</i>. </p>" |
| 4588 | + "documentation":"<p>Provision a CIDR to a public IPv4 pool.</p> <p>For more information about IPAM, see <a href=\"/vpc/latest/ipam/what-is-it-ipam.html\">What is IPAM?</a> in the <i>Amazon VPC IPAM User Guide</i>.</p>" |
4589 | 4589 | },
|
4590 | 4590 | "PurchaseHostReservation":{
|
4591 | 4591 | "name":"PurchaseHostReservation",
|
|
14145 | 14145 | "IpamId":{
|
14146 | 14146 | "shape":"IpamId",
|
14147 | 14147 | "documentation":"<p>The ID of the IPAM to delete.</p>"
|
| 14148 | + }, |
| 14149 | + "Cascade":{ |
| 14150 | + "shape":"Boolean", |
| 14151 | + "documentation":"<p>Enables you to quickly delete an IPAM, private scopes, pools in private scopes, and any allocations in the pools in private scopes. You cannot delete the IPAM with this option if there is a pool in your public scope. If you use this option, IPAM does the following:</p> <ul> <li> <p>Deallocates any CIDRs allocated to VPC resources (such as VPCs) in pools in private scopes.</p> <note> <p>No VPC resources are deleted as a result of enabling this option. The CIDR associated with the resource will no longer be allocated from an IPAM pool, but the CIDR itself will remain unchanged.</p> </note> </li> <li> <p>Deprovisions all IPv4 CIDRs provisioned to IPAM pools in private scopes.</p> </li> <li> <p>Deletes all IPAM pools in private scopes.</p> </li> <li> <p>Deletes all non-default private scopes in the IPAM.</p> </li> <li> <p>Deletes the default public and private scopes and the IPAM.</p> </li> </ul>" |
14148 | 14152 | }
|
14149 | 14153 | }
|
14150 | 14154 | },
|
|
32009 | 32013 | "locationName":"tagSet"
|
32010 | 32014 | }
|
32011 | 32015 | },
|
32012 |
| - "documentation":"<p>In IPAM, a scope is the highest-level container within IPAM. An IPAM contains two default scopes. Each scope represents the IP space for a single network. The private scope is intended for all private IP address space. The public scope is intended for all public IP address space. Scopes enable you to reuse IP addresses across multiple unconnected networks without causing IP address overlap or conflict.</p> <p>For more information, see <a href=\"/vpc/latest/ipam/how-it-works-ipam.html\">How IPAM works</a> in the <i>Amazon VPC IPAM User Guide</i> </p>" |
| 32016 | + "documentation":"<p>In IPAM, a scope is the highest-level container within IPAM. An IPAM contains two default scopes. Each scope represents the IP space for a single network. The private scope is intended for all private IP address space. The public scope is intended for all public IP address space. Scopes enable you to reuse IP addresses across multiple unconnected networks without causing IP address overlap or conflict.</p> <p>For more information, see <a href=\"/vpc/latest/ipam/how-it-works-ipam.html\">How IPAM works</a> in the <i>Amazon VPC IPAM User Guide</i>.</p>" |
32013 | 32017 | },
|
32014 | 32018 | "IpamScopeId":{"type":"string"},
|
32015 | 32019 | "IpamScopeSet":{
|
|
40492 | 40496 | "type":"structure",
|
40493 | 40497 | "required":[
|
40494 | 40498 | "IpamPoolId",
|
40495 |
| - "Cidr" |
| 40499 | + "Cidr", |
| 40500 | + "IpamPoolAllocationId" |
40496 | 40501 | ],
|
40497 | 40502 | "members":{
|
40498 | 40503 | "DryRun":{
|
|
0 commit comments