@TB3dock - Did you find a way to do this? I was going through
but don't see a documentation on connecting AEM as Cloud Service
instance with Dynamic Media and generate desired renditions. Update: I
found this -
but feel free to add more...
Our AEM CMS cloud environments are in Europe. Our backend systems (for
login, may payment, purchase etc) are also in Europe. Unfortunately,
Adobe dont give fixed egress IPs by default, and fixed IPs are required
for our AEM instances to communicate to our various backend APIs (they
have to be whitelisted). We have to request fixed IPs for each env, each
time they are rebuilt. The fixed IP they give us is a single USA IP. The
non fixed IPs are from Europe, but they change every day. We noticed
Hi @TB3dock AEMaaCS provides facility to extract logs via Splunk.Also
customer can connect their own splunk feed with AEMaaCS feed. Please
check with your CSE for this feature I hope this will provide more
options for querying specific logs that you need. Regards,Rajashankar.R
Adobe admitted that they updated production to oracle java 11.0.14 which
has a well documented and already fixed P1 bug. This took down our sites
for around 10 hours as we did not know where the problem came from. We
hotfixed our prod env by downgrading http requests to http 1.1. We could
not reproduce in our dev cloud envs as adobe updated prod before they
updated dev. They updated dev 2 days later to the same broken version of
java. In our industry, 10 hours of down time can cost anything from...
Hi everyone, We need to do same redirection (non-WWW to WWW) on our
cloud environment. But we did content path masking via Apache Sling
Resource Resolver Factory configuration. We didn't create any mapping
under /etc/map.. path. Our prod environment have 2 DNS record. One for
www , one for non-www.
https://yoast.com/how-to-remove-www-from-your-url/This document says you
can redirect incoming traffic to www on htaccess file. Could we take
similar approach?Add below RewriteRule on dispatcher conf ...
This solution didnt work for us, because we have so many servlets,
maintained by different teams, returning responses in hundreds of places
in different ways. AEM forces you to choose between UTF-8 or
application/json, you can't have both (without a significant rewrite of
the code and very large cost of retesting every aspect). I would say
that the "side effect" of setting UTF-8 causing the response type to
change to text is a pretty serious bug.
OK, we have got a step further. In the Author AEM instance web control
panel, there is indeed The option to "create dynamic media
configuration" under Hammer->Cloud Services.Creating a configuration you
have to chose:1) title: dev-test2) email: my adobe email3) password: my
adobe password4) region: europe. Then it just says "connection failed"