Skip to content

Commit 8b4df13

Browse files
authored
remove duplicate s3 paragraph
This paragraph was repeated: "Also keep in mind that Amazon S3 works in a different way from most of our destinations. Using a destinations selector like the [integrations object](https://segment.com/docs/connections/spec/common/#integrations) will not have any effect on events in the case of Amazon S3.". Removed second instance of it.
1 parent e7b612a commit 8b4df13

File tree

1 file changed

+0
-2
lines changed
  • src/connections/warehouses/catalog/amazon-s3

1 file changed

+0
-2
lines changed

src/connections/warehouses/catalog/amazon-s3/index.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,6 @@ The Amazon S3 destination puts the raw logs of the data we're receiving into you
1010

1111
Keep in mind that Amazon S3 works in a different way from most of our destinations. Using a destinations selector like the [integrations object](https://segment.com/docs/connections/spec/common/#integrations) does not affect events in the case of Amazon S3.
1212

13-
Also keep in mind that Amazon S3 works in a different way from most of our destinations. Using a destinations selector like the [integrations object](https://segment.com/docs/connections/spec/common/#integrations) will not have any effect on events in the case of Amazon S3.
14-
1513
The diagram below illustrates how the S3 destination works.
1614

1715
Data from your sources is processed by the Segment Tracking API, which collects the Events in batches. When the batches reach a 100 MB, or once an hour, a process in the Segment backend uploads them to a secure Segment S3 bucket, from which they can be securely copied to your own S3 bucket.

0 commit comments

Comments
 (0)