Adding the standby page
Otherwise known as the "Turn it On" page, here is an overview of what the Standby page is, what it is used for and how it is configured.
Last updated
Otherwise known as the "Turn it On" page, here is an overview of what the Standby page is, what it is used for and how it is configured.
Last updated
When cloud Resources have been powered down, visitors to an Application on an Environment which has been powered down would ordinarily see an unfriendly 5xx error page as the Application is not reachable whilst its Resources (such as servers) are powered off.
One of the great features of Turn it Off is the ability to present a friendly, non-technical standby page (often known as the "Turn it Off" page) to business users and moreover, give them the ability to power on the Application if they need to use it.
This allows you to give your internal application users the control, in order to restart stopped resources. An example of this would be a marketing team wanting to use their staging or UAT site at a weekend when a scheduled turn off was in place.
Typically this page is used in the scenario where an Application is being used in a Non-Production setting, such as for example, functional testing, integration testing, staging etc.
Users will see a page like this upon visiting the Application when Turn it Off has powered it down:
Using the Standby page is optional, as shown in the Wizard used as you onboard your Environments and Resources.
The Standby page works by deploying an "Agent" in your Cloud provider account whilst Resources are powered down. This Agent manages the switching of traffic between your Application and the 'Turn it Off" page shown above and is deployed on a micro virtual machine.
More detail can be found here on Configuring the Standby Agent.
Whilst the agent allows your users to turn the environments on, this is not the only way to turn on the environment. It can also be done via the application.
To do so, Navigate to the environment and a button will appear under Manual intervention that will trigger an environment turn on:
Turning on your environment is dependent on the type of resources in your environment. Typically the turn on process for an environment with Virtual Machines or services that are backed by Autoscaling (Fargate, Elastic Beanstalk) are turned on within 3-5 minutes, however there are edge cases such as RDS whereby it can take a while for the RDS instance to be in a "ready" state.
In the unlikley event that your environment is stuck in a "pending" state for some time, please raise a support ticket as a Priority 1.
