Edge gateways

An edge gateway is located between your application and the internet. It is the gateway through which users access all of your applications within a single environment.
Each environment has at least one gateway which will serve all applications for that environment.

It handles all incoming traffic and will route it to the correct destination: HTTP traffic to your webapp, SSH access to the correct stack item, etc.

But it does much more! For example:

• It will take care of HTTPS offloading, so you do not need to worry about this at all in your application setup.

• It can handle basic authorization to paths of your choosing, so that you have a simple mechanism for shielding staging environments from prying eyes.

• It can allow higher timeouts for legacy time consuming paths.

• It can provide a point of presence in a specific region or country.

• And the list goes on…

Just like with the applications you write, a gateway will not be able to handle an infinite amount of users. For high traffic sites, gateways can be added on the fly, provided the DNS is set up as expected, without downtime to spread load and serve more users.
Naturally, this might also require the application itself to scale along.
There is no limit to the amount of gateways that can be attached to a single environment.