<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hello Alun, while I welcome this technical move towards the cloud and a more resilient infrastructure, please let's not forget to avoid any deadlocks in the future. I could also envision a difficult situation for DNS over HTTPS (i.e. how would you run HTTPS without DNS?). What I want to say is, core-services that are fundamentally important, such as the RIPE-Database or RPKI-validations rely on direct availability. In case of a catastrophic AWS failure, or simply "bootstrapping the Internet" - let's always keep this in mind that we are able to start up the net without too many interwoven services. So this is a vote towards "keep also a plan-b in reserve" in case there a problem. All the best - and please keep healthy, regards, Kurt <div class="moz-cite-prefix">Am 10.05.21 um 13:40 schrieb Alun Davies: </div> <blockquote type="cite" cite="mid:FC210712-4ECE-4992-A1DE-E554B6AA7855@ripe.net"> <pre class="moz-quote-pre" wrap="">Dear colleagues, The mission critical services the RIPE NCC provides to the Internet community require a solid technical foundation. In this new article on RIPE Labs, Felipe Silveira looks at plans to use cloud infrastructure as a means to that end. The full article is available here: <a class="moz-txt-link-freetext" href="https://labs.ripe.net/author/felipe_victolla_silveira/rpki-repositories-and-the-ripe-database-in-the-cloud/">https://labs.ripe.net/author/felipe_victolla_silveira/rpki-repositories-and-the-ripe-database-in-the-cloud/</a> Kind regards, Alun Davies RIPE Labs Editor RIPE NCC </pre> </blockquote> </body> </html>