Skip to content

Commit 6e74d40

Browse files
committed
adding benefits and getting started
1 parent 4ec837f commit 6e74d40

File tree

1 file changed

+31
-0
lines changed
  • src/connections/destinations/catalog/actions-s3

1 file changed

+31
-0
lines changed

src/connections/destinations/catalog/actions-s3/index.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,40 @@ The AWS S3 (Actions) destination allows you to store event data as objects in a
1313

1414

1515
## Benefits of AWS S3 (Actions) vs AWS S3 Classic
16+
The traditional AWS S3 Classic destination enabled the storage of raw logs containing data Segment received, directly into your S3 bucket. While this provided a straightforward data storage solution, users often needed to implement additional processing to standardize or transform these logs for downstream analytics or integrations.
1617

18+
The AWS S3 (Actions) destination enhances this capability by introducing configurable options to format and structure event data prior to storage. This new approach offers several key benefits:
19+
20+
1. Standardized Data Formatting
21+
Instead of raw, unprocessed logs, AWS S3 (Actions) lets you define consistent output formats for your data. This standardization simplifies downstream analysis, ensuring your event payloads adhere to predefined schemas without requiring custom transformation processes after storage.
22+
23+
2. Configurable Data Translation
24+
AWS S3 (Actions) supports translation rules that can map raw event attributes to more meaningful or actionable representations. You can configure these rules to meet specific data schema requirements, reducing the need for post-processing and improving compatibility with other tools and analytics platforms.
25+
26+
3. Enhanced Delivery Controls
27+
The destination provides advanced options for batching, compression, and file naming conventions. These controls help optimize storage efficiency and simplify data retrieval workflows.
28+
29+
4. Improved Data Consistency and Quality
30+
By standardizing event payloads before delivery, AWS S3 (Actions) minimizes inconsistencies and errors often associated with raw data ingestion. This leads to cleaner, more reliable data for downstream systems.
1731

1832

1933
## Getting Started
34+
Setting up the AWS S3 (Actions) destination is a straightforward process designed to help you quickly configure and deploy standardized event data to your Amazon S3 bucket. Follow these steps to get started:
35+
36+
### Prerequisites
37+
Ensure you have the following in place before configuring the AWS S3 (Actions) destination:
38+
39+
- Amazon S3 Bucket: Create a bucket in your AWS account or use an existing one where you want to store the event data.
40+
- AWS IAM Permissions: Verify that you have appropriate IAM roles with write access to the S3 bucket and permissions for the Segment connection.
41+
- Access Keys: Prepare your AWS Access Key ID and Secret Access Key. These will be needed to authenticate Segment with your S3 bucket.
42+
43+
44+
## Create a new destination
45+
46+
47+
### Create an IAM role in the AWS console
48+
49+
50+
### Build Configuration Mappings
2051

2152

0 commit comments

Comments
 (0)