Convox will, if needed, automatically generate a valid SSL certificate for your service via AWS ACM. If you already have a single matching certificate in AWS ACM, in the same region as the rack is installed, for the domain(s) in your service’s configuration, Convox will use the existing certificate.

If you specify a custom domain: attribute for your service be on the lookout for a validation email that will come the first time you deploy.

Pre-generate your certificate

Convox allows you to generate your certificate ahead of time to ensure minimal delay before having your service available during your first deploy.

$ convox certs generate "*" ""
Generating certificate... OK, acm-eeae31f242e9

This will initiate the validation email process, so once you have validated the certificate, it will be ready and you won’t need to do anything further during your first deploy.

Certificate management

To simply list your current certificates:

$ convox certs
ID                          DOMAIN                                                       EXPIRES
acm-89ea927329d7            *  10 months from now
acm-a911c40399a1            *                                                1 year from now
cert-test-1580524125-66328  *.*                                        10 months from now

To delete an existing certificate:

$ convox certs delete acm-a89c0937f196
Deleting certificate acm-a89c0937f196... OK

To import an existing certificate:

$ convox certs import ~/.ssl/ ~/.ssl/my_key
Importing certificate... OK, acm-a89c0937f196

Local Rack

The local rack will use DNS names [process].[app].convox which resolves to your local rack. The local load balancer uses a certificate from a convox CA. On Firefox, you will need to set security.enterprise_roots.enabled to true in about:config or else you will not be able to confirm the security exception of the certificate.