Your customer could make use of a weighted routing policy (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-weighted), rather than failover routing. The idea here would be to set the weight for the primary to 1 & the secondary to 0, which would route all requests to the primary. When the customer wanted to fail over to the secondary, they'd swap the weights over (primary = 0, secondary = 1).
Having said that, if an unplanned failure of the primary happened, this scheme wouldn't maintain service until the weights were swapped, so it's not an ideal scenario from that perspective.
Will Route 53-with-Failover Based on CloudWatch Work With A Private API-Gateway REST-API?asked 9 months ago
Route 53 query pricingAccepted Answerasked 3 years ago
KDA failover strategyasked a month ago
Direct Connect Failover with two Virtual Interfaces (VIFs)Accepted Answerasked 2 years ago
Elastic Load Balancing and IIOPasked 7 months ago
All Route 53 Alias options greyed outAccepted Answerasked 18 days ago
Route 53 Active-Passive Failover Goes Back And Forth Between Primary and Secondary Due To Unstable Primary, i.e. Does Not SettleAccepted Answerasked 3 months ago
CDK and Route 53 Failoverasked 8 months ago
Route 53 Active-Passive FailoverAccepted Answerasked 3 years ago
Amazon Route53 Geolocation Routing Failoverasked 2 months ago