Skip to content

Commit aad45ce

Browse files
committed
Changed descriptions
1 parent e1a2f9b commit aad45ce

File tree

1 file changed

+5
-6
lines changed
  • src/connections/destinations/catalog/actions-s3

1 file changed

+5
-6
lines changed

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

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: S3 (Actions) Destination
33
hide-boilerplate: true
44
hide-dossier: false
5-
# id: 5f7dd8e302173ff732db5cc4
5+
id: 66eaa166f650644f04389e2c
66
# versions:
77
# - name: AWS S3 (Classic)
88
# link: /docs/connections/destinations/catalog/aws-s3/
@@ -13,7 +13,7 @@ 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.
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 (in JSON format) for downstream analytics or integrations.
1717

1818
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:
1919

@@ -69,8 +69,7 @@ To setup the IAM role to properly authorize Segment with the AWS S3 (Actions) de
6969
"Sid": "",
7070
"Effect": "Allow",
7171
"Principal": {
72-
"AWS":
73-
"arn:aws:iam::595280932656:role/customer-s3-dev-action-destination-access",
72+
"AWS":
7473
"arn:aws:iam::595280932656:role/customer-s3-prod-action-destination-access"
7574
},
7675
"Action": "sts:AssumeRole",
@@ -99,9 +98,9 @@ To finish configuration, enable the AWS S3 (Actions) Destination in your workspa
9998
6. Verify Segment data is stored in the S3 bucket by navigating to the `<your_S3_bucket>/` in the AWS console.
10099

101100
### Actions
102-
Segment’s introduced the following v2 Actions to the AWS S3(Actions) destination:
101+
Build your own Mappings. The following action is supported:
103102
- [Sync to S3](#sync-to-s3)
104103

105-
{% include components/actions-fields.html %}
104+
{% include components/actions-fields.html settings="true"%}
106105

107106

0 commit comments

Comments
 (0)