Skip to content

Connect from the internet

By default, containers, databases, queues, etc are not reachable from outside the Nexaa platform. To make this possible, you can create external connections.

We have a couple of types of external connections:

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

Ingress

Only suitable for containers

Ingress is by far the most easy way of connecting to the application in your container. This is the best way if you have a web application or website which needs to be reachable from the internet by (for example) a browser.

  1. Create or Edit a Container

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

  2. Expose the container port

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

  3. Enable Public Access

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

  4. Add an ingress

    Here you can fill in some details of your domain and if you want to enable TLS (https):

    • 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 access by specifying allowed IP addresses.
    • If left blank, the container will be accessible from anywhere in the world.

  6. Click Add

    Confirm the domain entry and click Add.

  7. Save the Container

    Make sure to save your container changes to apply the domain configuration.

Imporant

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

Connection via a shared IP

Suitable for containers, databases and message queues, no extra costs

A connection via a shared IP is ideal if your container is running an application, which isn't a web application or website (for example, a database). A connection via a shared IP can also be used to connect to your database or message queue directly.

The working of such a connection is we provide an IPv4 and IPv6 address to you which is shared among multiple customers. We define the external port and connect it to the default port of your database, message queue or container port. In case you want to connect to a port of the container, you also need to provide which port and which protocol (TCP, UDP or both) as this can be different per container.

  1. Create or Edit a Container, database or message queue

    Go to the container, database or message queue creation or edit screen in the Nexaa portal.

  2. Expose the container port (only necessary for containers)

    You need to expose a port for container traffic on which the container is listening to (e.g. 3306:3306).

  3. Enable Public Access (only necessary for containers)

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

  4. Add an external connection

    Here you get a small wizard where you will be walked through creating an externall connection.

    1. Select Shared IP and click Next
    2. for containers:
      • Select the port which you exposed in the previous step (e.g. 3306)
      • Select the protocol (TCP, UDP or both). In most cases just TCP is enough
    3. for containers, databases and message queues:
      • You can restrict access by specifying allowed IP-adresses in the IP Allow list section (remember to add your IPv6 address as well if you have one)
      • If left blank, the container, database or message queue will be accessible from anywhere in the world.
    4. You get an overview. Click "Enable" to add the external connection

  5. Save

    Make sure to save your container, database or message queue changes to apply the domain configuration.

Imporant

Once saved, your container will become available at the shared IP which is assigned to your container, database or message queue. you can find this IP in the overview of your container, database or message queue

Connection via a dedicated IP

Suitable for containers, databases and message queues, gives extra costs

The dedicated IP option is the same as the shared IP with some small differences. You will get an IPv4 and IPv6 address which is allocated specially for you. You can use these IP's to connect to any of your containers, databases or message queues. No other customers can make use of these IP-addresses You can also choose yourself which external port can connect to which container port, database or message queue.

This option is the right option when you need to decide which external port needs to be connected to the container port.

  1. Create or Edit a Container, database or message queue

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

  2. Expose the container port (only necessary for containers)

    You need to expose a port for container traffic on which the container is listening to (e.g. 3306:3306).

  3. Enable Public Access (only necessary for containers)

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

  4. Add an external connection

    Here you get a small wizard where you will be walked through creating an external connection.

    1. Select Dedicated IP and click Submit request
    2. For now, you need to fill in a form which will send your request to us. We will configure the connection for you and as soon as it's ready you will be notified.