message: Ref arch aws cost estimate improvement - switch to on-demand nodes
diff: @@ -23,10 +23,10 @@ title: "Single-Cluster Reference Architecture"
  # Single-Cluster Reference Architecture for Production Purposes
  | | |
  -| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  +| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  | Intended for: | Continous usage of Gitpod at a company-wide scale in a reliable way by leveraging popular cloud provider services such as S3 and RDS. |
  | Limitations: | - This is bound to a single cluster. Deploying in several regions requires setting up several Gitpod installations <br /> - Requires external dependencies (Object storage, registry, database) to be set up |
  -| Cost Estimates: | - [AWS\*](https://calculator.aws/#/estimate?id=258a343acea8193acd54ffabf1a61e203389439a): With the configuration in this estimate, you would be able to run 36 concurrent basic workspaces - assuming the same density as currently used in Gitpod Saas. Your mileage _will_ vary. <br /> \* Cost estimates do not include egress - however, we typically see egress cost to be an additional 15% on top of the estimates here. These estimates are just examples - the exact cost will depend on your set-up and usage profile. |
  +| Cost Estimates: | High-level cost estimates\*: <br /> - [AWS](https://calculator.aws/#/estimate?id=de4a90f9d1bd454e35ff0e1efa1ab6a0df79e0b5) <br/> \* With the configuration in these estimates, you are able to run 36 concurrent basic workspaces - assuming the same density as currently used in Gitpod SaaS. Cost estimates do not include egress. However, we typically see egress cost to be an additional 15% on top of the estimates here. These estimates are just examples - the exact cost will depend on your set-up and usage profile - your cost _will_ deviate. |
  This guide describes a single-cluster reference architecture for Gitpod aimed at production environments: continuous deployments of Gitpod used in anger by your engineers. It consists of a Kubernetes cluster, cert-manager, external MySQL database, external OCI image registry, and external object storage. It includes instructions on how to set up this reference architecture on the officially supported cloud providers.
  