Currently we have the setup Route53 -> Regional API Gateway (us-west-2, us-east-1). We want clients to sign the request using SigV4, which takes region into account. I am seeing the below error when testing from postman with region us-east-1, works fine for us-west-2.
{
"message": "Credential should be scoped to a valid region, not 'us-west-2'. "
}
I see since the requests from Route53 are routed by latency-based there can be a chance that the region used for signing would be different from the region the request routed to (like when API in a region is down). Is there a work around for this?