doc: fix EKS term for global K8S, as it's supported

Author: iru

README.md

@@ -143,7 +143,7 @@ This would be an overall schema of the **created resources**, for the default se
 
 - Cloudtrail / SNS / S3 / SQS
 - SSM Parameter for Sysdig API Token Storage
-- Sysdig Workload: ECS / AppRunner creation (EKS is pre-required, not created)
+- Sysdig Workload: ECS / AppRunner creation (K8s cluster is pre-required, not created)
   - each compute solution require a role to assume for execution
 - CodeBuild for on-demand image scanning
 - Sysdig role for [Compliance](./modules/services/cloud-bench)
@@ -217,7 +217,7 @@ Image scanning is not activated by default. Ensure you have the [required scanni
   - For ECR image scanning, upload any image to an ECR repository of AWS. Can find CLI instructions within the UI of AWS
   - For ECS running image scanning, deploy any task in your own cluster, or the one that we create to deploy our workload (ex.`amazon/amazon-ecs-sample` image).
 
-It may take some time, but you should see logs detecting the new image in the ECS cloud-connector task 
+It may take some time, but you should see logs detecting the new image in the ECS cloud-connector task
 
 ```
 {"component":"ecs-action","message":"processing detection {\"account\":\"***\",\"region\":\"eu-west-3\",\"taskDefinition\":\"apache:1\"}. source=aws_cloudtrail"}

examples-internal/organizational-k8s-threat-reuse_cloudtrail_s3/README.md

@@ -1,4 +1,4 @@
-# Sysdig Secure for Cloud in AWS<br/>:: Organizational, threat-detection with pre-existing resources (EKS + cloudtrail through S3-SNS-SQS events)
+# Sysdig Secure for Cloud in AWS<br/>:: Organizational, threat-detection with pre-existing resources (K8S + cloudtrail through S3-SNS-SQS events)
 
 
 - Sysdig **Helm** chart will be used to deploy threat-detection

examples/single-account-k8s/README.md

@@ -4,7 +4,7 @@ Deploy Sysdig Secure for Cloud in a provided existing Kubernetes Cluster.
 
 - Sysdig **Helm** [cloud-connector chart](https://charts.sysdig.com/charts/cloud-connector/) will be used to deploy threat-detection and scanning features
   <br/>Because these charts require specific AWS credentials to be passed by parameter, a new user + access key will be created within account. See [`credentials.tf`](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/blob/master/examples/single-account-k8s/credentials.tf)
-- Used architecture is similar to [single-account](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/blob/master/examples/single-account) but changing ECS <---> with an existing EKS
+- Used architecture is similar to [single-account](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/blob/master/examples/single-account) but changing ECS <---> with an existing K8s cluster (EKS or vanilla)
 
 ### Notice
 * All the required resources and workloads will be run under the **same AWS account**. <br/><br/>

examples/single-account-k8s/diagram.png

@@ -59,8 +59,8 @@
             cloudtrail >> Edge(color=color_event, style="dashed") >> sns
 
             with Cluster(""):
-                eks = EKS("EKS\n(pre-existing)")
-                with Cluster("namespace: sfc"):
+                eks = Deployment()
+                with Cluster("K8s Cluster\n(pre-existing)\nnamespace: sfc"):
                     cloud_connector = Deployment("cloud-connector")
 
 

examples/single-account-k8s/diagram.py

@@ -1,4 +1,4 @@
-# AWS Organizational Secure for Cloud Role for EKS
+# AWS Organizational Secure for Cloud Role for K8s
 
 The aim of this module is to manage the organizational **managed account** required role and permissions for threat-detection and image scanning modules to work properly.
 
@@ -13,9 +13,6 @@ The aim of this module is to manage the organizational **managed account** requi
   * Enable this role to assumeRole to member accounts through the `organizational_role_per_account` role,
     in order to be able to fetch images that may be in member-account repositories
 
-* Other permissions
-  * ECS-Task roles (of both modules) to be able to assume this role
-
 
 <!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
 ## Requirements