AWS Activate gives us cloud credits and architecture support. That sentence tends to be read as "so that's where the product runs," and it isn't, so here is the boundary in full.
What runs in the cloud
This website. Internal tooling. The build pipeline. The ordinary corporate software estate that every company our size runs and on which nobody's production depends.
What doesn't
- Aesthon Featherline deploys against the MES/MOM environment a plant already runs, inside the boundary that plant chooses.
- Aesthon Cavity's solver runs on a single on-prem GPU box, because part geometry is design IP and it doesn't leave the building.
Why more than one
We hold memberships with more than one cloud program on purpose. Credits are a real benefit at this stage and we take them, but a vendor relationship that quietly starts dictating architecture is a liability we'd be selling to customers for years. Two of them cancel out.