Add overview for "Running apps" component

_docs-sources/foundations/network-topology/index.md

@@ -13,7 +13,7 @@ Our standard network architecture includes:
 - DNS forwarding for a management VPC
 - Optionally, tags for an EKS cluster
 
-## Out of the box setup
+## Out-of-the-box setup
 
 Gruntwork will generate the IaC code you need to set up our standard, recommended VPC configuration, as detailed in our [VPC service catalog module](/reference/services/networking/virtual-private-cloud-vpc).
 

_docs-sources/foundations/running-apps/index.md

@@ -0,0 +1,44 @@
+# About Running Apps
+
+The Running Apps component is focused on enabling your organization's developers to run their apps and workloads.
+
+## Available approaches
+
+Running Apps includes first-class support for running workloads on EKS, ECS, and individual Lambda functions. You may use just one approach or all three, though we recommend limiting your management surface area as much as possible.
+
+### EKS
+
+Our standard EKS setup leverages IaC to give you:
+
+- A best-practices [EKS cluster configuration](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-eks)
+- Support for either [self-managed or managed worker nodes](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-eks-workers)
+- [Out-of-the-box support](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-eks-core-services) for log configurations, ALBs, external DNS and more
+- [IAM role to RBAC mappings](https://docs.gruntwork.io/reference/modules/terraform-aws-eks/eks-aws-auth-merger/)
+- Support for cluster autoscaling, including with [Karpenter](https://docs.gruntwork.io/reference/modules/terraform-aws-eks/eks-k8s-karpenter/)
+- An opinionated GitOps workflow ("GruntOps") that includes ArgoCD
+
+### ECS
+
+Our standard ECS setup leverages IaC to give you:
+
+- A best-practices [ECS cluster configuration](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-ecs-cluster)
+- The option to use [ECS Fargate](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-ecs-fargate-cluster) if desired
+- A way to deploy [ECS services](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-ecs-service)
+- ECS service discovery, load balancer support, canary deployments, and more
+
+### Lambda
+
+We support invoking Lambda functions across a range of scenarios:
+
+- [General-purpose Lambda function](https://docs.gruntwork.io/reference/modules/terraform-aws-lambda/lambda/)
+- [Lambda behind an API Gateway](https://docs.gruntwork.io/reference/modules/terraform-aws-lambda/lambda-http-api-gateway/)
+- [Lambda@Edge](https://docs.gruntwork.io/reference/modules/terraform-aws-lambda/lambda-edge/)
+- [Scheduled Lambda jobs](https://docs.gruntwork.io/reference/modules/terraform-aws-lambda/scheduled-lambda-job/)
+
+For running complex Serverless applications, we recommend the [Serverless Framework](https://www.serverless.com/), which is available separately via Serverless, Inc.
+
+## Out-of-the-box setup
+
+A Gruntwork subject matter expert in EKS, ECS, or Lambda will help you design a strategy for deploying apps using your preferred methodology, and provide support while you configure the Gruntwork modules to implement your strategy.
+
+If you are looking to add functionality not yet supported by Gruntwork, you can either add this on your own, or we will consider those requests for our roadmap or as part of a separate, paid engagement.

docs/foundations/network-topology/index.md

@@ -13,7 +13,7 @@ Our standard network architecture includes:
 - DNS forwarding for a management VPC
 - Optionally, tags for an EKS cluster
 
-## Out of the box setup
+## Out-of-the-box setup
 
 Gruntwork will generate the IaC code you need to set up our standard, recommended VPC configuration, as detailed in our [VPC service catalog module](/reference/services/networking/virtual-private-cloud-vpc).
 
@@ -32,6 +32,6 @@ This is done by directly working with the Terraform modules from Gruntwork Libra
 <!-- ##DOCS-SOURCER-START
 {
   "sourcePlugin": "local-copier",
-  "hash": "0a04285644a8f01f58325dd000d66fba"
+  "hash": "250fd5235210081650ae0f4cee677505"
 }
 ##DOCS-SOURCER-END -->

docs/foundations/running-apps/index.md

@@ -0,0 +1,52 @@
+# About Running Apps
+
+The Running Apps component is focused on enabling your organization's developers to run their apps and workloads.
+
+## Available approaches
+
+Running Apps includes first-class support for running workloads on EKS, ECS, and individual Lambda functions. You may use just one approach or all three, though we recommend limiting your management surface area as much as possible.
+
+### EKS
+
+Our standard EKS setup leverages IaC to give you:
+
+- A best-practices [EKS cluster configuration](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-eks)
+- Support for either [self-managed or managed worker nodes](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-eks-workers)
+- [Out-of-the-box support](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-eks-core-services) for log configurations, ALBs, external DNS and more
+- [IAM role to RBAC mappings](https://docs.gruntwork.io/reference/modules/terraform-aws-eks/eks-aws-auth-merger/)
+- Support for cluster autoscaling, including with [Karpenter](https://docs.gruntwork.io/reference/modules/terraform-aws-eks/eks-k8s-karpenter/)
+- An opinionated GitOps workflow ("GruntOps") that includes ArgoCD
+
+### ECS
+
+Our standard ECS setup leverages IaC to give you:
+
+- A best-practices [ECS cluster configuration](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-ecs-cluster)
+- The option to use [ECS Fargate](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-ecs-fargate-cluster) if desired
+- A way to deploy [ECS services](https://docs.gruntwork.io/reference/services/app-orchestration/amazon-ecs-service)
+- ECS service discovery, load balancer support, canary deployments, and more
+
+### Lambda
+
+We support invoking Lambda functions across a range of scenarios:
+
+- [General-purpose Lambda function](https://docs.gruntwork.io/reference/modules/terraform-aws-lambda/lambda/)
+- [Lambda behind an API Gateway](https://docs.gruntwork.io/reference/modules/terraform-aws-lambda/lambda-http-api-gateway/)
+- [Lambda@Edge](https://docs.gruntwork.io/reference/modules/terraform-aws-lambda/lambda-edge/)
+- [Scheduled Lambda jobs](https://docs.gruntwork.io/reference/modules/terraform-aws-lambda/scheduled-lambda-job/)
+
+For running complex Serverless applications, we recommend the [Serverless Framework](https://www.serverless.com/), which is available separately via Serverless, Inc.
+
+## Out-of-the-box setup
+
+A Gruntwork subject matter expert in EKS, ECS, or Lambda will help you design a strategy for deploying apps using your preferred methodology, and provide support while you configure the Gruntwork modules to implement your strategy.
+
+If you are looking to add functionality not yet supported by Gruntwork, you can either add this on your own, or we will consider those requests for our roadmap or as part of a separate, paid engagement.
+
+
+<!-- ##DOCS-SOURCER-START
+{
+  "sourcePlugin": "local-copier",
+  "hash": "5fadf65f5d6750b170d643866ccf2c8c"
+}
+##DOCS-SOURCER-END -->

sidebars/foundations.js

@@ -91,6 +91,18 @@ const sidebar = [
           },
         ]
       },
+      {
+        label: "Running apps",
+        type: "category",
+        collapsed: false,
+        items: [
+          {
+            label: "Overview",
+            type: "doc",
+            id: "foundations/running-apps/index",
+          },
+        ]
+      },
       // TODO: Disabling for now until it's an offering
       // {
       //   label: "Maintenance Foundations",