I have a lambda-backed api gateway that i deployed in two regions. These two API's are totally identical. I have two different URL's like
My idea was defining the same custom domains in two regions and using Route53 geolocation feature, serving the api from the nearest region to the user. But, after defining the custom URL in one region, when I try to define in the second region I get an error saying that this domain is already defined in another cloudfront distribution.
Is this a bug or which strategy can i follow to multi-region deployment of API Gateway.