Amazon Relational Database Service
User Guide (API Version 2014-10-31)

Oracle Secure Sockets Layer

You enable Secure Sockets Layer (SSL) encryption for an Oracle DB instance by adding the Oracle SSL option to the option group associated with an Oracle DB instance. You specify the port you want to communicate over using SSL. You must configure SQL*Plus as shown in this following section.

You enable SSL encryption for an Oracle DB instance by adding the Oracle SSL option to the option group associated with the DB instance. Amazon RDS uses a second port, as required by Oracle, for SSL connections. This approach allows both clear text and SSL-encrypted communication to occur at the same time between a DB instance and SQL*Plus. For example, you can use the port with clear text communication to communicate with other resources inside a VPC while using the port with SSL-encrypted communication to communicate with resources outside the VPC.


You can use Secure Sockets Layer or Native Network Encryption, but not both. For more information, see Oracle Native Network Encryption.

You can use SSL encryption with the following Oracle database versions and editions:

  • All versions, all editions including Standard Edition Two

  • All versions, all editions including Standard Edition Two

  • All versions, Enterprise Edition

  • Version 6 and later, Standard Edition, Standard Edition One, Enterprise Edition


You cannot use both SSL and Oracle native network encryption (NNE) on the same instance. If you use SSL encryption, you must disable any other connection encryption.

TLS Versions for the Oracle SSL Option

Amazon RDS for Oracle supports Transport Layer Security (TLS) versions 1.0 and 1.2. To use the Oracle SSL option, you must use the SQLNET.SSL_VERSION option setting. Following are the allowed values for this option setting:

  • "1.0" – Clients can connect to the DB instance using TLS 1.0 only.

  • "1.2" – Clients can connect to the DB instance using TLS 1.2 only.

  • "1.2 or 1.0" – Clients can connect to the DB instance using either TLS 1.2 or 1.0.

To use the Oracle SSL option, the SQLNET.SSL_VERSION option setting is also required:

  • For existing Oracle SSL options, SQLNET.SSL_VERSION is set to "1.0" automatically. You can change the setting if necessary.

  • When you add a new Oracle SSL option, you must set SQLNET.SSL_VERSION explicitly to a valid value.

The following table shows the TLS option settings that are supported for different Oracle engine versions and editions.

Oracle Engine Version SQLNET.SSL_VERSION="1.0" SQLNET.SSL_VERSION="1.2" SQLNET.SSL_VERSION="1.2 or 1.0" (All editions)



Supported (All editions)



Supported (Oracle EE)


Supported for and higher

Supported for and higher (Oracle SE1)


Not supported

Not supported (Oracle SE)


Not supported

Not supported

Configuring SQL*Plus to Use SSL with an Oracle DB Instance

You must configure SQL*Plus before connecting to an Oracle DB instance that uses the Oracle SSL option.


To allow access to the DB instance from the appropriate clients, ensure that your security groups are configured correctly. For more information, see Controlling Access with Security Groups. Also, these instructions are for SQL*Plus and other clients that directly use an Oracle home. For JDBC connections, see Setting Up an SSL Connection Over JDBC.

To configure SQL*Plus to use SSL to connect to an Oracle DB instance

  1. Set the ORACLE_HOME environment variable to the location of your Oracle home directory.

    The path to your Oracle home directory depends on your installation. The following example sets the ORACLE_HOME environment variable.

    prompt>export ORACLE_HOME=/home/user/app/user/product/12.1.0/dbhome_1

    For information about setting Oracle environment variables, see SQL*Plus Environment Variables in the Oracle documentation, and also see the Oracle installation guide for your operating system.

  2. Append $ORACLE_HOME/lib to the LD_LIBRARY_PATH environment variable.

    The following is an example that sets the LD_LIBRARY_PATH environment variable.

  3. Create a directory for the Oracle wallet at $ORACLE_HOME/ssl_wallet.

    The following is an example that creates the Oracle wallet directory.

    prompt>mkdir $ORACLE_HOME/ssl_wallet
  4. Download the RDS CA certificates file from and then put the file in the ssl_wallet directory.

    The RDS CA certificates file for AWS GovCloud (US-West) is available at

  5. In the $ORACLE_HOME/network/admin directory, modify or create the tnsnames.ora file and include the following entry.

    <net_service_name>= (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCPS) (HOST = <endpoint>) (PORT = <ssl port number>)))(CONNECT_DATA = (SID = <database name>)) (SECURITY = (SSL_SERVER_CERT_DN = "C=US,ST=Washington,L=Seattle,,OU=RDS,CN=<endpoint>")))
  6. In the same directory, modify or create the sqlnet.ora file and include the following parameters.


    To communicate with entities over a TLS secured connection, Oracle requires a wallet with the necessary certificates for authentication. You can use Oracle's ORAPKI utility to create and maintain Oracle wallets, as shown in step 7. For more information, see Setting Up Oracle Wallet Using ORAPKI in the Oracle documentation.



    You can set SSL_VERSION to a higher value if your DB instance supports it.

  7. Run the following commands to create the Oracle wallet.

    prompt>orapki wallet create -wallet $ORACLE_HOME/ssl_wallet -auto_login_only   prompt>orapki wallet add -wallet $ORACLE_HOME/ssl_wallet -trusted_cert -cert $ORACLE_HOME/ssl_wallet/rds-ca-2015-root.pem -auto_login_only

