Hi @_CL ,Yes, managing numerous environment variables can be challenging. I recommend:Create a JSON file in your code repository for each environment to store these variables.Use the Cloud Manager API to add or update environment variables programmatically.Refer to the Cloud Manager API documentatio...

Hi @_CL , In AEM as a Cloud Service (AEMaaCS), we have only the dev, stage, prod, and rde runmodes are available - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/deploying/overview#runmodes . Configuration can be set under the dev runmode, with envir...

Follow the approaches below:Update Environment Variables in Cloud Manager:To override publish and preview domains, adjust the AEM_CDN_DOMAIN_PUBLISH and AEM_CDN_DOMAIN_PREVIEW environment variables directly in Cloud Manager.Use Custom Environment Variables:Define custom variables (e.g., CUSTOM_EXTER...

Creating a separate repository to convert the existing full-stack project to be compatible with the front-end pipeline is unnecessary. Instead, some modifications are needed in the existing project:Parent pom.xml: Update the parent POM file to remove ui.frontend from the buildContext-Aware Configura...

Did you check this documentation - https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/operations/curl#replication-agent 

You can achieve this using Sling Dynamic Include. Refer to this link for more details. Write the logic on the server side to validate if the user has the correct subscription.

You don't need to run the full stack pipeline. You can use the config pipeline instead. For more details, refer to the official documentation: Config Pipeline in AEM as a Cloud Service.

You can use the Cloud environment variables and update this for specific environments. This can be assigned to an OSGI config variable. { "environmentType":"$[env:ENVIRONMENT_TYPE]" } 

We faced a similar issue due to load in the distribution queue. I recommend checking the author distribution queue to see if the deactivation request is still present. If the queue has more items, processing these requests can cause delays or failures.

We can achieve this using basic authentication in CDN. Refer this URL:https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn-credentials-authentication#basic-auth and this blog for more details - https://aemtechblog.medium.com/basic-auth...