You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-s3/index.md
+60-4Lines changed: 60 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,13 +38,69 @@ Ensure you have the following in place before configuring the AWS S3 (Actions) d
38
38
39
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
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
41
+
- 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.
45
42
46
43
47
44
### Create an IAM role in the AWS console
45
+
To setup the IAM role to properly authorize Segment with the AWS S3 (Actions) destination, follow the steps below.
46
+
47
+
1. Login to your AWS account
48
+
2. Create a new or use an existing bucket with `PutObject`, `GetObject`, `ListObject` access to the S3 bucket.
49
+
3. Go to IAM > Roles > Create Role
50
+
4. Provide the following policy permissions for the IAM that was just created:
51
+
```json
52
+
{
53
+
"Version": "2012-10-17",
54
+
"Statement": [
55
+
{
56
+
"Sid": "PutObjectsInBucket",
57
+
"Effect": "Allow",
58
+
"Action": [
59
+
"s3:PutObject",
60
+
"s3:PutObjectAcl"
61
+
],
62
+
"Resource": "arn:aws:s3:::<YOUR_BUCKET_NAME>/*"
63
+
}
64
+
]
65
+
}
66
+
```
67
+
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, please refer to the AWS documentation to create a user)
0 commit comments