We're introducing dedicated Endpoint Settings and Image Deployment Settings: a first-class way to configure per-endpoint behavior and image-based deployments separately from your app's environment variables.

What's changing

Until now, two categories of configuration were managed through special app environment variables:

• Endpoint behavior — variables like FORCE_SSL, IDLE_TIMEOUT, SSL_PROTOCOLS_OVERRIDE, and STRICT_HEALTH_CHECKS controlled how each endpoint handled traffic, but because they lived in the app environment, every endpoint shared the same values with no way to configure them independently.

• Image deployment — variables like APTIBLE_DOCKER_IMAGE, APTIBLE_PRIVATE_REGISTRY_USERNAME, and APTIBLE_PRIVATE_REGISTRY_PASSWORD specified which image to deploy and how to pull it, but mixing these into the app environment meant they were visible as runtime env vars inside your containers, and in Terraform, made certain types of changes harder than they should have been.

With this release, both are now managed through dedicated settings — endpoints get per-endpoint configuration, and image deployment details live in app-level settings, separate from the container environment.

What's new

• UI: Endpoint settings are now editable directly on each endpoint's configuration page. Image deployment settings are managed on the app's deployment configuration page.

• CLI: Update to aptible-cli v0.26.6 for aptible endpoints:https:modify --force-ssl ... and aptible deploy --docker-image ... style commands now write to settings rather than env.

  • Terraform: Update to aptible/aptible v0.10.0 — the aptible_endpoint and aptible_app resources now accept these as parameters. Consult the Aptible Terraform provider documentation for examples.

Why this matters

Beyond cleaner separation of concerns, this unlocks something that wasn’t possible before: each endpoint can now have independent settings.

• Enforce SSL on one endpoint while leaving another flexible.

• Set different idle timeouts per endpoint.

• Keep deployment details out of the runtime env your application code sees.

Backward compatibility window — action required within 1 month

Your existing configuration continues to work today. If you currently set any of these variables as app environment variables, those values have been or will be automatically migrated to the appropriate endpoints settings, and your apps and endpoints will continue to behave as before.

During the compatibility window:

• You may still set these variables as app environment variables. They will sync to the appropriate settings and a deprecation warning will be emitted on the operation.

• Removing one of these env vars no longer removes the underlying setting. The settings are now independent — clean up your environment freely without affecting your endpoints’ configurations.

Warning: every time you set one as configuration on your app, it will override all endpoint settings! You should remove the app configuration variables as soon as you have confirmed each endpoint has the settings you desire, and cease setting any of these in the app configuration.

What happens in 1 month

On June 1, 2026, we will complete the migration. At that point:

• Operations that set these variables as app env vars will fail. Any deploy or configure operation that passes a non-empty value for the impacted variables listed below.

• Auto-migration will run on the first deploy or configure. If your app still has any of these variables in its environment at that time, they will be automatically synced to the appropriate endpoints settings and removed from the app environment — no data will be lost.

We recommend updating your CLI, Terraform configuration, and any deployment scripts before May 11. See the updated configuration docs for the full list of affected variables and migration guidance, or contact support if you have questions.

If you wish to prevent all use of the deprecated app configuration variables before June 1st, contact Aptible Support.

Impacted variables

The following environment variables are impacted:

• APTIBLE_DOCKER_IMAGE

• APTIBLE_PRIVATE_REGISTRY_USERNAME

• APTIBLE_PRIVATE_REGISTRY_PASSWORD

• DISABLE_WEAK_CIPHER_SUITES

• FORCE_SSL

• IDLE_TIMEOUT

• MAINTENANCE_PAGE_URL

• RELEASE_HEALTHCHECK_TIMEOUT

• SHOW_ELB_HEALTHCHECKS

• SSL_CIPHERS_OVERRIDE

• SSL_PROTOCOLS_OVERRIDE

• STRICT_HEALTH_CHECKS