Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update CrossAccount.md #3752

Merged
merged 8 commits into from
Dec 12, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions docs/CrossAccount.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,31 @@ following to buckets in your *DataAccount*.
}
```

## Notifications
sir-sigurd marked this conversation as resolved.
Show resolved Hide resolved

In order for *ControlAccount* to use an existing and
[correctly configured SNS topic](EventBridge.md#the-workarounds)
for a single bucket in *DataAccount*, add a statement similar to the following
QuiltSimon marked this conversation as resolved.
Show resolved Hide resolved
to the topic resource policy:

```json
{
"Sid": "AWSConfigSNSPolicy",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::CONTROL-ACCOUNT:root"
},
"Action": [
"sns:GetTopicAttributes",
"sns:Subscribe"
],
"Resource": "SNS_TOPIC_ARN"
}
```

You can now set the SNS topic in the [Catalog Admin Panel](catalog/Admin.md) in bucket
sir-sigurd marked this conversation as resolved.
Show resolved Hide resolved
properties under "Indexing and notifications".

## CloudTrail

For security, auditing, and user-facing analytics, it is recommended that all
Expand Down
Loading