Implemented ConfigureBucketNotifications class

[akhil-sumologic]

ConfigureBucketNotifications ?

For each unique bucket in the Sources list:

1. SNS Topic — named sumo-s3-notif-{stack_suffix}-{bucket_hash}. One per unique bucket, shared across all sources pointing to that bucket.
2. SNS Topic Policy — allows s3.amazonaws.com to call sns:Publish on that topic, scoped to the specific bucket ARN via ArnLike.
3. S3 Bucket Notification — adds a TopicConfiguration on the existing bucket pointing to the SNS topic for s3:ObjectCreated:Put events.
4. SNS HTTPS Subscriptions — one per Sumo endpoint sharing that bucket. If ALB and ELB both point to the same bucket, the single topic gets two
   subscriptions — one to the ALB Sumo source endpoint, one to the ELB Sumo source endpoint. Both get every S3 event.

[Copilot]

Pull request overview

Adds a new CloudFormation custom resource implementation (Custom::ConfigureBucketNotifications) to manage S3 bucket event notifications and SNS topics/subscriptions for multiple “sources”, grouping by bucket so a single SNS topic is shared per bucket.

Changes:

• Introduces ConfigureBucketNotifications resource to create/update/delete SNS topics + topic policies per bucket.
• Configures S3 bucket notification TopicConfigurations for s3:ObjectCreated:Put events.
• Creates HTTPS SNS subscriptions per bucket for each configured Sumo endpoint and performs cleanup on update/delete.

Suppressed comments (1)

sumologic-app-utils/src/awsresource.py:1547

• _cleanup has the same issue as _configure: it indexes src['SumoEndpoint'] without checking it exists and can duplicate endpoints while grouping. This can raise KeyError during delete/update flows and makes the grouping inconsistent with _configure.

 active = [s for s in sources if s.get('BucketName')]
buckets = {}
for src in active:
buckets.setdefault(src['BucketName'], []).append(src['SumoEndpoint'])

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[npande]

LGTM