WhyWhen API Cloud launched initially there was only one location – AWS US East datacenter – in which you could publish your APIs. This has been a problem for some of our global customers for two reasons:
- Regulations: while API gateway does not store any end-user data and is merely enforcing policies and passing the calls to the backend, some companies would like to be on the safe side in terms of compliance and keep not just the backend but also the gateway within their jurisdiction,
- Performance: if both your backend service and your subscribers are in Australia, having the gateway in the US adds the extra hop to the other side of the globe and the corresponding wait for API consumers.
WhereThe following datacenter locations are available:
- US East,
- US West,
- Brazil (São Paulo),
- EU (Ireland),
- EU (Frankfurt, Germany),
- UK (London),
- Tokyo, Japan,
- Sydney, Australia,
- Seoul, South Korea,
- Mumbai, India.
|Starter||Getting Traction||Medium||Large||Extra Large|
|US East only||Pick any datacenter of choice||Up to 3 datacenters||Up to 7 datacenters||Unlimited number of AWS datacenters of choice|
How it works
- You submit a request by filing an API Cloud support ticket and tell us in which regions you would like your gateway to be placed and the custom URL you would like to be used,
- We work with you on configuring DNS. The following options are available:
- All traffic by default routed to a specific regional gateway: for example, a European company might decide that all traffic should go through a gateway in EU.
- Traffic is routed based on geographic location: European consumers are routed to the European hub, Australian - to an Australian hub, and so on.
- In addition to this default routing, we can set up gateway URLs specific to regional gateways so you can give your subscribers direct URLs to target your API gateways in the US, Europe, Brazil, Australia, Singapore, India, China, and so on.