Requirements for BYOIP in Amazon EC2

Question

I would like to bring to Amazon EC2 a /24 range of public IP addresses administered by RIPE. I had a look at the documentation for this operation and I am not able to understand if I can bring my range that has `ASSIGNED PA` set as status.

Specific accepted status values are specified in the procedure "[Bring your own IP addresses (BYOIP) in AWS Global Accelerator](https://docs.aws.amazon.com/global-accelerator/latest/dg/using-byoip.html)" but not in "[Bring your own IP addresses (BYOIP) in Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2-byoip.html)".

Am I missing something or this status is not a concern when doing BYOIP in Amazon EC2?

AWS-User-9680052 · Accepted Answer

Assigned PA addresses do not belong to the end-user and therefore need to be returned when they cease their connection with the Local Internet registry (LIR). Therefore, AWS would not support the types of addresses spaces. For RIPE, the supported allocation statuses are "ALLOCATED PA", "LEGACY", and "ASSIGNED PI".

As per the IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region (RIPE-730): https://www.ripe.net/publications/docs/ripe-733

ASSIGNED PA: This address space has been assigned to the issuing LIR infrastructure or an End User for use with services provided by the issuing LIR. It cannot be kept when terminating services provided by the LIR.

Brettski-AWS · Answer

My feel here is that the requirements should be the same for both. I'm going to provide that feedback to the teams about their documentation.

Requirements for BYOIP in Amazon EC2

Relevant content