Secure by default traffic for your deployments

This release tightens the path between your users and what you ship. Visitors who arrive over plain HTTP are now sent to the secure version of your app automatically, and the service that runs your workloads has been brought up to date against known vulnerabilities.

Every visitor lands on HTTPS

Not every link, bookmark or typed address starts with https://. Until now, a visitor who reached your deployment over plain HTTP could end up on an unencrypted connection, or on an error, depending on how they got there. Salus now redirects those requests to HTTPS for you, at the edge, before they ever reach your app.

That means one less thing to configure in every service you deploy. You don’t need redirect rules in your framework or a workaround in your web server: the secure connection is the default, and old http:// links keep working instead of breaking.

Patched against known vulnerabilities

We’ve updated the service that schedules and runs your workloads to address known vulnerabilities in its image. It is part of our ongoing hardening work and keeps the platform underneath your deployments current, so the gap between a fix being published and a fix running on Salus stays short.

This work sits on our side of the line. Your applications, their images and their build configuration are untouched.

---

As always, these changes are live now and require no action on your part. We’d love to hear what you think. Your feedback shapes what we build next.