Introduction to Sandbox Programs


A Sandbox program is one of the two types of programs available in AEM Cloud Service, the other being a Production program.

A Sandbox is typically created to serve the purposes of training, running demos, enablement, or Proof of Concept (POC)s. They are not meant to carry live traffic. They are not subject to the AEM as a Cloud Service Commitments.

The environments created in a Sandbox are not configured for auto-scaling. Therefore, these environments are not suitable for performance or load testing.

Sandbox programs include Sites and Assets and are auto-populated with a Git repository, a Development environment, and a non-production pipeline. The Git repository is populated with a sample project based on the AEM Project archetype.

Refer to Understanding Programs and Program Types to learn more about the Program Types.

Attributes of Sandbox Programs

Sandbox Programs have the following attributes:

  1. Program Creation: The Sandbox program creation includes automatic:

    • setup of project with sample code and content
    • creation of development environment
    • creation of non-production pipeline deploying to development environment (master branch deploying to development environment)
  2. Solutions: Sandbox programs include AEM Sites and Assets.

  3. AEM Updates: AEM updates can be applied manually to environments in a Sandbox program, and are not automatically pushed.
    Refer to AEM Updates to Sandbox Environments for more details.

  4. Hibernation: Environments in a Sandbox program are automatically hibernated if no activity is detected for a certain period of time. Sandboxes are put into hibernation node after 8 hours of inactivity, after which time, they can be de-hibernated. Hibernated environments can be manually de-hibernated.
    Refer to Hibernating and De-hibernating Sandbox Environments for more details.

  5. Deletion: Sandboxes are deleted after 6 months of being in continuous hibernation mode, after which time, they can be recreated.

On this page