Alfresco on AWS Deployment Architecture (2026): EC2, EKS, S3 & Cost Optimization
Deploying Alfresco Content Services (ACS) on Amazon Web Services can improve infrastructure flexibility, but architecture choices determine reliability and total cost of ownership. This practical guide covers an Alfresco AWS deployment architecture , Amazon EC2 versus EKS, S3 content storage, RDS PostgreSQL, search, messaging, security, cost assumptions, and configuration examples. Technical scope: This is a reference design, not a ready-to-run production configuration. Validate your exact ACS version, licensed connectors, chart release, search compatibility, and AWS region before implementation. Quick answer: Start with private Alfresco repository nodes behind an Application Load Balancer, RDS PostgreSQL, a supported S3 Content Connector, a version-compatible search stack, an ActiveMQ-compatible messaging service, and isolated transform services. Choose EC2 for simpler operational requirements or EKS when your team can maintain Kubernetes.