AWS exitEU jurisdictionCLOUD Act

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

1
AWS inventory
We map your AWS environment: which services you use (S3, RDS, Lambda, SQS, CloudFront), which data flows and IAM policies exist, and which dependencies are embedded in the code.
2
Service-by-service translation
For each AWS service, we determine the target alternative at a Dutch provider, and we are upfront about where no exact equivalent exists and what that means for the application.
3
Adapting and migrating
We adapt the application, migrate data and configuration, and run in parallel where possible so we can switch over in a controlled way and fall back if needed.
4
Landing and operations
Your environment lands at a sovereign Dutch provider. Afterwards, we take care of monitoring, maintenance and further development of the application.

What we build and deliver

S3 to object storage
S3 buckets move to S3-compatible object storage at an EU provider. The API is largely the same, so code changes are limited to endpoints, credentials and bucket policies.
RDS to managed Postgres or MySQL
RDS databases migrate to managed PostgreSQL or MySQL, including data migration, user management, replication and backup policy.
Lambda to containers
We rebuild serverless functions as containers on Kubernetes: as a service, a scheduled job or a queue worker. The business logic stays; the platform becomes open.
SQS and SNS to RabbitMQ or NATS
We translate queues and pub/sub patterns into open alternatives such as RabbitMQ or NATS, paying close attention to delivery guarantees and retry behaviour.
Rebuilding IAM and networking
IAM roles, VPCs, security groups and secrets do not translate automatically. We redesign the identity and network model following the principle of least privilege.
CloudFront to an EU CDN
Static assets and caching move from CloudFront to a European CDN solution, including TLS certificates and cache rules.

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

Government and public sector

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.

Healthcare

Institutions that process medical data under NEN 7510 and the GDPR and want to reduce their dependence on a US hyperscaler.

Financial sector

Organisations covered by DORA, applicable since 17 January 2025, that need control over ICT third parties and exit scenarios.

NIS2 sectors

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.

Kubernetes / containers
S3-compatible object storage
PostgreSQL / MySQL
RabbitMQ / NATS
Keycloak
Terraform / infrastructure as code
EU CDN
Encryption in transit and at rest

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

Can we replace AWS one-to-one with a Dutch cloud?
Largely, but not entirely. Core services such as object storage, managed databases, containers and message queues have mature European or open source alternatives. For some managed services, such as DynamoDB or Step Functions, there is no exact equivalent; we solve that functionality in the application layer with open components. We state this per service in the migration plan upfront.
Our data is already in an EU region of AWS. Isn't that enough?
No, not if EU jurisdiction is the requirement. As a US company, AWS is subject to the US CLOUD Act, which allows the US government to demand data even if it is physically located in Frankfurt or Amsterdam. Jurisdiction follows the parent company, not the region where your data is stored.
What happens to our S3 buckets and RDS databases?
S3 data moves to S3-compatible object storage with a European provider; because the API is largely the same, the changes to your code are limited to endpoints and credentials. We migrate RDS databases to managed PostgreSQL or MySQL, including data migration, users and backup policy.
What do you do with our Lambda functions?
We rebuild Lambda functions as containers that run on Kubernetes or a comparable platform, for example as a service, scheduled job or queue worker. The business logic stays intact; we set up the invocation and scaling mechanisms again using open components.
Does Appfront provide the infrastructure itself?
No. Appfront is a software and app development company. We handle the application changes and the migration; for the infrastructure itself we work with specialist Dutch providers and give independent advice on which one fits your requirements.
Why is an exit plan relevant to this migration?
The revised Dutch Government Cloud Policy of 3 July 2026 requires public sector organisations to carry out a risk assessment and an annually tested exit plan for public cloud. An AWS migration is effectively the execution of such an exit plan. Outside the public sector too, regulators and NIS2 increasingly ask for demonstrable exit scenarios.

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.

Edit content