@LyonMartin Unfortunately, you can not do that locally. This is not even possible with RDEs in the AEM as cloud.

@nusratja Looks like you are stripping off the extension (.html in this case) using a rewrite rule either at dispatcher or at the CDN level if you are using something like an Akamai in front of AEM. You might want to check that out first.

@IshaJa In order to be able to proceed with the PEN test, you will need to get in touch with your Adobe Account Team who will fill out a non-disclosure form with you.   https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-19808  

@nivethaS You can follow the below for creation of CFs programmatically.   Resource fragmentResource = resourceResolver.getResource(fragmentPath); if (null != fragmentResource) { ContentFragment contentFragment = fragmentResource.adaptTo(ContentFragment.class); if (nu...

@Rivianwild You might want to check with your Adobe account TAM. Also, You can create custom product profiles as well if needed.

@Mario248 Yes it is. I have tested version 17.0.0 working perfectly with AEM as cloud service.

@AliSyed1  check if there is any custom configuration that you are using that is tied to the run modes. If yes, you might want to see if that configuration is getting applied for your dev1 environment.

@_CL  Once the script is added into the HEAD , it will show up in the source html code as well as in the network tab. you should see something like a gtm.js show up in the network tab.  

@Ankan_Ghosh check this out -  https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/programmatically-know-where-page-is-being-published-preview/td-p/608407  

@thoufikcse  I would agree with @Saravanan_Dharmaraj . For the most accurate information on any licensing cost questions , TAM is your guy. Also, with AEMaCS there are multiple types of costs involved. One would be just the environment provisioning costs and another would be based on the amount of t...