From 6ba6b72bc49d3126367abc2719e15fcbd292a4fe Mon Sep 17 00:00:00 2001 From: Leo J <153937047+leiicamundi@users.noreply.github.com> Date: Thu, 16 Jan 2025 17:29:24 +0100 Subject: [PATCH] doc(self-managed): clarify quotas needed for AWS usage --- docs/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md | 4 ++++ .../setup/deploy/amazon/amazon-eks/terraform-setup.md | 4 ++++ docs/self-managed/setup/deploy/openshift/redhat-openshift.md | 4 ++++ .../self-managed/setup/deploy/amazon/amazon-eks/eksctl.md | 4 ++++ .../setup/deploy/amazon/amazon-eks/terraform-setup.md | 4 ++++ .../setup/deploy/amazon/openshift/terraform-setup.md | 4 ++++ 6 files changed, 24 insertions(+) diff --git a/docs/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md b/docs/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md index 4d80bb0c78d..561baf592d8 100644 --- a/docs/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md +++ b/docs/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md @@ -50,6 +50,10 @@ This guide results in the following: - [IAM Roles for Service Accounts](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html) (IRSA) configured and [Pod Identities](https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html). - This simplifies the setup by not relying on explicit credentials, but instead allows creating a mapping between IAM roles and Kubernetes service accounts based on a trust relationship. A [blog post](https://aws.amazon.com/blogs/containers/diving-into-iam-roles-for-service-accounts/) by AWS visualizes this on a technical level. - This allows a Kubernetes service account to temporarily impersonate an AWS IAM role to interact with AWS services like S3, RDS, or Route53 without supplying explicit credentials. +- [AWS Quotas](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) + - Ensure at least **3 Elastic IPs** (one per availability zone). + - Verify quotas for **VPCs, EC2 instances, and storage**. + - Request increases if needed via the AWS console ([guide](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html)), costs are only for resources used. This basic cluster setup is required to continue with the Helm set up as described in our [AWS Helm guide](./eks-helm.md). diff --git a/docs/self-managed/setup/deploy/amazon/amazon-eks/terraform-setup.md b/docs/self-managed/setup/deploy/amazon/amazon-eks/terraform-setup.md index f09f417a077..fe79e3c47fc 100644 --- a/docs/self-managed/setup/deploy/amazon/amazon-eks/terraform-setup.md +++ b/docs/self-managed/setup/deploy/amazon/amazon-eks/terraform-setup.md @@ -30,6 +30,10 @@ If you are completely new to Terraform and the idea of IaC, read through the [Te - This simplifies the setup by not relying on explicit credentials and instead creating a mapping between IAM roles and Kubernetes service account based on a trust relationship. A [blog post](https://aws.amazon.com/blogs/containers/diving-into-iam-roles-for-service-accounts/) by AWS visualizes this on a technical level. - This allows a Kubernetes service account to temporarily impersonate an AWS IAM role to interact with AWS services like S3, RDS, or Route53 without having to supply explicit credentials. - IRSA is recommended as an [EKS best practice](https://aws.github.io/aws-eks-best-practices/security/docs/iam/). +- [AWS Quotas](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) + - Ensure at least **3 Elastic IPs** (one per availability zone). + - Verify quotas for **VPCs, EC2 instances, and storage**. + - Request increases if needed via the AWS console ([guide](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html)), costs are only for resources used. - This guide uses GNU/Bash for all the shell commands listed. ### Considerations diff --git a/docs/self-managed/setup/deploy/openshift/redhat-openshift.md b/docs/self-managed/setup/deploy/openshift/redhat-openshift.md index b488c8b1d95..7dc36e27ef4 100644 --- a/docs/self-managed/setup/deploy/openshift/redhat-openshift.md +++ b/docs/self-managed/setup/deploy/openshift/redhat-openshift.md @@ -49,6 +49,10 @@ Camunda 8 supports OpenShift versions in the Red Hat General Availability, Full - [jq (1.7+)](https://jqlang.github.io/jq/download/) to interact with some variables. - [GNU envsubst](https://www.gnu.org/software/gettext/manual/html_node/envsubst-Invocation.html) to generate manifests. - [oc (version supported by your OpenShift)](https://docs.openshift.com/container-platform/4.17/cli_reference/openshift_cli/getting-started-cli.html) to interact with OpenShift. +- [AWS Quotas](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) + - Ensure at least **3 Elastic IPs** (one per availability zone). + - Verify quotas for **VPCs, EC2 instances, and storage**. + - Request increases if needed via the AWS console ([guide](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html)), costs are only for resources used. - A namespace to host the Camunda Platform, in this guide we will reference `camunda` as the target namespace. ## Deploy Camunda 8 via Helm charts diff --git a/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md b/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md index e7d382f70be..0b9dafa0659 100644 --- a/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md +++ b/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/eksctl.md @@ -18,6 +18,10 @@ This guide provides a user-friendly approach for setting up and managing Amazon - [kubectl (1.30+)](https://kubernetes.io/docs/tasks/tools/#kubectl), a CLI tool to interact with the cluster. - [AWS CLI (2.17+)](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html), a CLI tool for creating AWS resources. - [eksctl (0.193+)](https://eksctl.io/getting-started/), a CLI tool for creating and managing Amazon EKS clusters. +- [AWS Quotas](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) + - Ensure at least **3 Elastic IPs** (one per availability zone). + - Verify quotas for **VPCs, EC2 instances, and storage**. + - Request increases if needed via the AWS console ([guide](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html)), costs are only for resources used. - This guide uses GNU/Bash for all the shell commands listed. ### Considerations diff --git a/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/terraform-setup.md b/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/terraform-setup.md index 26b85f8914e..621359e446c 100644 --- a/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/terraform-setup.md +++ b/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/terraform-setup.md @@ -32,6 +32,10 @@ If you are completely new to Terraform and the idea of IaC, read through the [Te - This simplifies the setup by not relying on explicit credentials and instead creating a mapping between IAM roles and Kubernetes service account based on a trust relationship. A [blog post](https://aws.amazon.com/blogs/containers/diving-into-iam-roles-for-service-accounts/) by AWS visualizes this on a technical level. - This allows a Kubernetes service account to temporarily impersonate an AWS IAM role to interact with AWS services like S3, RDS, or Route53 without having to supply explicit credentials. - IRSA is recommended as an [EKS best practice](https://aws.github.io/aws-eks-best-practices/security/docs/iam/). +- [AWS Quotas](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) + - Ensure at least **3 Elastic IPs** (one per availability zone). + - Verify quotas for **VPCs, EC2 instances, and storage**. + - Request increases if needed via the AWS console ([guide](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html)), costs are only for resources used. - This guide uses GNU/Bash for all the shell commands listed. ### Considerations diff --git a/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/openshift/terraform-setup.md b/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/openshift/terraform-setup.md index eca6ea8c5eb..4d146c2e9fa 100644 --- a/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/openshift/terraform-setup.md +++ b/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/openshift/terraform-setup.md @@ -30,6 +30,10 @@ If you are completely new to Terraform and the idea of IaC, read through the [Te - [kubectl (1.30+)](https://kubernetes.io/docs/tasks/tools/#kubectl) to interact with the cluster. - [ROSA CLI](https://docs.redhat.com/en/documentation/red_hat_openshift_service_on_aws/4/html/getting_started/rosa-quickstart-guide-ui#rosa-getting-started-environment-setup_rosa-quickstart-guide-ui) to interact with the cluster. - [jq (1.7+)](https://jqlang.github.io/jq/download/) to interact with some Terraform variables. +- [AWS Quotas](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) + - Ensure at least **3 Elastic IPs** (one per availability zone). + - Verify quotas for **VPCs, EC2 instances, and storage**. + - Request increases if needed via the AWS console ([guide](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html)), costs are only for resources used. - This guide uses GNU/Bash for all the shell commands listed. ### Considerations