On Mon, 2018-04-09 at 14:00 +1000, Roger Clarke wrote: > [But back then I'd never come across any provider who had a clue how > to even detect the geographical and/or jurisdictional location of an > instance, far less how to prevent an instance being run up in a > jurisdictional location that was on a blacklist, or missing from a > whitelist.
AWS is aware of where any given instance is, right down to the square metre. Users know down to the city. Although AWS could be lying when they say that ap-southeast-2a is in Sydney. There really is no way to tell. Assuming AWS is not lying, it is not required that one be aware of instance locations. If you just say "give me an instance" you will get one - somewhere. But you can then find out where it is. If you want to not set up instances in particular regions it's not really AWS' job to stop you. However, they provide tools so that you can stop yourself. It's probably those sorts of steps that defence is talking about for Azure. And maybe Azure doesn't have the tools. Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (ka...@biplane.com.au) http://www.biplane.com.au/kauer http://twitter.com/kauer389 GPG fingerprint: A0CD 28F0 10BE FC21 C57C 67C1 19A6 83A4 9B0B 1D75 Old fingerprint: A52E F6B9 708B 51C4 85E6 1634 0571 ADF9 3C1C 6A3A _______________________________________________ Link mailing list Link@mailman.anu.edu.au http://mailman.anu.edu.au/mailman/listinfo/link