As demonstrated on Steps 8 and 9 of using Public IPv4 BYOIP, the two functions listed above are available only via AWS CLI / SDKs at the moment, and not through CloudFormation.
This impose significant challenges on how far our automation can go to provision new VPCs with slices of public BYOIP IPAM pools.
We need to manage them through Cloudformation, especially when dealing with ephemeral VPCs.
With the help of Cloudformation lifecycle, when the user deletes the stack, CF should deprovision all IPv4s and delete the public ipv4 pool.
Name of the resource
Other
Resource name
AWS::EC2::CreatePublicIpv4Pool, AWS::EC2::ProvisionPublicIpv4PoolCidr
Description
As demonstrated on Steps 8 and 9 of using Public IPv4 BYOIP, the two functions listed above are available only via AWS CLI / SDKs at the moment, and not through CloudFormation.
This impose significant challenges on how far our automation can go to provision new VPCs with slices of public BYOIP IPAM pools.
We need to manage them through Cloudformation, especially when dealing with ephemeral VPCs. With the help of Cloudformation lifecycle, when the user deletes the stack, CF should deprovision all IPv4s and delete the public ipv4 pool.