You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22-3Lines changed: 22 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ Terraform module that deploys the [**Sysdig Secure for Cloud** stack in **AWS**]
5
5
6
6
Provides unified threat-detection, compliance, forensics and analysis through these major components:
7
7
8
-
***[CSPM/Compliance](https://docs.sysdig.com/en/docs/sysdig-secure/benchmarks/)**: It evaluates periodically your cloud configuration, using Cloud Custodian, against some benchmarks and returns the results and remediation you need to fix. Managed through `cloud-bench` module. <br/>
8
+
***[CSPM/Compliance](https://docs.sysdig.com/en/docs/sysdig-secure/posture/compliance-unified-/)**: It evaluates periodically your cloud configuration, using Cloud Custodian, against some benchmarks and returns the results and remediation you need to fix. Managed through `cloud-bench` module. <br/>
9
9
10
10
***[CIEM](https://docs.sysdig.com/en/docs/sysdig-secure/posture/)**: Permissions and Entitlements management. Requires BOTH modules `cloud-connector` and `cloud-bench`. <br/>
11
11
@@ -41,7 +41,12 @@ For other Cloud providers check: [GCP](https://github.com/sysdiglabs/terraform-g
41
41
42
42
## Usage
43
43
44
-
There are several ways to deploy this in you AWS infrastructure:
44
+
- There are several ways to deploy this in you AWS infrastructure, gathered under **[`/examples`](./examples)**
45
+
- Many module,examples and use-cases provide ways to **re-use existing resources (as optionals)** in your infrastructure (cloudtrail, ecs, vpc, k8s cluster,...)
46
+
- Find some real **use-case scenario explanations** under [`/examples-internal/use-cases*`](./examples-internal)
-[Organizational - Existing Cloudtrail withouth SNS, but with S3 configuration, with K8s Cluster and Filtered Cloudtrail Event Account](./examples-internal/use-cases-self-baked/org-s3-k8s-filtered-account.md)
45
50
46
51
### - Single-Account
47
52
@@ -135,9 +140,23 @@ Upload any image to the ECR repository of AWS.
135
140
136
141
## Troubleshooting
137
142
143
+
### Q: Getting error "404 Invalid parameter: TopicArn" when trying to reuse an existing cloudtrail-sns
### Q: Getting error when creating the ECS subnet due to nats not being supported
140
153
```
154
+
155
+
A: In order to subscribe to a SNS Topic, SQS queue must be in the same region
156
+
S: Change `aws provider``region` variable to match same region for all resources
157
+
158
+
### Q: Getting error "400 availabilityZoneId is invalid" when creating the ECS subnet
159
+
```text
141
160
│ Error: error creating subnet: InvalidParameterValue: Value (apne1-az3) for parameter availabilityZoneId is invalid. Subnets can currently only be created in the following availability zones: apne1-az1, apne1-az2, apne1-az4.
142
161
│ status code: 400, request id: 6e32d757-2e61-4220-8106-22ccf814e1fe
0 commit comments