You own this. AWS Outpost is leased and you still also pay for the resource usage on top of the outpost unit itself. And this would not be integrated with your AWS account.
It's mostly not true that you still pay for resource usage on top of the Outpost unit. That's only true, AFAIK, for EBS local snapshots and Route 53 Resolver endpoints. The big boys--EC2 instances, S3 storage, and EBS volumes--are all "free" on Outposts. That is, included in the cost of the unit and not double-charged.
Charging for EBS local snapshots on your own Outpost S3 storage and Route 53 Resolvers on your own compute is a weird one. I don't know how they defend that. To me, it seems indefensible.
> You can purchase Outposts servers capacity for a three-year term and choose between three payment options: All Upfront, Partial Upfront, and No Upfront. … At the end of your Outposts servers term, you can either renew your subscription and keep your Outposts server(s), or return your Outposts server(s). If you do not notify AWS of your selection before the end of your term, your Outposts server(s) will be renewed on a monthly basis, at the rate of the No Upfront payment option corresponding to your Outposts server configuration.
> You can purchase Outposts rack capacity for a 3-year term … either renew your subscription and keep your existing Outposts rack(s), or return your Outposts rack(s)
Route 53 on outposts doesn’t charge for your own compute. The outpost resolver is free. The oupost resolver endpoint must be backed by an in-region resolver endpoint, which doesn’t become free just because you own an outpost. What you’re paying for is the ability to sustain high query volume from instances in your VPC to an on-prem DNS server.
