3 ms·
That feels like they used the ground work laid with AWS Outposts to enable such smaller auxiliary local zones as well: In both cases the control plane still res
by Dunedan 7y ago
That feels like they used the ground work laid with AWS Outposts to enable such smaller auxiliary local zones as well: In both cases the control plane still resides in the "real" region, but the data plane for a local zone and an AWS Outpost is located somewhere else (customer data center or in the case of this local zone somewhere in LAX). I'd even bet that the hardware that they use to power AWS Outposts and such a Local Zone is the same. Of course obviously the scale and the offered services are different.
- someotherone 7y agoThere's definitely similarities, but I could see it being totally different too. Outposts in only 16 racks max; I'd assume this is much more than that. Outposts is for single user and this is for everyone. Billing models presumably differ. Outposts goes in user's DC whereas I assume this is hard connected to AWS network backbone. IDK if making these based on the same infra would be the right abstraction layer.
- jedberg 7y agoThey said during they keynote that they used the outpost technology to make this happen.