Skip to content

Commit

Permalink
Update _data-prepper/pipelines/configuration/sinks/s3.md
Browse files Browse the repository at this point in the history
Signed-off-by: Melissa Vagi <[email protected]>
  • Loading branch information
vagimeli authored Jun 6, 2024
1 parent d498755 commit e608d5e
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion _data-prepper/pipelines/configuration/sinks/s3.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,9 @@ In order to use the `s3` sink, configure AWS Identity and Access Management (IAM

## Cross-account S3 access<a name="s3_bucket_ownership"></a>

When Data Prepper fetches data from an S3 bucket, it verifies the ownership of the bucket using the [bucket owner condition](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucket-owner-condition.html). By default, the S3 sink does not require `bucket_owners`. If `bucket_owners` is configured and a bucket is not included in one of these mapped configurations, the `default_bucket_owner` defaults to the account id from the `aws.sts_role_arn`.
When Data Prepper fetches data from an S3 bucket, it verifies bucket ownership using [bucket owner condition](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucket-owner-condition.html).

By default, the S3 sink does not require `bucket_owners`. If `bucket_owners` is configured and a bucket is not included in one of these mapped configurations, `default_bucket_owner` defaults to the account id from `aws.sts_role_arn`.

When ingesting data from multiple S3 buckets with different account associations, configure Data Prepper for cross-account S3 access based on the following conditions:

Expand Down

0 comments on commit e608d5e

Please sign in to comment.