Skip to content

Commit 122a802

Browse files
author
iru
authored
docs: clarify use-case
1 parent 129ceb5 commit 122a802

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

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

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,15 @@ With EKS as workload-type.
77
<br/>This is terraform-based guidelines, but can also check [Manual Organizational Setup - Three-Way Cross-Account ](./manual-org-three-way.md)
88

99
- **User Infrastructure Setup**:
10-
1. Management Account
11-
- Organizational Cloudtrail with no SNS activation
10+
11+
This is the scenario we're going to recreate
12+
13+
1. Management Account / Accounts
14+
- Eithere there is an Organizational Cloudtrail reporting to the log archive account
15+
- Or several accounts reporting to the same log archive account
1216
2. Log Archive Account
1317
- Cloudtrail-S3 bucket, with event notification to an SNS > SQS
14-
3. Member Account
18+
3. Workload/Security Member Account
1519
- Sysdig Secure for cloud deployment
1620
- Existing K8S Cluster
1721
- permission setup rely on an `accessKey/secretAccessKey` parameters of the workload, but can setup the

0 commit comments

Comments
 (0)