How can I modify the way my app handles SSL?

Aptible endpoints use an AWS Elastic Load Balancer and an Nginx proxy to terminate SSL for all requests.

We offer a few ways to configure the way your app handles SSL by forwarding certain environment variables from your Aptible app configuration to the load balancer and proxies (see further down this page for usage examples of how to set them):

Available variables

FORCE_SSL: Redirect HTTP traffic to HTTPS and enable HSTS

By default, Aptible Endpoints accept traffic over both HTTP and HTTPS.

Your app can detect which protocol is being used by examining a request’s X-Forwarded-Proto header, which is set to https if HTTPS was used and http otherwise.

To disallow HTTP at the Aptible Endpoint entirely, you can set the FORCE_SSL environment variable to true in your app’s configuration (it must be set to the string true, not just any value).

Setting FORCE_SSL=true causes 2 things to happen:

  • Your app’s Endpoints will redirect all HTTP requests to HTTPS.
  • Your app’s Endpoints will set the Strict-Transport-Security header on responses with a max age of 1 year.

Make sure you understand the implications of setting the Strict-Transport-Security header before using this feature. In particular, by design, clients that connect to your site and receive this header will refuse to reconnect via HTTP for up to a year after they receive the Strict-Transport-Security header.


The SSL_PROTOCOLS_OVERRIDE variable lets you customize the SSL Protocols allowed on your Endpoint. Available protocols depend on your Endpoint platform:

  • For ALB Endpoints: you can choose from these 3 combinations: TLSv1 TLSv1.1 TLSv1.2 (default), TLSv1.1 TLSv1.2 and TLSv1.2.

  • For Legacy ELB Endpoints: the format is that of the Nginx ssl_protocols directive. Pay very close attention to the format as a bad variable will prevent the proxies from starting.

Note that the format for ALBs and ELBs is effectively identical: the only difference is the supported protocols. This means that if you have both ELB Endpoints and ALB Endpoints on a given app, or if you’re upgrading from ELB to ALB, things will work as expected as long as you use protocols supported by ALBs (which are stricter).


NOTE: This variable is only available on Legacy ELB Endpoints: on ALB Endpoints, you normally don’t need to customize the ciphers available.

This variable lets you customize the SSL Ciphers used by your Endpoint.

The format is a string accepted by Nginx for its ssl_ciphers directive. Please pay very close attention to the required format, as here again a bad variable will prevent the proxies from starting.

DISABLE_WEAK_CIPHER_SUITES: an opinionated more secure policy for ELBs

NOTE: This variable is only available on Legacy ELB Endpoints: on ALB Endpoints, weak ciphers are disabled by default, so that setting has no effect.

Setting this variable to true (and here again, it has to be the exact string true) causes your Endpoint to stop accepting traffic over the SSLv3 protocol or using the RC4 protocol.

We generally recommend setting this variable to true on all ELB Endpoints nowadays (or better yet: upgrade to an ALB Endpoint where that’s the default).

Setting these variables

To set these variables, use the Aptible CLI:

# Note that the value to enable FORCE_SSL is the string "true", it can't be e.g. "1".
aptible config:set FORCE_SSL=true "SSL_PROTOCOLS_OVERRIDE=TLSv1.1 TLSv1.2" --app $APP_HANDLE
# Note that the value to enable DISABLE_WEAK_CIPHER_SUITES is also the string "true", it can't be e.g. "1".
aptible config:set DISABLE_WEAK_CIPHER_SUITES=true --app $APP_HANDLE

Note: if your app is deployed on Aptible v1 infrastructure you’ll also need to restart it for the setting to take effect via aptible restart --app $APP_HANDLE.

The Enclave Platform