Eclipse Dataspace Components on AWS: Architecture patterns in production

This article presents production-ready architecture patterns for deploying Eclipse Dataspace Components (EDC) connectors on AWS, emphasizing isolation, managed services, and security best practices.

• EDC connectors consist of control and data planes deployed as containers in Amazon ECS with AWS Fargate for serverless orchestration
• Use managed services including Amazon Aurora for persistence, AWS Secrets Manager for credentials, and Amazon Cognito for OAuth 2.0 client credentials
• Amazon S3 provides durable data storage for shared and received data through the data space
• Amazon API Gateway and Network Load Balancer enable secure, private network connectivity with VPC links and IAM/SigV4 protection
• Infrastructure-as-Code with AWS CDK enables automated, templatized deployment of isolated connector cells
• Implement defense-in-depth security through network isolation, security groups, IAM least privilege, and encryption at rest and in transit
• Design for regional resilience with cross-zone load balancing, Aurora multi-AZ replication, and independent control/data plane scaling
• Treat observability as first-class with Amazon CloudWatch Container Insights and structured health check endpoints

Production EDC deployments require deliberate architecture decisions combining community best practices with AWS recommendations to achieve fault tolerance, scalability, and security while minimizing operational complexity.