Skip to content

Connect from the internet

By default, containers, databases, message queues, and other services are not reachable from outside the Nexaa platform. To make external access to your services possible, you can create external connections.

There are multiple types of external connections:

  • Ingress
  • Connection via a shared IP-address
  • Connection via a dedicated IP-address

Ingress

Only applicable to containers, for no extra costs

Ingress is the easiest way to enable external access to a container running on Nexaa. This type of external connection is ideal for web applications or websites which need to be reachable from the internet by (for example) a webbrowser. Only HTTP and HTTPS are supported for ingresses.

  1. Create or configure a Container

    Go to the container creation or configure screen in the Nexaa portal.

  2. Expose the container port

    You need to expose a port for container traffic; this should be the port on which the container is listening (e.g., 5002:5002).

  3. Enable External Access

    Toggle the setting “Make this container accessible from the internet?” to enable.

  4. Add an ingress

    On the ingress tab, click on Add New Ingress and fill in the desired configuration:

    • Domain name: You can enter your custom domain name (e.g., app.example.com) that has the CNAME pointing to nlhaa1-sc1-ingress.tilaa.com. If you leave it empty an autogenerated domain name will be created for you
    • HTTP port: This will be the port you exposed in the previous step (e.g., 5002)
    • Enable TLS (optional): When enabling this all traffic will be redirected to https (secure http) and a certificate will automatically be created (and updated)

  5. (Optional) Restrict Access by IP

    • You can restrict what can access your container by specifying which IP addresses should have access (IP allowlist).
    • If left blank, the container will be accessible from anywhere in the world (0.0.0.0/0, ::/0).

  6. Click Add

    Confirm the configuration and click Add.

  7. Save the Container

    Make sure to click Update Container to apply the new configuration.

Important

Once saved, your container will become available at the specified domain, from the specified allowlist. Please allow time for DNS changes to propagate — this may take several minutes to a few hours depending on your domain registrar.

See also: Connect your domain to a container.

Connection via a shared IP

Applicable to containers, databases and message queues, for no extra costs

A connection via a shared IP-address is ideal if your container is running an application which isn't a web application or website (for example, a database), or to allow external connections to your database or message queue.

For external connections over shared IP Nexaa provides an IPv4 and IPv6 address to you which is shared among multiple customers. You receive a random dedicated port number on this shared IP-address which is connected to the port of your database, message queue or container port. This port is dedicated to your service alone and can be used to connect to it. TCP and UDP are supported for shared IP external connections.

External connections for database and message queue clusters always use TCP and utilize the default port of the internal service. For containers you can choose between TCP or UDP (or both), and you need to provide the port number that you configured for your container.

See the step-by-step guides per service:

Connection via a dedicated IP

Applicable to containers, databases and message queues, for extra costs

A connection via a dedicated IP-address is ideal if your container is running an application which isn't a web application or website (for example, a database), or to allow external connections to your database or message queue, and the external connection requires a specific port number.

For external connections over dedicated IP Nexaa provides an IPv4 and IPv6 address to you which is only available to your services. You can then choose a dedicated port number on this IP-address which will be connected to the port of your database, message queue or container port. TCP and UDP are supported for dedicated IP external connections.

External connections for database and message queue clusters always use TCP and utilize the default port of the internal service. For containers you can choose between TCP or UDP (or both), and you need to provide the port number that you configured for your container.

See the step-by-step guides per service:

Manage external connections

Applicable to containers, databases and message queues

See the step-by-step guides per service: