Controversy in the Netherlands over the decision of SIDN to migrate the management of .nl domains to AWS.

The recent decision by the Foundation for Internet Domain Management in the Netherlands (SIDN) to move its .nl domain management infrastructure to Amazon Web Services (AWS) has sparked a wave of reactions on social media platforms like LinkedIn. The controversy revolves around the choice of an American company to host critical internet infrastructure in the Netherlands.

Loek Bakker, SIDN’s new CTO, announced that over the next two years, all of SIDN’s ICT infrastructure would be migrated to AWS. According to Bakker, this change aims to streamline technical management and open up new possibilities for service development. However, this decision has not been well received by several experts and professionals in the Dutch tech sector.

Concerns and Criticisms Expressed on LinkedIn

The concerns expressed on LinkedIn focus on several key aspects:

Dependence on a Foreign Company: Comments like those from William Edwards of Cyberfusion criticize the reliance of a critical resource of Dutch society on an American company, questioning the lack of consideration for the geopolitical situation.

Worries about Digital Sovereignty: Alex Bik, CTO of BIT B.V., and others express concerns about digital sovereignty and the movement of critical data outside the European Union, at a time when other parts of the world are seeking to reduce their reliance on cloud computing.

Impact on the Local Technology Sector: Some, like Koen de Jonge, an IT infrastructure expert, and Jeroen Oldenhof, CTO at CJ2 Hosting, view this decision as a snub to the Dutch hosting and data center industry.

Questions about SIDN’s Strategy: There are those, like Mathijs Kadijk, founder of Nonstrict, who wonder about the strategy and risk analysis that led SIDN to this decision, especially considering the existence of alternative providers in the Netherlands or the EU.

Doubts About Independence and Autonomy: Wido den Hollander, CTO at Your.Online, questions SIDN’s assertion that the registration system will become independent from specific cloud providers, arguing that the choice of AWS itself suggests otherwise.

SIDN’s decision has sparked significant debate about digital sovereignty, dependence on foreign providers, and the impact on the local IT industry. The criticisms and concerns expressed on platforms like LinkedIn reflect a growing awareness of the importance of maintaining local control and management of critical digital infrastructures. The situation poses a dilemma about how to balance technological innovation with national sovereignty and security.

Concerns about ‘Vendor Lock-In’

An additional concern expressed on social media, especially LinkedIn, about SIDN’s decision to migrate to AWS is the risk of ‘vendor lock-in’. This refers to the dependence on a single cloud service provider, which could limit SIDN’s ability to switch to other providers in the future.

Explanation of SIDN regarding ‘Vendor Lock-In’

In response to these concerns, SIDN has explained that they are aware of the importance of avoiding ‘vendor lock-in’. They claim that there is currently no mature European alternative, but they are open to switching to a European option as soon as one becomes available. Therefore, they have emphasized the need for an exit strategy.

SIDN’s Strategy to Avoid Dependence on a Single Provider

SIDN’s strategy involves following “provider-agnostic architectural principles” when migrating to the cloud. This entails using open standards whenever possible and implementing the fewest specific AWS functions. Each step of the process will be carefully evaluated.

Commitment to Transparency and Shared Knowledge

SIDN has also committed to sharing its knowledge with stakeholders, including aspects that, in hindsight, could have been handled differently. They plan to compile a manual documenting best practices and errors in provider-agnostic cloud engineering, based on their experience. Cristian Hesselman, Director of SIDN Labs, and CTO Loek Bakker will provide further details in a future blog.

In summary, SIDN’s decision to migrate to AWS has sparked significant debate, focused not only on digital sovereignty and the impact on the local tech sector, but also on the risks associated with ‘vendor lock-in’. The tech community in the Netherlands and beyond is closely monitoring the situation, hoping that SIDN’s strategy to avoid dependence on a single provider and their promise of transparency will serve as a case study in managing critical digital infrastructures.

References: SIDN news and LinkedIn.

Scroll to Top