Skip to main content

About Running Apps

The Running Apps component is focused on:

  • Enabling your organization's developers to run their containerized apps
  • Enabling your organization's developers to run individual Lambda functions
  • Adopting patterns for managing multiple clusters across many teams

What's included

  • Strategy. For EKS, Gruntwork has an opinionated GitOps workflow we call "GruntOps."
  • IaC Modules. Running Apps includes access to several IaC modules relating to EKS, ECS, and individual Lambda functions.
  • Tooling. We make use of Kubernetes ecosystem tooling like Karpenter and Argo, in addition to our own tooling to improve the UX for ECS and Lambda.
  • Setup. Our modules include documentation on how to configure an EKS or ECS cluster.
  • Updates. Gruntwork publishes regular updates to EKS, ECS, and Lambda modules, and you can use Patcher to automatically update to the latest version of these modules.

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:

ECS

Our standard ECS setup leverages IaC to give you:

Lambda

We support invoking Lambda functions across a range of scenarios:

For running complex Serverless applications, we recommend the Serverless Framework, which is available separately via Serverless, Inc.

Missing functionality

If you are looking to add functionality not yet supported by Gruntwork, you can either contribute a pull request, add the functionality on your own, work with Gruntwork as part of paid engagement, or request we add it to our roadmap.