Connecting to an Oracle DB Instance Using SSL

After you configure SQL*Plus to use SSL as described previously, you can connect to the Oracle DB instance with the SSL option. Optionally, you can first export the TNS_ADMIN value that points to the directory that contains the tnsnames.ora and sqlnet.ora files. Doing so ensures that SQL*Plus can find these files consistently. The following example exports the TNS_ADMIN value.

export TNS_ADMIN = ${ORACLE_HOME}/network/admin

Connect to the DB instance. For example, you can connect using SQL*Plus and a <net_service_name> in a tnsnames.ora file.

sqlplus <mydbuser>@<net_service_name>

You can also connect to the DB instance using SQL*Plus without using a tnsnames.ora file by using the following command.

sqlplus '<mydbuser>@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCPS)(HOST = <endpoint>) (PORT = <ssl port number>))(CONNECT_DATA = (SID = <database name>)))'

You can also connect to the Oracle DB instance without using SSL. For example, the following command connects to the DB instance through the clear text port without SSL encryption.

sqlplus '<mydbuser>@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <endpoint>) (PORT = <port number>))(CONNECT_DATA = (SID = <database name>)))'

If you want to close Transmission Control Protocol (TCP) port access, create a security group with no IP address ingresses and add it to the instance. This addition closes connections over the TCP port, while still allowing connections over the SSL port that are specified from IP addresses within the range permitted by the SSL option security group.

Setting Up an SSL Connection Over JDBC

To use an SSL connection over JDBC, you must create a keystore, trust the Amazon RDS root CA certificate, and use the code snippet specified following.

To create the keystore in JKS format, use the following command. For more information about creating the keystore, see the Oracle documentation.

keytool -keystore clientkeystore -genkey -alias client

Next, take the following steps to trust the Amazon RDS root CA certificate.

To trust the Amazon RDS root CA certificate

  1. Download the Amazon RDS root CA certificate from

  2. Convert the certificate to .der format using the following command.

    openssl x509 -outform der -in rds-ca-2015-root.pem -out rds-ca-2015-root.der
  3. Import the certificate into the keystore using the following command.

    keytool -import -alias rds-root -keystore clientkeystore -file rds-ca-2015-root.der
  4. Confirm that the key store was created successfully.

    keytool -list -v -keystore clientkeystore.jks

    Enter the keystore password when you are prompted for it.

The following code example shows how to set up the SSL connection using JDBC.

import java.sql.Connection; import java.sql.DriverManager; import java.sql.SQLException; import java.util.Properties; public class OracleSslConnectionTest { private static final String DB_SERVER_NAME = "<dns-name-provided-by-amazon-rds>"; private static final Integer SSL_PORT = "<ssl-option-port-configured-in-option-group>"; private static final String DB_SID = "<oracle-sid>"; private static final String DB_USER = "<user name>"; private static final String DB_PASSWORD = "<password>"; // This key store has only the prod root ca: private static final String KEY_STORE_FILE_PATH = "<file-path-to-keystore>"; private static final String KEY_STORE_PASS = "<keystore-password>"; public static void main(String[] args) throws SQLException { final Properties properties = new Properties(); final String connectionString = String.format( "jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)(HOST=%s)(PORT=%d))(CONNECT_DATA=(SID=%s)))", DB_SERVER_NAME, SSL_PORT, DB_SID); properties.put("user", DB_USER); properties.put("password", DB_PASSWORD); properties.put("oracle.jdbc.J2EE13Compliant", "true"); properties.put("", KEY_STORE_FILE_PATH); properties.put("", "JKS"); properties.put("", KEY_STORE_PASS); final Connection connection = DriverManager.getConnection(connectionString, properties); // If no exception, that means handshake has passed, and an SSL connection can be opened } }

Enforcing a DN Match with an SSL Connection

You can use the Oracle parameter SSL_SERVER_DN_MATCH to enforce that the distinguished name (DN) for the database server matches its service name. If you enforce the match verifications, then SSL ensures that the certificate is from the server. If you don't enforce the match verification, then SSL performs the check but allows the connection, regardless if there is a match. If you do not enforce the match, you allow the server to potentially fake its identify.

To enforce DN matching, add the DN match property and use the connection string specified below.

Add the property to the client connection to enforce DN matching.

properties.put("", "TRUE”);

Use the following connection string to enforce DN matching when using SSL.

final String connectionString = String.format( "jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)(HOST=%s)(PORT=%d))" + "(CONNECT_DATA=(SID=%s))" + "(SECURITY = (SSL_SERVER_CERT_DN = \"C=US,ST=Washington,L=Seattle,,OU=RDS,CN=%s\")))", DB_SERVER_NAME, SSL_PORT, DB_SID, DB_SERVER_NAME);