PuppyIP Resource Center
Network And Account Troubleshooting 6 min Published 2026-11-20

HTTPS fails after an AWS Transform F5 BIG-IP migration? Check listeners, VIPs, and targets

If HTTPS fails after an F5 BIG-IP migration, find the source virtual server in your AWS Transform plan and confirm that a load balancer was generated. Add the HTTPS listener for a source client-ssl profile, register test targets, and verify the DNS name or VIP after health checks pass.

AWS Transform F5 BIG-IP Load balancing HTTPS

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • AWS Transform can migrate supported F5 BIG-IP load balancing when you upload a source network file and map the network to new VPCs. Generated load balancers use the internal scheme.
  • A source F5 client-ssl profile requires an HTTPS listener after deployment. Generated target groups start empty, with registration needed during testing and cutover.
  • ALBs use the new load balancer DNS name. NLBs generally retain the VIP mapped to AWS, with exceptions listed in the migration plan.

Check whether the plan actually generated a load balancer

AWS announced AWS Transform support for F5 BIG-IP LTM migration on November 17, 2026, and published a worked example on November 18. The documented workflow requires uploading a source network file, mapping the source network to new VPCs, and choosing <code>Include load balancers</code>. Supply the F5 BIG-IP configuration separately. In the plan, locate the entry by its source virtual server name, VIP, and port.

HTTP and HTTPS virtual servers map to Application Load Balancers (ALBs). TCP and UDP map to Network Load Balancers (NLBs). If the entry is marked skipped, read the reason first. Examples include disabled entries, attached iRules or LTM policies, IPv6 VIPs, pools spanning network segments, and an ALB with subnets in fewer than two Availability Zones. Account for that entry in the migration before troubleshooting post-deployment traffic.

Check the HTTPS listener, certificate, and port

If the source virtual server uses an F5 <code>client-ssl</code> profile, AWS Transform deploys the load balancer without an HTTPS listener. This is a documented follow-up step. Check the original port and the certificate referenced by the source configuration. Have an authorized administrator follow your organization's process to import the certificate material into AWS Certificate Manager (ACM) in the target account and Region. Add an HTTPS listener on the appropriate port that forwards to the corresponding target group.

From a network approved for access to the destination, test the service hostname that clients will actually use. Check the certificate name, chain, and listener port. If the TLS handshake completes but the application still fails, check forwarding and the target group. Generated load balancers are internal. If the service requires internet-facing access, handle that requirement separately in the cutover plan.

Check that usable instances are registered in the target group

AWS Transform deploys empty target groups. During test and cutover instance launches, AWS Transform asks whether to register an instance in the target group associated with its source server. Register it when it is ready to receive the intended test or production traffic. Check the registered instances, protocol, port, and health against the plan.

If registered targets remain unhealthy, check the health-check path and response status, the network path from the load balancer, the target security group, and the port on which the application listens. F5 monitors and AWS target group checks can use different success criteria. Verify a healthy application response before changing the checks.

Verify the service end to end before updating DNS or client addresses

An ALB does not retain the address of the source virtual server. At cutover, point the application DNS record at the new ALB DNS name and replace hard-coded source IPs in clients. An NLB generally retains the VIP as mapped to AWS. The migration plan flags exceptions. If a client connects by IP, verify the final address in the plan.

From the intended internal network, test HTTPS and a representative application request using the service hostname. Verify that the request reaches the intended target. Record the load balancer, listener, target health, and observed address. Cut over production traffic when you've verified the service behavior required by the migration plan.

Sources

Frequently Asked Questions

The plan migrated my HTTPS service. Why is the listener absent in AWS?

When the source F5 virtual server uses client-ssl, AWS Transform deploys the load balancer first. Import the corresponding certificate material and add an HTTPS listener on the original port as indicated in the plan.

Why does the application receive no traffic after I add the listener?

Check the listener's forwarding target and target group registration. Generated groups start empty. After registration, check the target port and health status.

Can clients keep using the original VIP?

An ALB uses a new load balancer DNS name. NLBs generally retain the source VIP as mapped to AWS. Check the plan for the actual address and any exceptions.