Endpoints let you expose your Apps on Aptible Deploy to clients over the public internet or your Stack's internal network.
An Endpoint is always associated with a given Service: traffic received by the Endpoint will be load-balanced across all the Containers for the service, which allows for highly-available and horizontally-scalable architectures.
Aptible Deploy supports several types of Endpoints.
The Endpoint type determines the type of traffic the Endpoint accepts (and on which ports it does so), and how that traffic is passed on to your App Containers:
- HTTP(S) Endpoints accept HTTP and HTTPS traffic and forward plain HTTP traffic to your containers. They handle HTTPS termination for you.
- TLS Endpoints accept TLS traffic and forward it as TCP to your containers. Here again, TLS termination is handled by the Endpoint.
- TCP Endpoints accept TCP traffic and forward TCP traffic to your containers.
Regardless of which placement you choose, you can always enable IP Filtering as a means to further lock down which clients are allowed to connect to your Endpoint.
Aptible Deploy Endpoints let you bring your own Custom Domain.
If you don't have or don't want to use a Custom Domain, you can use an Aptible Deploy-provided Default Domain.
HTTP(S) Endpoints and TLS Endpoints perform TLS termination for you, so if you are using either of those, Aptible Deploy will need a certificate valid for the hostname you plan to access the Endpoint from.
There are two cases here:
- If you are using a Default Domain, Aptible Deploy controls the hostname, and will provide a SSL / TLS Certificate as well.
- However, if you are using a Custom Domain, you will need to provide Aptible Deploy with a Custom Certificate, or enable Managed TLS and let Aptible Deploy provision the certificate for you.
Endpoints enforce idle timeouts on traffic. See Endpoint Timeouts for more information.
Updated 4 months ago