AWS requirements

Amazon Web Services

The page lists the requirements for deploying to Amazon's cloud solution 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.30+
  • 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 necessary, depends on other software used auto-scaling of pods can increase usage
• AWS Relational Database System (RDS)
  • PostgreSQL v14
  • RDS Proxy
  • Sizing: 4 vCPUs and 16 GB RAM (db.m6i.xlarge); adjust as necessary to workload
• AWS ElastiCache
  • Redis OSS v7
  • Sizing: 2 vCPUs and 1.37 GB RAM (cache.t3.small); adjust as necessary to workload
• AWS MQ (AMQ)
  • ActiveMQ v5.18
  • Sizing: 2 vCPUs and 1 GB RAM (mq.t3.micro); adjust as necessary to workload
• MongoDB Atlas
  • MongoDB v6
  • VPC Peering to AWS application/Kubernetes VPC
  • Sizing: Set compute auto-scaling for minimum of M30 and maximum of M50; minimum of M30 required for auto-scaling, maximum can be adjusted to 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 emails). While AWS has the Simple Email Service (SES), most customers will have an existing SMTP server for this use.