docs(aws): dual-region setup in AWS (#3430)

* docs(aws): add dual-region setup

* docs(aws): additions to the dual-region setup

* docs(aws): switch to tabs and collapsables for dual-region

* docs(aws): further adjustments to the dual-region

* style(formatting): initial technical review

* docs(aws): pull request adjustments

pre-cloning setup

* docs(aws): dual-region switch to git clone

* docs(aws): pull request adjustments

* docs(aws): remove tabs and simplify with more scripts

* docs(aws): use new folder path

* docs(aws): implement pr suggestions

* small tweak

---------

Co-authored-by: Christina Ausley <[email protected]>

docs/self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/terraform-setup.md

@@ -86,19 +86,21 @@ The [AWS Terraform provider](https://registry.terraform.io/providers/hashicorp/a
 There are several ways to authenticate the `AWS` provider.
 
 - (Recommended) Use the [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) to configure access. Terraform will automatically default to AWS CLI configuration when present.
-- Set environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`, where the `key` and `id` can be retrieved from the [AWS Console](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html).
+- Set environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`, which can be retrieved from the [AWS Console](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html).
 
 :::
 
 :::warning
 
-Do not use secrets in your configuration files.
+Do not store sensitive information (credentials) in your Terraform files.
 
 :::
 
 :::warning
 
-The user who creates the resources will always be the owner. This means the user will always have admin access to the Kubernetes cluster until you delete it. Therefore, it can make sense to create an extra [AWS IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html) that's solely used for Terraform purposes.
+A user who creates resources in AWS will therefore own these resources. In this particular case, the user will always have admin access to the Kubernetes cluster until the cluster is deleted.
+
+Therefore, it can make sense to create an extra [AWS IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html) which credentials are used for Terraform purposes.
 
 :::
 

optimize_sidebars.js

@@ -1787,6 +1787,10 @@ module.exports = {
                       "Install Camunda 8 on an EKS cluster",
                       "self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eks-helm/"
                     ),
+                    docsLink(
+                      "Dual-region setup",
+                      "self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/dual-region/"
+                    ),
                     docsLink(
                       "IAM roles for service accounts",
                       "self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/irsa/"

sidebars.js

@@ -835,6 +835,7 @@ module.exports = {
                     "self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eks-eksctl",
                     "self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eks-terraform",
                     "self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/eks-helm",
+                    "self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/dual-region",
                     "self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/irsa",
                   ],
                 },

versioned_docs/version-8.4/self-managed/platform-deployment/helm-kubernetes/platforms/amazon-eks/terraform-setup.md

@@ -86,19 +86,21 @@ The [AWS Terraform provider](https://registry.terraform.io/providers/hashicorp/a
 There are several ways to authenticate the `AWS` provider.
 
 - (Recommended) Use the [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) to configure access. Terraform will automatically default to AWS CLI configuration when present.
-- Set environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`, where the `key` and `id` can be retrieved from the [AWS Console](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html).
+- Set environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`, which can be retrieved from the [AWS Console](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html).
 
 :::
 
 :::warning
 
-Do not use secrets in your configuration files.
+Do not store sensitive information (credentials) in your Terraform files.
 
 :::
 
 :::warning
 
-The user who creates the resources will always be the owner. This means the user will always have admin access to the Kubernetes cluster until you delete it. Therefore, it can make sense to create an extra [AWS IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html) that's solely used for Terraform purposes.
+A user who creates resources in AWS will therefore own these resources. In this particular case, the user will always have admin access to the Kubernetes cluster until the cluster is deleted.
+
+Therefore, it can make sense to create an extra [AWS IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html) which credentials are used for Terraform purposes.
 
 :::