Eclipse Dataspace Components on AWS: Architecture patterns in production
Running Eclipse Dataspace Components (EDC) connectors in production on AWS requires deliberate architecture decisions around isolation, managed services, and security layering. In Part 1 of this series, we covered the fundamentals of data space architectures and EDC per the International Data Space Association’s (IDSA) standards. If you are new to EDC, we recommend starting there.
Related articles
Cloudflare WAF protects WordPress applications from two high-severity vulnerabilities
Cloudflare has deployed two WAF rules in response to high-severity vulnerabilities disclosed to us by the WordPress security team. The new rules protect all Cloudflare customers using affected WordPress versions, but customers should still update immediately to a patched release
Eclipse Dataspace Components on AWS: Cost optimization strategies
When you deploy Eclipse Dataspace Components (EDC) connectors on AWS, one of the first challenges you face is predicting and controlling the cost of the required infrastructure. Without clear benchmarks, it is difficult to make informed decisions about workload sizing, environment configuration, and long-term investment. Part 1 of this 3-part blog series covered the fundamentals
Eclipse Dataspace Components on AWS: Data sharing fundamentals
This three-part blog series offers a comprehensive guide to implementing Eclipse Dataspace Components (EDC) on AWS. The first installment lays the theoretical groundwork, covering IDSA standards, the Dataspace Protocol (DSP), and the essential architecture of EDC. The second part focuses on practical deployment patterns suitable for production, utilizing AWS services such as Amazon Elastic Container Service (ECS) and Amazon Aurora. The series ultimately aims to facilitate successful EDC implementation on AWS.