.svg)
AWS S3 Connector for eDiscovery & Data Collection
Collect files, documents, and metadata stored in Amazon S3 buckets for eDiscovery, compliance, and investigations without complicated workarounds. The Onna + AWS S3 Connector lets you access data across your organization's cloud storage on a defensible, unified platform.
Why Connect Amazon S3 to Your eDiscovery Collections Platform
Amazon S3 is where organizations store vast amounts of business-critical data, from documents, exports from other applications, archived records, and more. When legal or compliance needs arise, that data has to be accessible, complete, and defensible.
Without the right tools, collecting from AWS is harder than it should be because:
Data is stored across multiple buckets from different sources and teams
Files may include exports from applications Onna does not directly integrate with
Historical data and metadata must be preserved alongside file content
Bucket access and permissions require careful coordination with IT and AWS admins
The Onna + AWS S3 Connector enables organizations to collect this data in a defensible and scalable way. Through S3's API, the connector syncs files and metadata from specified buckets while preserving historical information and chain of custody.
AWS S3 Connector Capabilities
The Onna + AWS S3 Connector is designed for enterprise-scale data collection from cloud storage environments.
Key capabilities include:
Direct connection to Amazon S3 via API
Support for one-time and auto-sync modes
Multi-bucket collection from a single sync configuration
Audit logs for all collection activity
Historical data collection from a specified start date
Metadata preservation alongside file content
Bridge integration for applications without a native Onna connector
These capabilities allow organizations to perform targeted collections from S3 or use S3 as a bridge to data sources that Onna does not directly integrate with.
What Data Can Be Collected from Amazon S3
The connector captures both file content and metadata from Amazon S3 buckets including:
Files & Content
All file types stored in connected S3 buckets
Files ingested from third-party applications via S3
Historical files from a specified date range
Data stored in multiple buckets
These collections preserve the structure and context of files and metadata so investigators can reconstruct data provenance accurately.
AWS S3 Metadata Collected
Alongside file content, the connector captures key metadata fields including:
Metadata
File title
File creation date
File last modified date
File extension
File size
MD5 hash
Creator information
File URL in source
S3 bucket name
This metadata allows teams to verify file integrity, establish data provenance, and identify the origin of files collected from S3 buckets.
How AWS S3 Data Collection Works
The connector simplifies S3 data collection through a structured workflow.
Add Amazon S3 as a data source
Navigate to your workspace and add Amazon S3 as a source.
Authenticate the connection
Enter the credentials provided by your AWS admin, including Access Key ID, Secret Access Key, bucket name(s), and AWS region.
Configure the collection
Define collection settings including:
- Collection name
- Sync mode (one-time or auto-sync)
- Sync start date (required)
Select buckets
Specify which S3 buckets to collect from. Multiple bucket names can be entered, one per line. Bucket names must match exactly as they appear in S3.
Start sync
Once configuration is complete, the S3 collection begins and data appears within your Onna workspace.
AWS S3 Data Collection Options
The Onna + AWS S3 Connector supports flexible sync modes depending on investigation needs.
One-Time Sync
A targeted collection used for litigation or investigations with a defined date range.
Auto-Sync
Automatically collects new files and data as they are added to connected S3 buckets.
Common AWS S3 eDiscovery Use Cases
Litigation Response
Collect files stored in S3 relevant to legal matters quickly and defensibly.
Bridge Collection for Unsupported Applications
Use S3 as an intermediary to collect data from applications that do not have a native Onna connector.
Regulatory Compliance
Archive files and records stored in S3 to meet regulatory data retention requirements.
Internal Investigations
Identify files, documents, and metadata stored in S3 that are relevant to incidents or policy violations
%201.webp){kind=logo}
%201.webp)
Onna + AWS S3 Connector FAQs
Yes. You can add multiple bucket names to a single sync configuration, one per line. Each bucket name must match exactly as it appears in Amazon S3.
Yes. Because customers can upload any type of data to an S3 bucket, the connector is designed to collect all files accessible through the S3 API within the specified bucket(s). Onna processes 1,000+ file types at ingestion.
You will need an Access Key ID and Secret Access Key with the appropriate S3 permissions. Onna recommends working with your AWS admin to create a scoped IAM role and generate the necessary credentials.
A sync start date is required for all S3 collections. This defines the earliest point from which files will be collected based on their metadata.
Yes. The Onna S3 connector is designed to serve as a bridge to applications that Onna does not directly integrate with. If data from another source is being exported or stored in an S3 bucket, Onna can collect it from there.
Yes. Onna maintains a comprehensive audit log of all preservations, collections, and user actions. Every collection has a documented chain of custody.
Immediately. Onna indexes data in real time at ingestion, so collected S3 data is searchable as soon as it's pulled in.
Start Collecting AWS S3 Data for eDiscovery
Connect Amazon S3 in minutes and begin collecting files, documents, and cloud storage data from across your organization's buckets.