Skip to content

Commit 3ce1b90

Browse files
author
iru
authored
doc: clarify cloudtrail-s3-sns-sqs
1 parent f1e6c53 commit 3ce1b90

File tree

1 file changed

+11
-2
lines changed
  • modules/infrastructure/cloudtrail_s3-sns-sqs

1 file changed

+11
-2
lines changed

modules/infrastructure/cloudtrail_s3-sns-sqs/README.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,16 @@
1-
# Cloudtrail_S3 event notification handle through SNS-SQS
1+
# Cloudtrail S3 event notification handle through SNS-SQS
22

3-
Provision a cloud-connector cloudtrail input, based on an S3-SNS-SQS event-notification.
3+
In order cloud-connector module to be able to ingest cloudtrail-s3 events (insted of cloudtdrail-sns ones), it needs an sqs queue URL from where to get the events.
44

5+
This way of ingesting, is the [`aws-cloudtrail-s3-sns-sqs` ingestor](https://charts.sysdig.com/charts/cloud-connector/#ingestors)
6+
It requires:
7+
- `queueURL`: the url of the sqs queue (see point 2)
8+
- `assumeRole`: optional; the role need to be able to fetch the events to the S3 bucket (as the event payload is not coming in the sqs message)
9+
10+
This module helps with the creation of the SQS queue from which to pull the cloudtrail events, leveraging the S3 "bucket event notification" system.
11+
12+
Module gets the cloudtrail-s3 bucket name as input and provides the sqs topic url as output.
13+
514
# How it works
615

716
- This module's output will be visible in the `S3` console, after entering a bucket, in it's `Properties`, `Event notifications` section.

0 commit comments

Comments
 (0)