To protect your data from security threats, Rackspace KaaS ensures that all connections between the internal components and external systems are compliant with the cloud industry best practices by using Secure Sockets Layer (SSL) and SSL certificates. Rackspace KaaS uses OpenSSL self-signed certificates for the various components of the Rackspace KaaS deployment.
In a secure system, components communicate with each other by sending secure messages that are signed by a certificate authority (CA), a third-party that verifies the identities of the communicating parties. If one component needs to talk to an unfamiliar component, it confirms that component’s identity by using a CA that is known to both of these components. If the first component cannot confirm the identity of the second component, it refuses the connection.
Rackspace KaaS uses the Kubernetes
cert-manager to help issue Rackspace
KaaS certificates from appropriate CAs, make sure certificates are valid and
up-to-date, and attempt to renew certificates.
In EKS, cert-manager integrates with Amazon Route53 for automatic, DNS-based certificates.
In RPCO and RPCR,
cert-manager uses a self-signed CA. Customers can use
cert-manager to request valid Lets Encrypt certificates that use HTTP for
Specific usage instructions#
There are currently no specific usage instructions for the Rackspace KaaS Certificate Management service.