Skip to content

Commit 4cf005e

Browse files
Update README.md
1 parent 00ec9ba commit 4cf005e

File tree

1 file changed

+15
-8
lines changed

1 file changed

+15
-8
lines changed

README.md

Lines changed: 15 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,34 +5,34 @@ Terraform module that deploys the **Sysdig Secure for Cloud** stack in **AWS**.
55

66
There are three major components:
77

8-
* **Cloud Threat Detection**: Tracks abnormal and suspicious activities in your cloud environment based on Falco language.<br/>Managed through [cloud-connector module](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/modules/services/cloud-connector).<br/><br/>
8+
* **Cloud Threat Detection**: Tracks abnormal and suspicious activities in your cloud environment based on Falco language. Managed through [cloud-connector module](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/modules/services/cloud-connector).<br/>
99

10+
* **CSPM/Compliance**: 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](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/modules/services/cloud-bench).<br/>
1011

11-
* **CSPM/Compliance**: It evaluates periodically your cloud configuration, using Cloud Custodian, against some benchmarks and returns the results and remediation you need to fix.<br/>Managed through [cloud-bench module](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/modules/services/cloud-bench).<br/><br/>
12-
13-
* **Cloud Scanning**: Automatically scans all container images pushed to the registry or as soon a new task which involves a container is spawned in your account.<br/>Managed through [cloud-scanning module](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/modules/services/cloud-scanning).<br/><br/>
12+
* **Cloud Scanning**: Automatically scans all container images pushed to the registry or as soon a new task which involves a container is spawned in your account.Managed through [cloud-scanning module](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/modules/services/cloud-scanning).<br/>
1413

1514
For other Cloud providers check: [GCP](https://github.com/sysdiglabs/terraform-google-cloudvision), [Azure](https://github.com/sysdiglabs/terraform-azurerm-cloudvision)
1615

16+
<br/>
1717

1818
## Usage
1919

2020
There are several ways to deploy this in you AWS infrastructure:
2121

22-
### · Single-Account
22+
- ### Single-Account
2323
Sysdig workload will be deployed in the same account where user's resources will be watched.<br/>
2424
More info in [`./examples/single-account`](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/examples/single-account)
2525

2626
![single-account diagram](https://raw.githubusercontent.com/sysdiglabs/terraform-aws-secure-for-cloud/b95bf11fe513bda3c037144803d982a6e4225ce9/examples/single-account/diagram-single.png)
2727

28-
### · Organizational
28+
- ### Organizational
2929

3030
Using an organizational configuration Cloudtrail.
3131
More info in [`./examples/organizational`](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/examples/organizational)
3232

3333
![organizational diagram](https://raw.githubusercontent.com/sysdiglabs/terraform-aws-secure-for-cloud/b95bf11fe513bda3c037144803d982a6e4225ce9/examples/organizational/diagram-org.png)
3434

35-
### · Self-Baked
35+
- ### Self-Baked
3636

3737
If no [examples](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/examples) fit your use-case, be free to call desired modules directly.
3838

@@ -67,6 +67,8 @@ Notice that:
6767
* All created resources will be created within the tags `product:sysdig-secure-for-cloud`, within the resource-group `sysdig-secure-for-cloud`
6868

6969

70+
71+
<br/><br/>
7072
## Troubleshooting
7173

7274
- Q: How to **validate secure-for-cloud cloud-connector (thread-detection) provisioning** is working as expected?<br/>
@@ -91,7 +93,6 @@ Notice that:
9193
```
9294
$ aws ecs update-service --force-new-deployment --cluster sysdig-secure-for-cloud-ecscluster --service sysdig-secure-for-cloud-cloudconnector --profile <AWS_PROFILE>
9395
```
94-
9596
For the AWS_PROFILE, set your `~/.aws/config` to impersonate
9697
```
9798
[profile secure-for-cloud]
@@ -100,6 +101,12 @@ Notice that:
100101
source_profile=<AWS_MASTER_ACCOUNT_PROFILE>
101102
```
102103
104+
- Q: How to test **cloud-scanner** image-scanning?<br/>
105+
- A: Upload any image to the ECR repository of AWS. You should see a log in the ECS-cloud-scanner task + CodeBuild project being launched successfully
106+
<br/>
107+
108+
109+
<br/><br/>
103110
## Authors
104111
105112
Module is maintained and supported by [Sysdig](https://sysdig.com).

0 commit comments

Comments
 (0)