eDiscovery and Preservation for Amazon S3
Amazon S3 is a cloud storage service from Amazon Web Services. Used by some of the biggest brands, Amazon S3 lets companies store data in S3 from multiple services at a massive scale.
Onna is the most robust and defensible eDiscovery tool to collect and preserve data from Amazon S3 buckets. Onna connects directly with S3’s API and is able to connect to a specific bucket to collect all files found, as well as relevant metadata.
Using Onna with Amazon S3
Collect, process, preserve and search across your Amazon S3 data in real-time.
Amazon S3 is object storage, which is meant to store and retrieve any amount of data in its native format from anywhere, like web sites, mobile and corporate apps, and data from IoT sensors or devices.
Onna’s Amazon S3 integration offers unparalleled search and e-discovery features across S3 buckets. Additionally, Onna’s S3 integration can work as a bridge to applications that Onna does not have a built-in integration. Users can setup an indirect integration through an S3 bucket.
All collected data, including images, audio and video files, is processed, indexed, and OCR’d instantaneously, rendering a fully searchable environment of your Amazon S3 data. Relevant data can be exported and uploaded to any review platform for a seamless experience.
Main Features
API Based Collections
By connecting with Amazon S3’s API, Onna collects all available data, metadata, and historical information stored in the S3 bucket.
Bridge to Other Applications
Our S3 integration can also be leveraged as a bridge to other applications Onna does not directly support, so you can extract data from any application through an S3 bucket.
eDiscovery Exports
Export relevant Amazon S3 data in a custom load file ready to be uploaded onto any review platform for further assessment. Exports include the natives and metadata.
How to Collect from Amazon S3 with Onna
Amazon S3 Integration Features
To create a bucket in Amazon S3, you must have access to the Amazon Management Console.
To create the integration in Onna, you will need:
- Bucket name
- Access Key ID
- Secret Access Key
- AWS region
For security purposes, we recommend working with your AWS admin and creating a role with access to specific buckets.
What is collected?
Onna’s S3 integration can collect all objects from a specific bucket. You can use an existing bucket from within the organization’s S3 or create a new one specifically for Onna.
All files available through the S3 API and linked to the specific bucket are synced, including, but not limited to:
- Files stored in the bucket from other sources
Historical information and related metadata, including:
- File Title
- File creation
- File last modified
- Extension
- Size
- MD5 hash
- Creators
- File URL in source
- S3 Bucket name
What are your sync modes?
We currently support three syncing modes – one-time, archive, and auto.
- One-time is a one-way sync that collects information only once. You can use our date range picker to sync tickets from a particular time range
- Auto-sync means that Onna will perform a full sync first and will keep the data source and Onna in mirrored sync. Any deletions from the data source will be deleted in Onna, as well.
Some of our Customers
Join these cutting-edge companies using Onna to enhance their eDiscovery and knowledge management strategies
Frequently Asked Questions
How is Onna deployed?
How is data from S3 rendered in Onna?
Data from S3 buckets is rendered in its native format.
Does Onna provide any audit logs?
Yes, Onna provides audit logs for all collections and processing activities across all its supported integrations.
How does Onna work?
What information do I need to connect S3 with Onna?
You will need the following information:
- Access ID: This would be provided by the AWS admin for the specific role.
- Access secret: This would be provided by the AWS admin for the specific role.
- Bucket name: You can add multiple buckets. The names must match the ones found in S3.
- Region: This region must match the region the S3 bucket is stored in.