Configure AWS access using GCP ServiceAccount (GKE)
This method outlines the procedure for configuring AWS access through a GCP ServiceAccount. It is designed to establish secure cross-cloud access, allowing C8 managed by Google Cloud Platform (GCP) to interact seamlessly with AWS services.
Step 1: Enable Workload Identity (skip if already enabled)
You can enable Workload Identity on an existing Standard cluster by using the gcloud CLI or the Google Cloud console. Existing node pools are unaffected, but any new node pools in the cluster use Workload Identity.
Note You can check the current status by running the command gcloud container clusters describe CLUSTER_NAME --region=COMPUTE_REGION --format="value(workloadIdentityConfig)
Replace the following:
CLUSTER_NAME: the name of your existing GKE cluster.
COMPUTE_REGION: the Compute Engine region of your cluster. For zonal clusters, use --zone=COMPUTE_ZONE.
PROJECT_ID: your Google Cloud project ID.
Step 2: Create a service account and bind it with a k8s service account
Step 2.1: Create the c8-backend service account and bind it with the k8s service account
Important Replace the PROJECT_ID with the project ID of the Google Cloud project of your IAM service account.
Annotate the Kubernetes Service Account, which can be achieved by adding an annotation to the c8-backend service account during the Helm installation command(or by using the BACKEND_SA_ANNOTATION variable with the installation helper script).
Annotate the Kubernetes Service Account, which can be achieved by adding an annotation to the c8-djw service account during the Helm installation command(or by using the DJW_SA_ANNOTATION variable with the installation helper script).