our AEM cloud is currently hosted in Europe North (aka NL).
However, as well as europe, we have customers in Brazil, for whom the site is unusably slow due to the large latency between the regions.
Now AEM fully supports putting publish instances into different locations, to solve this problem, but this feature is missing in the arguably-crippled Cloud version.
The question is what locations are available for hosing the cloud service, and specifically is Brazil supported?
The only option we have is to create and manage complete duplicationions of our sites in each region, which is going to be difficult and expensive, especially given its not possible to create a package with all our images even (due to the package size limitations) so we cant even backup or manually copy content from one env to another in the same region.
On prem might help, but we do not have any technical operations teams in our organization.
Hello @TB3dock, AEM as a cloud service provides creating environments (author and publisher instances) based on different regions as listed below (as of today):
These regions cannot be changed once you create your environment in cloud manager. So you need to carefully create your environment by keeping in mind where your users are located.
Coming to your question where the users are facing slowness from Brazil, AEMaaCS comes with CDN provided by Fastly and if there is slowness experienced in Brazil location then you might need to check with Adobe on how your CDN is handling traffic from that region.
I recommend you to get in touch with your Adobe Support and ask them about Fastly CDN.
Hope this helps!
Thanks for the info. So Adobe do not have Brazil.
Adobes fastly CDN is little faster than no CDN. We see that in brazil, its taking 2s+ to download 40kb images which are fastly cache hits with long max-age.
We can see that performance wise, episerver cloud with Cloudflare is serving content orders of magnitude faster than AEM with Fastly. We are considering putting cloudflare in front, which will help for non dynamic content.
Adobe support is for practical purposes non existent. It takes 2-3 months and constant escalation to get the simplest of requests carried out, such as adding a fix IP to an env (back in the day of legacy IPs which routed all our North Europe egress traffic via USA), and almost as long to get it removed ( so we can use advanced networking fixed IP in europe saving .5s on every egress call. We dont use any support now except when the production system breaks (e.g. when they upgraded java version to one with a know http bug, without telling us, and we were down for several days. We ended up finding the issue and creating a work around weeks before Adobe responded.
@TB3dock - You can find the details here: https://developer.adobe.com/experience-cloud/cloud-manager/guides/api-usage/creating-programs-and-en.... Please note this is not up-to-date as the region keeps on adding from time to time.