> They all seem to have some weird genesis as data transfer gateways (looks like a local network share, but really sends data back to S3 or some other cloud sto

> They all seem to have some weird genesis as data transfer gateways (looks like a local network share, but really sends data back to S3 or some other cloud store), and they all seem to have weird compromises… Yes, but Id say they _should_ be data transfer gateways and instead we ended up with _faux disconnected ec2_ racks. From what Ive seen the bulk of outpost usage is really close to the data gateway; “Im an onprem/hybrid customer, give me an EC2 vpc endpoint in my existing DC so I can move data and run some workloads mixed mode.” But instead outposts morphed in to “How do we fit EC2/EBS/S3/RDS in to an on prem rack that their cloud team can manage with our existing APIs.” Thats very much a different product and (IMO) a harder, bordering on unsolvable, problem. Getting down to many thousands of single RU appliances is only making it more impossible and disconnected from the AWS “mainline” infra. Id be REALLY interested to see a version of the outpost product that was a single 1-2RU whitebox router with a handfull of 100/400 gb ports and APIs to setup the tunneling/encap/VPC connections for each port. Give them local “vpc endpoints” termination and “direct” connectivity in to their VPC resources back in the region. But that looks a lot more like a DX kind of product than outposts, I think