Table of Contents

Search

  1. Preface
  2. Introduction to Microsoft SQL Server Connector
  3. Connections for Microsoft SQL Server
  4. Synchronization tasks with Microsoft SQL Server Connector
  5. Mappings and mapping tasks with Microsoft SQL Server Connector
  6. Replication tasks with Microsoft SQL Server
  7. Data type reference

Microsoft SQL Server Connector

Microsoft SQL Server Connector

Configure SSL with the serverless runtime environment

Configure SSL with the serverless runtime environment

You can use the serverless runtime environment with Microsoft SQL Server Connector to connect to an SSL-enabled Microsoft SQL Server database.
Before you configure a secure Microsoft SQL Server connection using the serverless runtime environment, complete the following prerequisite tasks to add the SSL certificates to the serverless runtime location:
  1. Create the following structure for the serverless agent configuration in AWS or Azure:
    <Supplementary file location>/serverless_agent_config
  2. Add the truststore certificate in the Amazon S3 bucket or Azure container in the following location in your AWS or Azure account:
    <Supplementary file location>/serverless_agent_config/SSL
  3. Copy the following code snippet to a text editor:
    version: 1 agent: agentAutoApply: general: sslStore: - fileCopy: sourcePath: SSL/<TrustStore_filename>
    where the source path is the directory path of the certificate file in AWS or Azure.
  4. Ensure that the syntax and indentations are valid, and then save the file as
    serverlessUserAgentConfig.yml
    in the following AWS or Azure location:
    <Supplementary file location>/serverless_agent_config
    When the .yml file runs, the SSL certificate is copied from the AWS or Azure location to the serverless agent directory.
  5. In the Microsoft SQL Server connection properties, specify the following certificate path in the serverless agent directory in the
    Trust Store
    field:
    /home/cldagnt/SystemAgent/serverless/configurations/ssl_store/<cert_filename>

0 COMMENTS

We’d like to hear from you!