Amazon S3 Connection
Learn how to create a connection to Amazon S3.
Written by Andrea Harvey
Updated at July 22nd, 2025
Table of Contents
Overview
The Amazon S3 connector in DryvIQ enables you to analyze, migrate, copy, and synchronize files between your Amazon S3 account and cloud storage repositories, as well as on-premises network file shares. The first step is to establish the connection by providing the necessary connection information for DryvIQ to connect to the platform. The connector can be created using any account with permissions to access the content.
Creating a Connection
- Expand the Manage section in the left navigation menu.
- Click Connections.
- Click Add connection.
- Select Amazon S3 as the platform on the Add connection modal.
- Enter the connection information. Reference the table below for details about each field.
- Test the connection to ensure DryvIQ can connect using the information entered.
- You will see a "Connection test succeeded" message on the Add connection modal when DryvIQ establishes connection. (If you don't see this message, verify the information you entered.)
- Select Done to finish creating the connection.
| Field | Description | Required |
|---|---|---|
| Display as |
Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists.
If you do not add a display name, the connection will automatically be named, “Amazon S3.” DryvIQ recommends you enter a name that more readily identifies the connection, especially if you will be creating multiple connections. |
Optional |
| Access Key | Enter the access key ID required to access the account. | Required |
| Secret Key | Enter the secret key required to access the account. | Required |
| Region | Select the AWS region assigned to the account (if applicable). | Optional |
| Service URL | If you have a custom Amazon S3 implementation, enter the service URL that needs to be used. You must enter the full URL including https:// at the the beginning. The URL will override the Region value. | Optional |
| Use Server-Side Encryption | Select if the account uses server side encryption. | Optional |
| Storage Class | Select the storage class: Standard, Standard-Infrequent Access, Reduced Frequency, or Glacier. | Optional |
Features and Limitations
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms, allowing you to configure actions based on Job Policies and Behaviors. The information below is platform-specific. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.
| Supported Features | Unsupported Features | Other Features/Limitations |
|---|---|---|
| Version Preservation |
Timestamp Preservation |
File Size Maximum: 5 TB |
| Metadata Map |
Author/Owner Preservation |
Path Length Maximum: No maximum |
|
Permission Preservation (See below.) |
File Lock Propagation |
Restricted Types: None |
|
Mirror Lock Ownership |
Segment Path Length: No maximum | |
|
Account Map |
DryvIQ restricts the use of / to prevent nesting in buckets.
Amazon doesn’t restrict characters but provides Object Key and Metadata guidelines you should follow. |
|
|
Group Map |
||
|
|
User Impersonation |
|
|
Tags Map |
Permission Preservation
Amazon S3’s permission structure affects how DryvIQ can apply permissions. Please be aware of the following limitations for permission preservation.
- Amazon S3 has a policy limit of 20,000 per bucket. DryvIQ will likely hit this limit if too many permissions are migrated.
- Amazon S3 supports permissions on folders only.
- Amazon S2 supports inheriting permissions from parent folders. It does not currently support permissions disinheritance (breaking permissions inheritance from parent folders).
- Amazon S3 only supports permissions on IAM users in AWS. IAM Groups are not supported because groups are not supported as policy principals in AWS. This is an AWS platform limitation.