This topic describes how to configure Secure Sockets Layer (SSL) encryption on your ApsaraDB RDS for SQL Server instance. You must enable SSL encryption on your RDS instance and install the SSL certificates issued by certificate authorities (CAs) on your application. SSL is used at the transport layer to encrypt network connections. This allows you to enhance the security and integrity of the transmitted data. However, SSL increases the response time.
- An SSL certificate remains valid for one year. Before the used SSL certificate expires, you must update its validity period. In addition, you must download the required SSL certificate file and configure the SSL certificate again. Otherwise, a client cannot connect to your RDS instance over an encrypted connection.
- SSL encryption may cause a significant increase in CPU utilization. We recommend that you enable SSL encryption only when you want to encrypt the connections with the public endpoint of your RDS instance. In most cases, connections with the internal endpoint of your RDS instance are secure and do not require SSL encryption.
- SSL encryption cannot be disabled after it is enabled. Proceed with caution.
- SSL encryption is not supported for the connections with the read/write splitting endpoint of your RDS instance.
Enable SSL encryption
- Log on to the ApsaraDB for RDS console.
- In the top navigation bar, select the region where the target RDS instance resides.
- Find the target RDS instance and click its ID.
- In the left-side navigation pane, click Data Security.
- Click the SSL Encryption tab.
- Turn on the switch next to Disabled.
- In the Configure SSL dialog box, select the endpoint for which you want to enable SSL encryption and click
Note You can encrypt connections that use either the internal or public endpoint as required.
- Click Download CA Certificate to download the SSL CA certificate files in a compressed package.
The downloaded package contains the following files:
p7b file: used to import CA certificates to the Windows operating system.
PEM file: used to import CA certificates to other operating systems or applications.
JKS file: the Java truststore file. The password is apsaradb. It is used to import the CA certificate chain to Java programs.Note When the JKS file is used in Java, you must modify the default JDK security configuration in JDK 7 and JDK 8. Open the
/jre/lib/security/java.securityfile on the host where your application resides, and modify the following configurations:
jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 224 jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024If you do not modify the JDK security configuration, the following error is reported. Similar errors are also caused by the Java security configuration.
javax.net.ssl.SSLHandshakeException: DHPublicKey does not comply to algorithm constraints
Configure an SSL certificate
Before your application or client can connect to your RDS instance, you must configure an SSL certificate on your application or client after you enable SSL encryption. In this section, MySQL Workbench is used as an example. If you are using other applications or clients, see the related instructions.
- Start MySQL Workbench.
- Choose .
- Enable Use SSL and import the required SSL certificate file.
Update the validity period of an SSL CA certificate
- Update Validity causes the RDS instance to restart. Proceed with caution.
- After you update the validity period, you must download and configure the SSL CA certificate again.