Skip to main content

Ingress

We create a unique ingress domain for each application environment. This domain is utilized to route traffic to your application.

Why​

Creating unique ingress domains for each application environment enables us to change the region where your applications are hosted (if necessary) without any required changes from your end.

This adds simplicity to features like the Move Region.

How it Works​

Each application environment ingress is associated with one of our ingress domains based on its region (see the list below).

When a new application environment is initiated, a CNAME is automatically generated in the following format: {account}-${app}-{env}.zcloud.services, pointing to the specific ingress domain of your region.

Here are the ingress domains assigned to each respective region:

  • US-5: ing-us-5.zcloud.ws
  • US-3: ing-us-3.zcloud.ws
  • EU-1: ing-eu-1.zcloud.ws
  • EU-2: ing-eu-2.zcloud.ws

For instance, consider an account foo with a website application that has a prod environment in the US-5 region. The CNAME would appear as foo-website-prod.zcloud.services and would point to the ingress domain ing-us-5.zcloud.ws.

Please bear in mind that our regional ingress domains should not be used directly because they can change. Always use the CNAME assigned to your application environment.

Connection timeouts​

By default, the ingress closes a connection when your app sends no data on it for 60 seconds. This applies to long requests, streaming responses and WebSockets.

WebSockets and other long-lived connections stay open as long as data flows. Send a keep-alive ping more often than every 60 seconds; Meteor's DDP heartbeat already does this. If you need a longer timeout, contact support.