Add draft EKS CloudFormation templates#1
Merged
Conversation
Greenfield wrapper (eks-cluster.yaml): VPC + EKS + node group + OIDC. Base (firewall-eks.yaml): ElastiCache + Socket token in Secrets Manager + IRSA role, emitting the helm install command. Plus an example DNS-override Helm values file. Statically validated (cfn-lint, helm template, kubeconform); not deploy-tested.
Eric Hibbs (flowstate)
force-pushed
the
add-eks-cloudformation-drafts
branch
from
d443529 to
099c1ba
Compare
Eric Hibbs (flowstate)
changed the title
…humbprint Hardcoding an OIDC thumbprint is brittle and would fail a real deploy. Remove the in-template AWS::IAM::OIDCProvider and document associating it with eksctl utils associate-iam-oidc-provider (which fetches the correct thumbprint) after the cluster is created.
Douglas (dacoburn)
approved these changes
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Draft CloudFormation for deploying the Socket Firewall on EKS (firewall + Redis, DNS-override routing, self-signed certs, fail-open) — the EKS companion to the existing per-platform deployment templates (ECS Fargate, GCP Cloud Run, Azure Container Apps).
cloudformation/eks-cluster.yaml— greenfield: VPC + EKS + node group + OIDC provider.cloudformation/firewall-eks.yaml— base: ElastiCache + Socket token (Secrets Manager) + IRSA; outputs thehelm upgrade --installcommand.cloudformation/values/dns-override.values.yaml— example Helm values (DNS-override + Redis + self-signed).Validation
Static only, not deploy-tested:
cfn-lintclean,helm templaterenders,kubeconformstrict valid. Can't be verified statically (needs a real deploy): the OIDC thumbprint (placeholder), IRSA trust, ElastiCache reachability, and cluster bring-up.Status
Draft — see
cloudformation/README.mdfor caveats and open items (handoff vs. one-shot Helm install, ecosystem list).