How do I configure multiple routing ports while migrating from CLB to ALB?
I used the Launch ALB Migration Wizard.
The change is that the number of ports in the routing tab has been reduced from 2 to 1. (The relevant information is attached to the link.) link image
If it is set to one, a 504 gateway timeout error occurs.
Is there a way to set two routing ports during migration?
I understand that you have multiple listeners for your CLB. While using migration using console, If the Classic Load Balancer has multiple listeners, the wizard uses the listener port with the lowest value for the target group port. Each instance registered with these listeners is registered with the target group on the listener ports for all the listeners
This is why you are seeing just one target group for your two backend port.
Is there a way to set two routing ports during migration? You can use the Option 2, https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/migrate-classic-load-balancer.html#load-balancer-copy-utility which should create two target groups for each of the listener backend port considering you are using different backend ports for the CLB listeners.
where are you from?
Custom Routing setup helpasked a year ago
How to make ALB seamlessly re-forward to a healthy target?asked 12 days ago
How do I configure multiple routing ports while migrating from CLB to ALB?Accepted Answerasked 2 months ago
Doesn't Route53 Weighted Routing switch on every request?asked 2 months ago
Network Load Balancer Headersasked 5 years ago
ALB DNS name with 3 AZs enabled resolves to 1 IPasked 2 months ago
Customer would like to migrate CLB to NLB/ALB.Accepted Answerasked 3 years ago
ALB Queries, Route53Accepted Answerasked a year ago
ALB Routing to Unhealthy TargetsAccepted Answerasked 3 years ago
Health checks when using ALB as target of NLBasked 4 months ago