Migrating from AWS to a Dutch sovereign cloud
Does your application run on AWS, and do you want to bring your data and systems under European jurisdiction? We translate your AWS environment into open alternatives at sovereign Dutch providers: S3 becomes S3-compatible object storage, RDS becomes managed PostgreSQL or MySQL, and Lambda becomes a container. Appfront handles the application changes and the migration; for the infrastructure we work with specialist Dutch partners.
What does migrating from AWS to a sovereign cloud mean?
Migrating from AWS to a sovereign cloud means moving your applications, data and infrastructure from Amazon Web Services to a provider that falls entirely under European jurisdiction. The core of the problem: as a US company, AWS is subject to the US CLOUD Act, even in the EU regions of Frankfurt, Amsterdam or Paris, and even within the announced AWS European Sovereign Cloud. Jurisdiction follows the parent company, not the location of the servers. If you want to demonstrably fall under EU law, you need to change provider, not region.
That requirement is becoming more concrete. The revised Dutch central government cloud policy of 3 July 2026 requires storage and processing within the EEA, mandates a risk assessment per cloud service and an annually reviewed exit plan, and advises against using public cloud for email and document management. NIS2, DORA and the GDPR also set requirements for how you control your digital supply chain. This page focuses specifically on translating AWS services; the general approach is described on our page about migrating applications to a sovereign cloud.
How we approach this
What we build and deliver
What can and cannot be replaced one-to-one
An honest picture up front prevents surprises during the migration. A large part of the average AWS environment has a mature European or open-source alternative. But some managed services are so specific to AWS that no exact equivalent exists. That functionality does not disappear: we solve it in the application layer, using open components that you keep control of yourself.
Easy to replace
- Object storage: the S3 API is a de facto standard, and EU providers support it
- Relational databases: RDS Postgres and MySQL migrate to managed equivalents
- Compute: translating EC2 and ECS/EKS to VMs and Kubernetes
- Messaging: SQS/SNS patterns map onto RabbitMQ or NATS
- CDN and DNS: European alternatives are available
No exact equivalent
Services such as DynamoDB, Step Functions, Cognito and EventBridge are tightly interwoven with the AWS platform. For these, we choose a solution in the application layer case by case: DynamoDB patterns, for example, land in PostgreSQL with jsonb, authentication moves to an open identity provider such as Keycloak, and we rebuild orchestration with open workflow components or explicit application code.
That is more work than a lift-and-shift, but the result is an environment with no hidden dependencies on a single vendor.
Who it's for
Organisations covered by the revised Dutch central government cloud policy and the BIO that need to move their AWS workloads within the EEA and under EU jurisdiction.
Institutions that process medical data under NEN 7510 and the GDPR and want to reduce their dependence on a US hyperscaler.
Organisations covered by DORA, applicable since 17 January 2025, that need control over ICT third parties and exit scenarios.
Organisations covered by the Cybersecurity Act (Cyberbeveiligingswet), which takes effect on 15 August 2026, and that want to demonstrably control their digital supply chain.
Technology and approach
We replace AWS-specific services with open, portable technology, so your environment is not locked in to a single vendor again after the migration. We capture the entire target environment in infrastructure as code, so the setup is reproducible and auditable, including for your exit plan.
Why Appfront
Appfront is an independent software and app development company. We know both the AWS side and the open alternatives, and in an AWS exit it is the application changes that are the real work: moving the infrastructure is rarely the problem, but the entanglement of your code with AWS services is. Because we don't sell hosting ourselves, our advice on where to land is not coloured by a platform of our own.
- Application changes and migration in one hand
- Independent advice on Dutch sovereign providers
- Honest about what can and cannot be replaced one-to-one
- Open standards and infrastructure as code as the foundation
Related services
If you are not coming from AWS but from another cloud, see migrating applications to a sovereign cloud or cloud exit and repatriation. If you want to set up a new environment on a sovereign basis, see building a sovereign cloud. For choosing a landing platform, our overview of the best sovereign cloud providers in the Netherlands can help.
Frequently asked questions
Get started with your AWS migration
Want to know what is involved in moving your AWS environment to a Dutch sovereign cloud? We are happy to walk through your services with you, without obligation, and give you an honest picture of what the translation involves.