Amazon Web Services

This page lists the requirements for deploying to Amazon Web Services (AWS).

Suggested requirements for AWS

If deploying to AWS, ensure that you have the following:

• AWS Virtual Private Networking (VPC)
  • Subnets, routing tables, internet access, etc.
  • Load balancing, WAF, etc. for ingress into Kubernetes
• AWS Elastic Kubernetes Service (EKS)
  • EKS Cluster v1.34+
  • Pod Identity Agent
  • Network Policy Implementation (e.g. Calico or VPC CNI)
  • Custom Metrics Collection Implementation, e.g. Prometheus as kube-prometheus-stack and Prometheus Adapter as prometheus-adapter
  • Block storage CSI Provider
  • Shared file system CSI Provider
  • Node Pool: 4 nodes with 16 vCPUs and 64 GB RAM (m6a.4xlarge); adjust as needed (other software running on the cluster and pod auto-scaling can increase usage)
• AWS Relational Database System (RDS)
  • PostgreSQL v14
  • RDS Proxy
  • Sizing: 4 vCPUs and 16 GB RAM (db.m6i.xlarge); adjust as needed for your workload
• AWS ElastiCache
  • Redis OSS v7
  • Sizing: 2 vCPUs and 1.37 GB RAM (cache.t3.small); adjust as needed for your workload
• AWS MQ (AMQ)
  • ActiveMQ v5.18
  • Sizing: 2 vCPUs and 1 GB RAM (mq.t3.micro); adjust as needed for your workload
• MongoDB Atlas
  • MongoDB v6
  • VPC Peering to AWS application/Kubernetes VPC
  • Sizing: enable compute auto-scaling with a minimum of M30 and a maximum of M50; M30 is the minimum required for auto-scaling, and the maximum can be adjusted to suit your workload
• Apache Kafka Helm Chart
  • Kafka v29.3
• Neo4j Standalone Helm Chart
  • Neo4J v4.4 - Needs two standalone clusters (neo4j1 and neo4j2)
• AWS CloudFront
  • Refer to the AWS CloudFront Requirements page for details.
• AWS S3
  • Refer to the AWS S3 Requirements page for details.
• SMTP (no dedicated cluster needed; simply an SMTP endpoint for delivering email). AWS offers the Simple Email Service (SES), but most customers use an existing SMTP server.