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.

Background information

SSL is developed by Netscape to provide encrypted communication between a web server and a browser. SSL supports various encryption algorithms, such as RC4, MD5, and RSA. The Internet Engineering Task Force (IETF) upgrades SSL 3.0 to TLS. However, the term "SSL encryption" is retained because it is more common in the communications industry. In this topic, SSL encryption refers to TLS encryption.
Note ApsaraDB RDS supports TLS 1.0, 1.1, and 1.2.

Precautions

  • 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, clients 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

  1. In the left-side navigation pane, click Data Security.
  2. Click the SSL Encryption tab.
  3. In the SSL Settings section, turn on SSL Encryption.
  4. In the dialog box that appears, select an endpoint and click OK.
    Note You can encrypt connections with either the internal or public endpoint based on your business requirements.
  5. Click Download CA Certificate to download the SSL certificate files in a compressed package.

    The compressed package contains the following files:

    • .p7b file: the CA certificate file that is used for a Windows operating system.
    • .PEM file: the CA certificate file that is used for an operating system or application that is not Windows-based.
    • .JKS file: the truststore certificate file that is used for Java. You can use this file to import the CA certificate chain to Java programs. The default password is apsaradb.
      Note When you use the .JKS file in JDK 7 or JDK 8, open the jre/lib/security/java.security file on the host where your application resides. Then, modify the following two default JDK security configuration items: 
      jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 224
jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024
      If you do not modify these configuration items, the following error is reported (in most cases, errors may occur due to the 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 use other applications or clients, see the related instructions.

  1. Start MySQL Workbench.
  2. Choose Database > Manage Connections.
  3. Enable Use SSL and import the required SSL certificate file.

Update the validity period of an SSL certificate

Note
  • The Update Validity operation causes your RDS instance to restart. Proceed with caution.
  • After you perform the Update Validity operation, you must download the required SSL certificate file and configure the SSL certificate again.
Update Validity