Use LogicWeb IPv4 in Amazon EC2
AWS BYOIP with LogicWeb IPv4
Use eligible LogicWeb leased IPv4 space with Amazon EC2 BYOIP, including AWS control validation, RPKI authorization, provisioning, advertisement, and cutover planning.
AWS Bring Your Own IP (BYOIP) lets you provision an eligible public IPv4 range into your AWS account and have Amazon advertise it while you keep using address space supplied by LogicWeb. For IPv4, AWS currently accepts /24 or larger ranges and validates both control of the range and route authorization before the prefix can be advertised.
Best fit
When this option makes sense.
Size address space around the network you actually operate, then leave deliberate room for growth and operational separation.
AWS teams that want stable public IPv4 while moving workloads into EC2
Customers that need portable leased address space instead of AWS-owned public IPv4
Infrastructure teams prepared to coordinate AWS verification, RIR/RDAP data, and RPKI before cutover
Plan the deployment
Start with an AWS-eligible /24 or larger
Amazon EC2 BYOIP currently accepts IPv4 prefixes no more specific than /24. The range must be registered with a supported RIR such as ARIN, RIPE, or APNIC to a business or institutional entity, and AWS can reject address space with a poor reputation. Confirm BYOIP eligibility with LogicWeb before building the deployment around a specific lease.
Route it deliberately
Authorize Amazon to originate the route
For standard commercial AWS Regions, Amazon documents ROAs authorizing AS16509 and AS14618 for publicly advertisable EC2 BYOIP space. The ROA, prefix length, and any existing origin authorization need to be coordinated carefully so the route stays RPKI-valid during the change. LogicWeb can coordinate the registry and RPKI side for eligible leased inventory.
Operate it well
Prove control, then provision the range
AWS verifies control before provisioning. Its EC2 workflow supports an X.509 certificate published in the RIR/RDAP record; Amazon VPC IPAM also supports DNS-based verification. After AWS marks the CIDR provisioned, it becomes an address pool in your account and can be prepared for use before you turn on AWS advertisement.
Operate it well
Cut over the advertisement deliberately
AWS recommends stopping advertisement of the BYOIP CIDR from the old location when you begin advertising it through AWS. You can prepare AWS resources first, then coordinate the routing change to reduce downtime. Once advertised through EC2 BYOIP, IPv4 addresses from the pool can be allocated as Elastic IPs for supported resources such as EC2 instances, NAT gateways, and Network Load Balancers.
Lease operations
Infrastructure around the prefix matters too.
Exact support depends on address family, prefix, registry, and deployment. Confirm the final order details before routing production traffic.
Same-day LOA
Authorization is normally emailed during sales hours after payment and order checks.
WHOIS / SWIP
Company details and updates are included for eligible /24 and larger allocations.
Geolocation updates
Request a city and country when ordering or through a support ticket.
IRR & RPKI / ROA
Route objects and origin authorizations through ARIN or RIPE where supported by the block.
Reverse DNS
Delegate reverse DNS to your nameservers or request hosted PTR records. The published minimum is /24.
Optional rotation
The published option costs $25 per /24 per month. Confirm suitability and availability with sales.
Keep the use attributable and policy-compliant.Leased address space remains subject to LogicWeb’s IP Leasing Policy and Acceptable Use Policy. Larger pools increase the importance of customer attribution, complaint handling, and clean routing records.Read the IP Leasing Policy
Official requirements · checked September 30, 2026
Verify the AWS-side requirements before provisioning.
AWS controls the BYOIP validation and advertisement workflow. LogicWeb can prepare eligible leased address space for that workflow, but AWS requirements, quotas, supported Regions, and validation rules can change. Use the current AWS documentation when you provision the prefix.
Before you order
Common questions.
Can I use leased LogicWeb IPv4 with AWS BYOIP?
Yes, eligible LogicWeb IPv4 leases can be prepared for AWS BYOIP. For EC2, plan on a /24 or larger and confirm the exact block with LogicWeb first because AWS still performs its own registration, control, route-authorization, and reputation validation.
Do I need my own ASN for AWS BYOIP?
Not for the normal Amazon EC2 BYOIP model. AWS advertises the prefix through Amazon ASNs after the range is provisioned and authorized. That is different from leasing IPv4 to originate from your own BGP ASN.
What does LogicWeb handle and what do I handle in AWS?
LogicWeb coordinates the eligible lease and the registry/RPKI changes that require control of the address space. You control your AWS account, the BYOIP provisioning workflow, your AWS resources, and the final advertisement/cutover. The exact verification method depends on the AWS workflow you choose.
Can I keep announcing the same prefix elsewhere while AWS advertises it?
AWS recommends stopping the old advertisement when you start advertising the BYOIP CIDR through AWS. Prepare the AWS resources first and coordinate both sides of the routing change to minimize disruption.
Can I use every address in an IPv4 BYOIP range?
AWS states that after an IPv4 range is brought to EC2, all addresses in the range are usable, including the first and last addresses that would traditionally be treated as network and broadcast addresses.
From planning to production
Need address space for this workload?
LogicWeb publishes IPv4 /24 through /18 and IPv6 /48, /32, and /29 lease options with routing and registry support.