diff --git a/docs/tutorials/kubernetes/in-cluster.md b/docs/tutorials/kubernetes/in-cluster.md
index ae733db84a..9b16b21f09 100644
--- a/docs/tutorials/kubernetes/in-cluster.md
+++ b/docs/tutorials/kubernetes/in-cluster.md
@@ -2,6 +2,7 @@
For in-cluster execution, you can use the supplied yaml files inside `/kubernetes`:
+* [prowler-sa.yaml](https://github.com/prowler-cloud/prowler/blob/master/kubernetes/prowler-sa.yaml)
* [job.yaml](https://github.com/prowler-cloud/prowler/blob/master/kubernetes/job.yaml)
* [prowler-role.yaml](https://github.com/prowler-cloud/prowler/blob/master/kubernetes/prowler-role.yaml)
* [prowler-rolebinding.yaml](https://github.com/prowler-cloud/prowler/blob/master/kubernetes/prowler-rolebinding.yaml)
diff --git a/docs/tutorials/prowler-app.md b/docs/tutorials/prowler-app.md
index d4d3d2f890..cd94504579 100644
--- a/docs/tutorials/prowler-app.md
+++ b/docs/tutorials/prowler-app.md
@@ -100,9 +100,11 @@ By default, the `kubeconfig` file is located at `~/.kube/config`.
???+ note
- If you are adding an **Amazon EKS** cluster, follow these additional steps to ensure proper authentication:
+ If you are adding an **EKS**, **GKE**, **AKS** or external cluster, follow these additional steps to ensure proper authentication:
- 1. Apply the necessary Kubernetes resources to your EKS cluster (you can find the files in the [`kubernetes` directory of the Prowler repository](https://github.com/prowler-cloud/prowler/tree/master/kubernetes)):
+ ** Make sure your cluster allow traffic from the Prowler Cloud IP address `52.48.254.174/32` **
+
+ 1. Apply the necessary Kubernetes resources to your EKS, GKE, AKS or external cluster (you can find the files in the [`kubernetes` directory of the Prowler repository](https://github.com/prowler-cloud/prowler/tree/master/kubernetes)):
```console
kubectl apply -f kubernetes/prowler-sa.yaml
kubectl apply -f kubernetes/prowler-role.yaml
@@ -119,11 +121,11 @@ By default, the `kubeconfig` file is located at `~/.kube/config`.
3. Update your `kubeconfig` to use the ServiceAccount token:
```console
kubectl config set-credentials prowler-sa --token=
- kubectl config set-context --user=prowler-sa
+ kubectl config set-context --user=prowler-sa
```
- Replace with the generated token and with your EKS cluster ARN.
+ Replace with the generated token and with your KubeConfig Context Name of your EKS, GKE or AKS cluster.
- 4. Now you can add the modified `kubeconfig` as the credentials of the AWS EKS Cluster in Prowler Cloud. Then simply test the connection.
+ 4. Now you can add the modified `kubeconfig` in Prowler Cloud. Then simply test the connection.
---