As organisations migrate workloads to the cloud, maintaining consistent public IP addresses has become increasingly important. Businesses often want to preserve existing firewall rules, customer allowlists, geolocation data, email reputation, or regulatory requirements while moving services into Amazon Web Services (AWS). AWS addresses this need through Bring Your Own IP (BYOIP), which allows organisations to advertise their own public IPv4 address space from AWS infrastructure instead of using Amazon-assigned public IPs.
Whether your organisation owns IPv4 resources outright or leases them from a provider that supports BYOIP, understanding the AWS onboarding process helps ensure a smooth migration and secure deployment.
What Is AWS BYOIP?
AWS Bring Your Own IP (BYOIP) allows organisations to import publicly routable IPv4 address ranges into Amazon EC2. Once provisioned, AWS advertises those addresses on the public internet, while the organisation retains control of the address space. The imported range appears as an address pool that can be used to allocate Elastic IP addresses for supported AWS services.
Typical use cases include:
- Cloud migration
- Disaster recovery
- Hybrid cloud deployments
- Application modernisation
- Preserving public-facing IP addresses
- Reducing infrastructure changes during migration
Can You Bring a Leased Prefix to AWS?
Yes, provided the lease agreement allows it and the provider supports AWS BYOIP requirements.
For BYOIP, AWS validates that the organisation provisioning the prefix is authorised to use it. In practice:
- Owned prefixes are commonly used for BYOIP.
- Leased prefixes can also be used when the leasing provider supports AWS onboarding and the required routing authorisations.
The key requirement is that AWS must be able to verify control of the address range through the supported validation process.
AWS BYOIP Requirements
Before onboarding an IPv4 range, AWS requires several conditions to be met.
Current requirements include:
- Publicly routable IPv4 address space
- Registration with a supported Regional Internet Registry (ARIN, RIPE NCC, or APNIC)
- Registration to a business or institutional entity
- A minimum IPv4 prefix size of /24
- Appropriate routing authorisations
- Successful ownership verification
AWS also evaluates the reputation of the address range and may reject prefixes associated with malicious activity.
Bringing an Owned IPv4 Prefix to AWS
For organisations that own IPv4 resources, the typical process includes:
- Confirm ownership through the appropriate RIR.
- Prepare the required routing authorisations.
- Complete AWS verification.
- Provision the address range.
- Advertise the prefix through AWS.
- Allocate addresses from the BYOIP pool to AWS resources.
After provisioning, AWS advertises the prefix while the organisation continues to control the address space.
Bringing a Leased IPv4 Prefix to AWS
The overall deployment process is similar, but additional coordination with the leasing provider is often required.
A typical workflow includes:
- Confirm that the lease permits AWS BYOIP deployment.
- Obtain any required routing authorisations.
- Coordinate RPKI and ROA configuration.
- Complete AWS verification.
- Provision the prefix in AWS.
- Begin advertising through AWS.
Not every leased prefix is automatically suitable for BYOIP, so organisations should verify support before deployment.
RPKI and ROAs
Routing security plays an important role in AWS BYOIP.
AWS requires appropriate routing authorisation before advertising publicly routable IPv4 prefixes.
A Route Origin Authorization (ROA) identifies which Autonomous System (ASN) is authorised to announce the IPv4 prefix.
For AWS BYOIP, organisations must authorise the appropriate AWS ASNs in the ROA before provisioning can complete. AWS validates this information during onboarding.
RDAP Verification
AWS also verifies control of the address space through RDAP.
Depending on the onboarding method, verification may involve:
- Updating RDAP records with an X.509 certificate, or
- Using Amazon VPC IP Address Manager (IPAM) with DNS-based validation.
These verification methods allow AWS to confirm that the organisation controls the IPv4 resources being onboarded.
Benefits of AWS BYOIP
Many organisations choose BYOIP because it provides operational continuity.
Advantages include:
- Retaining existing public IP addresses
- Preserving firewall allowlists
- Maintaining customer trust
- Simplifying migrations
- Supporting hybrid environments
- Greater operational flexibility
Businesses can move workloads to AWS while minimising changes to existing infrastructure.
Best Practices
Before deploying BYOIP, organisations should:
- Verify ownership or lease rights.
- Confirm the prefix meets AWS requirements.
- Review address reputation.
- Configure RPKI and ROAs correctly.
- Maintain accurate RDAP records.
- Plan regional deployment carefully.
- Test routing before production rollout.
Preparation significantly reduces deployment issues.
Common Deployment Challenges
Some common challenges include:
- Prefixes smaller than /24
- Missing ROAs
- Incorrect RDAP information
- Reputation issues
- Incomplete documentation
- Routing configuration errors
Reviewing AWS requirements before provisioning helps avoid unnecessary delays.
The Future of BYOIP
As hybrid cloud deployments continue to grow, BYOIP adoption is expected to increase.
Industry trends include:
- Greater cloud portability
- Increased use of customer-owned IP space
- Expanded RPKI adoption
- Improved routing automation
- Better integration with cloud networking tools
- Continued coexistence of IPv4 and IPv6
These developments make BYOIP an increasingly valuable option for enterprise cloud deployments.
Bringing IPv4 Resources to AWS Successfully
Understanding AWS BYOIP for IPv4 helps organisations migrate workloads while maintaining continuity for public-facing services. Whether deploying an owned IPv4 prefix or a leased prefix supported for BYOIP, success depends on proper planning, accurate routing authorisations, current RDAP records, and compliance with AWS onboarding requirements.
For the latest technical requirements and onboarding procedures, consult the official AWS BYOIP documentation before deployment.
About IPv4Hub
IPv4Hub is a trusted marketplace where organisations can lease, buy, and sell IPv4 address resources through a secure and transparent platform. Businesses benefit from verified IPv4 inventory, structured onboarding, transparent pricing, secure transaction workflows, and professional guidance throughout the acquisition process. For organisations planning AWS BYOIP deployments, IPv4Hub provides high-quality IPv4 resources, IP intelligence, and registry-aware support that help simplify cloud migrations while maintaining secure and scalable network infrastructure.
Discover available IPv4 blocks across multiple regional internet registries.