Environment Idling

To help reduce resource consumption, amazee.io Cloud implements idling for development environments. Our typical idling interval is 4 hours of inactivity on an environment, but this is subject to change.

In most cases, if you're actively using an environment it should not get idled.

To un-idle an environment, you can visit a URL for the environment, access the environment via SSH, or trigger a deployment. To prevent environments from being un-idled by internet activity, our un-idling process performs a request using Javascript when accessed by a URL.

In some cases this Javascript verification process can cause problems if you have external tools that hit your URLs and can't execute the verification. In these cases, it is possible to configure the routes in your environments .lagoon.yml file to disable this request verification process.

If you have autogenerated routes only, then you can use the following in your .lagoon.yml file.

routes:
  autogenerate:
    disableRequestVerification: true

If you have a custom route on a development environment, you can use the following. This has to be defined on each route though if you have more than one.

environments:
  develop:
    routes:
      - node:
          - develop.example.com:
              disableRequestVerification: true

While it is possible to disable environment idling, we recommend that the verification disabling is done before disabling idling all together. See the Lagoon documentation for more information on disabling idling.