aws.pkl provisions the EKS cluster and then the workload on top of
it:
Common patterns
Bookstore on EKS
An AWS infrastructure pattern, deployed with formae.
A full-stack bookstore application running on a managed EKS cluster. This example
lives in the formae Kubernetes plugin, and the AWS entry file provisions the
cluster itself (a VPC with public subnets, an internet gateway and routing,
cluster and node IAM roles, security groups, and an EKS AutoMode cluster) and
then deploys the workload onto it: a namespace, ConfigMaps and a secret, a
backend service account, an nginx frontend deployment behind a LoadBalancer
service, and a Node.js API backend behind a ClusterIP service. formae orders the
whole graph, so the cluster is ready before the Kubernetes resources land on it.
Deploy. Apply the AWS entry file. The cloud is chosen by which entry file you
apply, so
Verify. Once the command completes, the EKS cluster is under management:
Tear down. Remove everything the forma created. Because the workload depends
on the cluster, cascade the destroy to its dependents:
The full forma is in the
bookstore example.