Skip to content

Commit 9a0209d

Browse files
author
iru
committed
docs: refresh/clarify org-three-way
1 parent d9a93a5 commit 9a0209d

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

use-cases/org-three-way-ecs.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,9 @@ This is the scenario we're going to recreate
1919
3. Workload/Security Member Account
2020
- Sysdig Secure for cloud deployment
2121
- Optionally, we can re-use an existing VPC/subnet network setup.
22+
- 2 and 3 account points may be same account, we will cover both options.
2223

23-
**Sysdig Secure For Cloud [Features](https://docs.sysdig.com/en/docs/installation/sysdig-secure-for-cloud/)** covered
24+
This use-case cover following **[Sysdig Secure For CloudFeatures](https://docs.sysdig.com/en/docs/sysdig-secure/sysdig-secure-for-cloud/#features)**
2425
- Threat-Detection
2526
- Posture; Compliance + Identity Access Management
2627
- :warning: Cloud image scanning is not available for this use-case
@@ -105,7 +106,7 @@ This accountID will be required in the `SYSDIG_SECURE_FOR_CLOUD_MEMBER_ACCOUNT_I
105106

106107
#### 3.2 (Optional) S3 and Sysdig Workload are in different accounts
107108

108-
If `SYSDIG_SECURE_FOR_CLOUD_MEMBER_ACCOUNT_ID` is differnt to the account where the S3 is located, we need to allow
109+
If `SYSDIG_SECURE_FOR_CLOUD_MEMBER_ACCOUNT_ID` is different to the account where the S3 is located, we need to allow
109110
cross-account access through a role.
110111

111112
Permission setup for SysdigSecureForCloud-S3AccessRole
@@ -144,17 +145,17 @@ be used.
144145
#### 4. Launch Terraform Manifest
145146

146147
Let's create the Terraform manifest module parametrization, based on `examples/organizational`.
147-
Get detailed explanation of each variable bellow.
148+
<br/>Get detailed explanation of each variable bellow.
148149

149150
```terraform
150151
151152
152-
# --------------------------------------------------
153-
# Optional. for Cloudtrail S3-SNS-SQS creation
154-
# --------------------------------------------------
153+
# ----------------------------------------------------------
154+
# Optional. for Cloudtrail S3-SNS-SQS event-forwarder creation
155+
# ----------------------------------------------------------
155156
156157
# provider for S3 account
157-
# this is a sample authentication, can adapt it as long as alias is maintaned
158+
# this is a sample authentication, can adapt it as long as alias is maintained
158159
provider "aws"{
159160
alias = "s3"
160161
region = "<AWS_REGION>"

0 commit comments

Comments
 (0)