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.

Sign up for GitHub

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 README.md #215

Merged
merged 1 commit into from
Feb 19, 2025
Merged

Update README.md #215

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 4 additions & 2 deletions modules/coralogix-aws-shipper/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,8 +40,10 @@ If you're deploying multiple integrations through the same S3 bucket, you'll nee
If you already have a Lambda function with an S3 trigger set up, this Terraform deployment will remove the trigger. This applies to the following integration types within
the same S3 bucket: S3, CloudTrail, VpcFlow, S3Csv, and CloudFront.
To prevent this issue, you can explore alternative deployment methods:
- Deploy the integration using CF Quick Create or SAR, as explained in [this document](https://coralogix.com/docs/coralogix-aws-shipper/).
- Migrate your existing integrations to Terraform and use the `integration_info` variable.

- Deploy the integration using CF Quick Create or SAR, as explained in [this document](https://coralogix.com/docs/coralogix-aws-shipper/).

- Migrate your existing integrations to Terraform and use the `integration_info` variable.

| Name | Description | Type | Default | Required |
|------|-------------|------|---------|:--------:|
Expand Down