Table of Contents

Search

  1. Preface
  2. Introduction to Amazon S3 V2 Connector
  3. Connections for Amazon S3 V2
  4. Amazon S3 V2 sources and targets
  5. Mappings and mapping tasks with Amazon S3 V2
  6. Migrating a mapping
  7. Upgrading to Amazon S3 V2 Connector
  8. Data type reference
  9. Troubleshooting

Amazon S3 V2 Connector

Amazon S3 V2 Connector

Client-side encryption for Amazon S3 V2 sources

Client-side encryption for Amazon S3 V2 sources

Client-side encryption is a technique to encrypt data before transmitting the data to the Amazon S3 server.
You can read a client-side encrypted file in an Amazon S3 bucket. To read client-side encrypted files, you must provide a master symmetric key or customer master key in the connection properties. The Secure Agent decrypts the data by using the master symmetric key or customer master key.
When you generate a client-side encrypted file using a third-party tool, metadata for the encrypted file is generated. To read an encrypted file from Amazon S3, you must upload the encrypted file and the metadata for the encrypted file to the Amazon S3 bucket.
You require the following keys in the metadata when you upload the encrypted file:
  • Content-Type
  • x-amz-meta-x-amz-key
  • x-amz-meta-x-amz-unencrypted-content-length
  • x-amz-meta-x-amz-matdesc
  • x-amz-meta-x-amz-iv

Reading a client-side encrypted file

Perform the following tasks to read a client-side encrypted file:
  1. Provide the master symmetric key when you create an Amazon S3 V2 connection.
    Ensure that you provide a 256-bit AES encryption key in Base64 format.
  2. Copy the
    local_policy.jar
    and
    US_export_policy.jar
    files from the following directory:
    <Secure Agent installation directory>/jdk/jre/lib/security/policy/unlimited/
  3. Paste the files in the following directory:
    <Secure Agent installation directory>/jdk/jre/lib/security/
  4. Restart the Secure Agent.

0 COMMENTS

We’d like to hear from you!