Appendix B — Internal encryption (mTLS)

mTLS makes the services inside QuantaCloud talk to each other over HTTPS, each proving who it is with a certificate. The certificates are created in your own account, so they are yours alone.

A new stack has mTLS on from the start. The install creates the certificates and installs them before any service starts. Admin → System → Network → Certificates shows every service as Installed and in use; you only come back to it to renew (below).

A stack installed with mTLS off (InternalTlsMode = off, or created before this release) keeps it off through every console update. To switch it on, one update does everything:

#

Where

What

1

AWS Console → CloudFormation → your stack

Update → Replace existing template → upload the quantacloud.yaml of this release → Next.

2

The form

Set ImageTag to this release and InternalTlsMode to required. Leave every other field as it is → Next → tick the acknowledgement → Submit.

3

Wait

About 10–15 minutes, until the stack shows UPDATE_COMPLETE. The update creates the certificates, installs them and switches mTLS on.

4

Admin Console → System → Network → Certificates

Every service shows Installed and in use.

Note

Certificates you already created on that page are used as they are; any that are missing are added.

Warning

A command-line update that leaves out InternalTlsMode takes the default, required, and switches mTLS on. To keep a stack off, pass InternalTlsMode=off.

Renewing. Service certificates last 397 days; the page warns 30 days before they expire. Click Create all certificates and Install in AWS again. Because mTLS is on, the services restart by themselves to load the new certificates (about 5 minutes; sign-in may pause briefly).

Switching it off again. Update the stack with InternalTlsMode = off.

Your own certificate authority (advanced). Instead of the Admin Console you can supply your own certificates as Secrets Manager secrets and enter their ARNs in the Section 6 fields; each one replaces the stack’s own secret:

Field

Secret contents

Certificate

InternalCaBundleSecretArn

The CA certificate(s), PEM text

—

AdminApiTlsSecretArn

JSON {"cert":"<PEM>","key":"<PEM>"}

CN admin-api, SAN admin-api.<stack name>.local

DriveApiTlsSecretArn

same shape

CN drive-api, SAN drive-api.<stack name>.local

GridApiTlsSecretArn

same shape

CN grid-api, SAN grid-api.<stack name>.local

DeviceSyncTlsSecretArn

same shape

CN device-sync, SAN device-sync.<stack name>.local

EdgeNginxTlsSecretArn

same shape

CN edge-nginx (client certificate)

WebTlsSecretArn

same shape

CN web (server certificate of the web task)

Each leaf certificate needs both the server auth and client auth extended key usages. With required, the stack’s own database also requires encrypted connections.