Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange for Amazon Redshift
  3. PowerExchange for Amazon Redshift Configuration
  4. Amazon Redshift Sources and Targets
  5. Amazon Redshift Mappings
  6. Amazon Redshift Pushdown Optimization
  7. Amazon Redshift Sessions
  8. Appendix A: Amazon Redshift Data Type Reference
  9. Appendix B: Troubleshooting

PowerExchange for Amazon Redshift User Guide for PowerCenter

PowerExchange for Amazon Redshift User Guide for PowerCenter

Client-side Encryption

Client-side Encryption

Client-side encryption is a technique to encrypt data before transmitting the data to the Amazon Redshift server.
To enable client-side encryption, you must provide a master symmetric key, which is a 256-bit AES encryption key in Base64 format in the connection properties. The PowerCenter Integration Service encrypts the data by using the master symmetric key or customer master key.
The PowerCenter Integration Service encrypts the files that are uploaded to Amazon S3 at the client-side. If you enable both server-side and client-side encryption for an Amazon Redshift target, then the client-side encryption is used for data load. If you provide customer master key ID generated by AWS Key Management Service in the Amazon Redshift connection properties, then the server-side encryption is used for data load. To enable client-side encryption, perform the following tasks:
  1. Provide the master symmetric key when you create an Amazon Redshift connection. Ensure that you provide a 256-bit AES encryption key in Base64 format.
  2. Update the security policy JAR files to support encryption with maximum security.
    Update the
    local_policy.jar
    and the
    US_export_policy.jar
    files in the following directory:
    <Informatica Installation Directory>\ava\jre\lib\security
    . You can download the JAR files supported by your JAVA environment from the Oracle website.
  3. Select
    Turn on S3 Client Side Encryption
    as the encryption type in the target session properties.

0 COMMENTS

We’d like to hear from you!