Skip to content

Commit 2bc40c5

Browse files
authored
Merge pull request #4719 from segmentio/aws-s3-fix
Update AWS S3 Language
2 parents 9f444d9 + b27a672 commit 2bc40c5

File tree

1 file changed

+6
-7
lines changed
  • src/connections/storage/catalog/aws-s3

1 file changed

+6
-7
lines changed

src/connections/storage/catalog/aws-s3/index.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,17 +15,16 @@ Functionally, the two destinations (Amazon S3 and AWS S3 with IAM Role Support)
1515

1616
The AWS S3 destination puts the raw logs of the data Segment receives into your S3 bucket, encrypted, no matter what region the bucket is in.
1717

18-
> info ""
19-
> Segment copies data into your bucket every hour around the :40 minute mark. You may see multiple files over a period of time depending on the amount of data Segment copies.
20-
21-
Keep in mind that AWS S3 works differently than most other destinations. Using a destinations selector like the [integrations object](/docs/connections/spec/common/#integrations) does not affect events with AWS S3.
18+
AWS S3 works differently than most destinations. Using a destinations selector like the [integrations object](/docs/connections/spec/common/#integrations) does not affect events with AWS S3.
2219

23-
The diagram below illustrates how the S3 destination works.
20+
The Segment Tracking API processes data from your sources and collects the Events in batches. Segment then uploads the batches to a secure Segment S3 bucket, from which they're securely copied to your own S3 bucket in small bursts. Individual files won't exceed 100 MB in size.
2421

25-
The Segment Tracking API processes data from your sources, and collects the Events in batches. When these batches reach a 100 MB, or once per hour, a Segment initiates a process which uploads them to a secure Segment S3 bucket, from which they are securely copied to your own S3 bucket.
22+
{% comment %}
2623

2724
![Diagram showing how data is transferred from Segment Tracking API to a customer's AWS S3 bucket.](images/s3processdiagram.png)
2825

26+
{% endcomment %}
27+
2928
## Create a new destination
3029

3130
Complete either [Create an IAM role in the AWS console](#create-an-iam-role-in-the-aws-console), [Create an IAM role using the AWS CLI](#create-an-iam-role-using-the-aws-cli), or [Create IAM roles using Terraform](#create-iam-roles-using-terraform) to set up the AWS S3 Destination with IAM Role Support.
@@ -298,7 +297,7 @@ resource "aws_iam_role_policy_attachment" "segment_aws_s3_role_kms_policy_attach
298297

299298
To finish configuration, enable the AWS S3 Destination with IAM Role Support destination in your workspace.
300299

301-
1. Add the **AWS S3** destination from the Storage Destinations tab of the catalog. This document is about the **AWS S3** destination. For information about the **Amazon S3** destination, which does not include IAM Role support, see the documentation [here](/docs/connections/storage/catalog/amazon-s3/).
300+
1. Add the **AWS S3** destination from the Storage Destinations tab of the catalog. This document is about the **AWS S3** destination. For information about the **Amazon S3** destination, which does not include IAM Role support, see the [Amazon S3 documentation](/docs/connections/storage/catalog/amazon-s3/).
302301
![AWS S3](images/aws-s3-tile.png)
303302
2. Select the data source you'll connect to the destination.
304303
3. Provide a unique name for the destination.

0 commit comments

Comments
 (0)