Merge pull request #7242 from mayur-pitale/segment-actions-s3

Initial Commit

Author: stayseesong

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

@@ -0,0 +1,100 @@
+---
+title: AWS S3 (Actions) Destination
+hide-boilerplate: true
+hide-dossier: false
+id: 66eaa166f650644f04389e2c
+private: true
+beta: true
+# versions:
+#   - name: AWS S3 (Classic)
+#     link: /docs/connections/destinations/catalog/aws-s3/
+---
+{% include content/plan-grid.md name="actions" %}
+
+The AWS S3 (Actions) destination allows you to store event data as objects in a secure, scalable cloud storage solution. Each event is written to your S3 bucket, organized into a customizable folder structure such as by event type or timestamp. This makes it easy to manage, archive, and analyze data using downstream tools or AWS services.
+
+
+## Benefits of AWS S3 (Actions) vs AWS S3 Classic
+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 (in JSON format) for downstream analytics or integrations.
+
+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:
+
+* **Standardized Data Formatting**. AWS S3 (Actions) lets you define consistent output formats for your data, either CSV or TXT file formats, in a folder definition that you choose. The previous AWS S3 Classic Destination only allowed raw JSON payloads stored within a specific folder called `"segment-logs"`. 
+
+* **Configurable Data Translation**.  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 by either adding in custom columns or using the default ones.
+
+* **Enhanced Delivery Controls**. The destination provides advanced options for batch size controls and file naming conventions. These controls can help optimize efficiency and simplify data retrieval workflows.
+
+## Getting started
+Setting up the AWS S3 (Actions) destination is a straightforward process designed to help you configure and deploy standardized event data to your Amazon S3 bucket. Follow these steps to get started:
+
+### Prerequisites
+Ensure you have the following in place before configuring the AWS S3 (Actions) destination:
+
+- Amazon S3 Bucket: Create a bucket in your AWS account or use an existing one where you want to store the event data.
+- AWS IAM Permissions: Verify that you have appropriate IAM roles with write access to the S3 bucket and permissions for the Segment connection.
+- IAM Access IDs: Prepare your AWS IAM ARN ID and IAM External ID. These will be needed to authenticate and authorize Segment with your S3 bucket.
+
+
+### Step 1: Create an IAM role in the AWS console
+To set up the IAM role to properly authorize Segment with the AWS S3 (Actions) destination:
+
+1. Log in to your AWS account. 
+2. Create a new or use an existing bucket with `PutObject`, `GetObject`, `ListObject` access to the S3 bucket.
+3. Navigate to **IAM > Roles > Create Role**.
+4. Provide the following policy permissions for the IAM that was just created: 
+```json
+{
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Sid": "PutObjectsInBucket",
+            "Effect": "Allow",
+            "Action": [
+                "s3:PutObject",
+                "s3:PutObjectAcl"
+            ],
+            "Resource": "arn:aws:s3:::<YOUR_BUCKET_NAME>/*"
+        }
+    ]
+}
+```
+5. Click on the Trust Relationships tab and edit the trust policy to allow the IAM user to assume the role. If a user is not already created, refer to the AWS documentation to create a user.
+```json
+{
+   "Version": "2012-10-17",
+   "Statement": [
+     {
+       "Sid": "",
+       "Effect": "Allow",
+       "Principal": {
+         "AWS":                      
+         	"arn:aws:iam::595280932656:role/customer-s3-prod-action-destination-access"
+       },
+       "Action": "sts:AssumeRole",
+       "Condition": {
+         "StringEquals": {
+           "sts:ExternalId": "<YOUR_EXTERNAL_ID>"
+         }
+       }
+     }
+   ]
+ }
+```
+## Step 2: Add the AWS S3 (Actions) Destination in Segment
+To finish the configuration, enable the AWS S3 (Actions) Destination in your workspace. 
+
+1. Add the **AWS S3 (Actions)** destination from the Destinations tab of the catalog.
+2. Select the data source you want to connect to the destination.
+3. Provide a unique name for the destination.
+4. Complete the destination settings:
+   * Enter the name of the region in which the bucket you created above resides.
+   * Enter the name of the bucket you created above. Be sure to enter the bucket's **name** and not URI.
+   * Enter the ARN of the IAM role you created above. The ARN should follow the format `arn:aws:iam::ACCOUNT_ID:role/ROLE_NAME.`
+   * Enter the IAM External ID, which is a value set in the Trust Relationship under your AWS IAM Role.
+5. Enable the destination.
+6. Verify the Segment data is stored in the S3 bucket by navigating to the `<your_S3_bucket>/` in the AWS console. 
+
+{% include components/actions-fields.html settings="true"%}
+
+