Can you share ui.frontend/src/index.js here? Additionally, include the jsProcessor to the aem-clientlib-generator config in ui.frontend/clientlib.config.js file. jsProcessor: ['min:gcc;languageIn=ECMASCRIPT_NEXT']  

Hi @konstantyn_diachenko, We have raised Adobe support ticket last month regarding same topic. Support team confirmed - Cloud Env IP range is large and is not shared for whitelisting. You need to set Advanced Networking. Dedicated Egress IP would be the right fit for the use case you mentioned. Plea...

From Adobe Support Team I just heard back from the team and they mentioned that we do not support this kind of syntax unfortunately, therefore only 1 file can be used. Also they mentioned that this is not a YAML feature per say but an extension of YAML that some softwares, like Ansible, provide. So,...

Hi @KNan, Can you share OSGi configs and dispatcher filter rules?

I have already raised a ticket with the Adobe Support team and awaiting their response. Thanks.

Inline config works fine, but we prefer managing IP addresses in a separate file for better reusability across different rules. This approach allows us to use the same IP addresses in multiple rules without duplication.

Thanks @Tad_Reeves. I successfully migrated content from AMS to AEMaaCS. However, I encountered an issue during ingestion jobs where no environments were available in the destination dropdown. I later discovered that migration sets need to be created on AEMaaCS, not AMS.

Hi @sachithak792023, Can you share the log here?

We tried to whitelist domains only for specific IP addresses. Given the large number of domains and IP addresses, we aimed to make the configuration more readable and manageable by separating the lists into different files using the YAML lookup method as shown below:  - name: domains-ip-restriction ...

Hi @sachithak792023, We had to remove maven-surefire-plugin from pom.xml.