All traffic to Aiven services is always protected by TLS. It ensures that third-parties can’t eavesdrop or modify the data while in transit between Aiven services and the clients accessing them.
Every Aiven project has its own private Certificate Authority (CA) which is used to sign certificates that are used internally by the Aiven services to communicate between different cluster nodes and to Aiven management systems.
Some service types (listed below) uses the Aiven project’s CA for external connections. To access these services, you need to download the CA certificate and configure it on your browser or client.
For other services a browser-recognized CA is used, which is normally already marked as trusted in browsers and operating systems, so downloading the CA certificate is not normally required.
All the services in a project share the same Certificate Authority(CA)
Most of our services use a browser-recognized CA certificate, but there are exceptions:
Aiven for PostgreSQL® requires the Aiven project CA certificate to connect when using verify-ca or verify-full as
sslmode. The first mode requires the client to verify that the server certificate is actually emitted by the Aiven CA, while the second provides maximum security by performing HTTPS-like validation on the hostname as well. The default
sslmode, require, ensures TLS is used when connecting to the database, but does not verify the server certificate. For more information, see the PostgreSQL documentation
Aiven for Apache Kafka® requires the Aiven project CA certificate, and also the client key and certificate.
For these services you can Download a CA certificate from the service overview page.
Older/existing services may be using the Aiven project’s CA, you can request switching to a browser-recognized certificate by opening support ticket and letting us know.