Having explored this previously in the context of this (which was mostly vapourware when I looked at it a couple of years back) and the Azure equivalent:
1. Regulatory requirements.
2. There are no network - and hence egress - charges to the rest of your infra.
3. Limited ability to operate disconnected.
On the last point, the Azure offering is vastly, vastly superior, since the AWS one used to phone home and stop after a few hours, which undercuts the value on the third point. There are quite a few places with no local cloud presence, and unreliable connectivity to the nearest one; for example, last time I was in New Caledonia, there were multi-day outages and degradation to their sole fibre to the world. They do significant research workloads (thanks to the SPC) and something that could endure that while allowing you to keep using cloud APIs would be very convenient.
Having explored this previously in the context of this (which was mostly vapourware when I looked at it a couple of years back) and the Azure equivalent:
1. Regulatory requirements. 2. There are no network - and hence egress - charges to the rest of your infra. 3. Limited ability to operate disconnected.
On the last point, the Azure offering is vastly, vastly superior, since the AWS one used to phone home and stop after a few hours, which undercuts the value on the third point. There are quite a few places with no local cloud presence, and unreliable connectivity to the nearest one; for example, last time I was in New Caledonia, there were multi-day outages and degradation to their sole fibre to the world. They do significant research workloads (thanks to the SPC) and something that could endure that while allowing you to keep using cloud APIs would be very convenient.