-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Hi - I work on both projects so happy to share any insights. Currently, EKS blueprints rely on the terraform-aws-eks module for provisioning the control plane resources and has its own implementation for node groups/fargate profiles. There are plans to move all of cluster creation over to use the terraform-aws-eks module since this is what we see most commonly used from customers for cluster creation. The main difference between the two projects is that the terraform-aws-module is just focused on creating an EKS cluster and the necessary resources required (IAM roles, policies, security groups, etc.) whereas the EKS blueprints are creating not only a cluster but also bootstrapping it with the software that users require to support workloads. This is where the EKS blueprints addons and teams functionality comes into play.
As I'll soon need to spin up an EKS cluster from scratch due to a new role, I've been looking into what my options are for speeding up the process of provisioning the necessary infrastructure and add-ons to run the usual workflows. Most notably, I've come across the eks-blueprints project and the terraform-aws-eks module, the latter of which seems to be older and more widely adopted because of that. The plan is to run the entire thing on Fargate, as I'm the only architect on the team and due to other responsibilities would rather run everything without having to manage EC2 instances and node groups.