Accessing DEV, QA and UAT Author and Publisher from Non-Adobe Enviroments

[Shiv_Prakash_Patel]

To access Adobe Experience Manager (AEM Managed Services) Author instances in QA and UAT environments from a non-Adobe environment, which approach is recommended:

• Setting up a VPN with IP whitelisting to access the Author instance directly
• Accessing the Author instance through the Dispatcher by enabling it in the Dispatcher configuration

If there is any official documentation supporting the recommended approach, please provide the relevant links.

Thanks

[chaudharynick]

Hi @Shiv_Prakash_Patel 

To securely access AEM instances, it’s recommended to set up a VPN with IP whitelisting. This approach ensures that only authorized users from specified IP addresses can access the Author instance, enhancing security.

please refer to Adobe’s official documentation for configuring the VPN: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/security/configu...

[Shiv_Prakash_Patel]

Hi @chaudharynick ,

Do you know any official document or section where the recommended approach to setting up a VPN is mentioned?

Thanks,

[chaudharynick]

Hi @Shiv_Prakash_Patel ,

I don't have any official document where that clearly states that but from architecture standpoint it's the best way to interact for security and ensures only authorized users from specific IP addresses can interact with the AEM

You can refer to this blog as well for more details https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/networking/vpn

[arunpatidar]

we used IP whitelist in AMS and on-prem to allow access.

[giuseppebag]

For AEM Managed Services Author instances, the recommended approach is VPN with IP whitelisting. This approach:

• Provides more secure access to Author instances
• Follows Adobe's security best practices
• Prevents exposure of the Author tier to the public internet

Accessing the Author through a Dispatcher is generally not recommended because:

• Author instances contain sensitive functionality not meant for public access
• May introduce security vulnerabilities
• Goes against AEM architecture best practices

If the VPN setup is challenging, you can discuss with your Adobe Customer Success Engineer alternative secure access methods specific to your implementation.