Eclipse Dataspace Components on AWS: Cost optimization strategies

Summary

Deploying Eclipse Dataspace Components (EDC) connectors on AWS presents challenges in forecasting infrastructure expenses without clear benchmarks. Estimated costs differ substantially between business-critical setups and non-critical environments based on compute and database sizing. A business-critical configuration relying on Amazon Aurora PostgreSQL db.r6g.large and standard Amazon ECS with AWS Fargate totals an estimated 387.00 USD monthly in the eu-south-2 region. Sizing down to db.t4g.medium and switching to AWS Fargate Spot lowers the non-critical monthly expense to 164.00 USD, representing a 58% reduction. Core cost drivers remain baseline infrastructure components, while storage, API calls, and data transfers contribute marginally under baseline assumptions.

Takeaways

1. 1

   Amazon Aurora PostgreSQL and Amazon ECS compute represent the primary cost drivers for EDC deployments rather than usage-based charges like API Gateway and S3.

2. 2

   Using db.t4g.medium and AWS Fargate Spot for non-critical workloads reduces estimated monthly connector infrastructure costs from $387.00 to $164.00, a 58% reduction.

3. 3

   AWS Graviton-based instances such as r6g and t4g families provide improved price-performance and energy efficiency per watt compared to equivalent x86 instances.