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
+19-18Lines changed: 19 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -1,34 +1,36 @@
1
1
# Sysdig Secure for Cloud in AWS
2
2
3
-
Terraform module that deploys the **Sysdig Secure for Cloud** stack in **AWS**. It provides unified threat detection, compliance, forensics and analysis.
3
+
Terraform module that deploys the **Sysdig Secure for Cloud** stack in **AWS**.
4
+
<br/>It provides unified threat detection, compliance, forensics and analysis.
4
5
5
-
There are three major component:
6
+
There are three major components:
6
7
7
-
***Cloud Threat Detection**: Tracks abnormal and suspicious activities in your cloud environment based on Falco language.Managed through cloud-connector.
8
-
***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.
9
-
***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.
8
+
***Cloud Threat Detection**: Tracks abnormal and suspicious activities in your cloud environment based on Falco language.<br/>Managed through cloud-connector.<br/><br/>
9
+
***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.<br/><br/>
10
+
***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.<br/><br/>
For other Cloud providers check: [GCP](https://github.com/sysdiglabs/terraform-google-cloudvision), [Azure](https://github.com/sysdiglabs/terraform-azurerm-cloudvision)
15
13
16
14
---
17
15
18
16
## Usage
19
17
20
18
There are several ways to deploy this in you AWS infrastructure:
21
19
22
-
### Single-Account
20
+
### · Single-Account
21
+
Sysdig workload will be deployed in the same account where user's resources will be watched.<br/>
22
+
More info in [`./examples/single-account`](https://github.com/sysdiglabs/terraform-aws-cloudvision/tree/master/examples/single-account)
23
23
24
-
More info in the [`./examples/single-account/README.md`](https://github.com/sysdiglabs/terraform-aws-cloudvision/tree/master/examples/single-account/README.md)
More info in the [`./examples/organizational/README.md`](https://github.com/sysdiglabs/terraform-aws-cloudvision/tree/master/examples/organizational/README.md)
29
+
More info in [`./examples/organizational`](https://github.com/sysdiglabs/terraform-aws-cloudvision/tree/master/examples/organizational)
If no [examples](https://github.com/sysdiglabs/terraform-aws-cloudvision/tree/master/examples) fit your use-case, be free to self-configure your own `cloudvision` module.
34
36
@@ -44,7 +46,7 @@ module "cloudvision_aws" {
44
46
}
45
47
46
48
```
47
-
See main module [`variables.tf`](https://github.com/sysdiglabs/terraform-aws-cloudvision/tree/master/variables.tf) or [inputs summary](#inputs) file for more optional configuration.
49
+
See [inputs summary](#inputs) or main [module `variables.tf`](https://github.com/sysdiglabs/terraform-aws-cloudvision/tree/master/variables.tf) file for more optional configuration.
48
50
49
51
To run this example you need have your [aws master-account profile configured in CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html) and to execute:
50
52
```terraform
@@ -54,9 +56,8 @@ $ terraform apply
54
56
```
55
57
56
58
Notice that:
57
-
- This example will create resources that cost money. Run `terraform destroy` when you don't need them anymore
58
-
- For more detailed configuration inspect both main module and example input variables
59
-
- All created resources will be created within the tags `product:sysdig-cloudvision`, within the resource-group `sysdig-cloudvision`
59
+
* This example will create resources that cost money.<br/>Run `terraform destroy` when you don't need them anymore
60
+
* All created resources will be created within the tags `product:sysdig-cloudvision`, within the resource-group `sysdig-cloudvision`
Copy file name to clipboardExpand all lines: examples/organizational/README.md
+14-16Lines changed: 14 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,22 @@
1
1
# Sysdig Secure for Cloud in AWS: Shared Organizational Trail
2
2
3
-
Deploy Sysdig Secure for Cloud sharing the Trail within an organization. The module will deploy an organizational
4
-
CloudTrail and workload will be run in a member account.
3
+
Deploy Sysdig Secure for Cloud sharing the Trail within an organization.
4
+
* In the **master account**
5
+
* An Organizational Cloutrail will be deployed
6
+
* When an account becomes part of an organization, AWS will create an `OrganizationAccountAccessRole`[for account management](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_access.html), which Sysdig Secure for Cloud will use for member-account provisioning.
7
+
<br/>This Role is hardcoded ATM
8
+
* In the **user-provided member account**:
9
+
* An additional role `SysdigCloudvisionRole` will be created within the master account, to be able to read cloudtrail-s3 bucket events
10
+
* All the Sysdig Secure for Cloud service-related resources will be created
5
11
6
-
When an account becomes part of an organization, AWS will create an `OrganizationAccountAccessRole`[for account management](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_access.html), which cloudvision module will use for member-account provisioning
7
-
8
-
In the member account:
9
-
* An additional role `SysdigCloudvisionRole` will be created within the master account, to be able to read s3 bucket events
10
-
* All the cloudvision service-related resources will be created
1. Have an existing AWS account as the organization master account
19
-
* Organizational cloudTrail service must be enabled
19
+
* Organizational CloudTrail service must be enabled
20
20
1. AWS profile credentials configuration of the `master` account of the organization
21
21
* This account credentials must be [able to manage cloudtrail creation](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/creating-trail-organization.html)
22
22
> You must be logged in with the management account for the organization to create an organization trail. You must also have sufficient permissions for the IAM user or role in the management account to successfully create an organization trail.
See main module [`variables.tf`](https://github.com/sysdiglabs/terraform-aws-cloudvision/blob/master/examples/organizational/variables.tf) or [inputs summary](#inputs) file for more optional configuration.
45
+
See [inputs summary](#inputs) or module [`variables.tf`](https://github.com/sysdiglabs/terraform-aws-cloudvision/blob/master/examples/organizational/variables.tf) file for more optional configuration.
46
46
47
47
To run this example you need have your [aws master-account profile configured in CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html) and to execute:
48
48
```terraform
@@ -51,11 +51,9 @@ $ terraform plan
51
51
$ terraform apply
52
52
```
53
53
54
-
Note that:
55
-
- This example will create resources that cost money. Run `terraform destroy` when you don't need them anymore
56
-
- For more detailed configuration inspect both main module and example input variables
57
-
- All created resources will be created within the tags `product:sysdig-cloudvision`, within the resource-group `sysdig-cloudvision`
58
-
54
+
Notice that:
55
+
* This example will create resources that cost money.<br/>Run `terraform destroy` when you don't need them anymore
56
+
* All created resources will be created within the tags `product:sysdig-cloudvision`, within the resource-group `sysdig-cloudvision`
See main module [`variables.tf`](https://github.com/sysdiglabs/terraform-aws-cloudvision/blob/master/examples/single-account/variables.tf) or [inputs summary](#inputs) file for more optional configuration.
30
+
See [inputs summary](#inputs) or module module [`variables.tf`](https://github.com/sysdiglabs/terraform-aws-cloudvision/blob/master/examples/single-account/variables.tf) file for more optional configuration.
31
31
32
32
To run this example you need have your [aws master-account profile configured in CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html) and to execute:
33
33
```terraform
@@ -36,11 +36,9 @@ $ terraform plan
36
36
$ terraform apply
37
37
```
38
38
39
-
Note that:
40
-
- This example will create resources that cost money. Run `terraform destroy` when you don't need them anymore
41
-
- For more detailed configuration inspect both main module and example input variables
42
-
- All created resources will be created within the tags `product:sysdig-cloudvision`, within the resource-group `sysdig-cloudvision`
43
-
39
+
Notice that:
40
+
* This example will create resources that cost money.<br/>Run `terraform destroy` when you don't need them anymore
41
+
* All created resources will be created within the tags `product:sysdig-cloudvision`, within the resource-group `sysdig-cloudvision`
0 commit comments