There&#x27;s a balance to be had, and there&#x27;s very likely different periods in a business lifecycle where some environments make more sense than others.<p>There&#x27;s a pretty big cost to learning how to manage and get value all the AWS stuff, and in the early days of a project - especially true in the &#x27;startup&#x27; world - there are probably more areas where $ can be spent to create more value.<p>I&#x27;ve seen far too many people spin up multiple AWS and tie themselves to expensive AWS setups when a small linode or other VPS (managed or otherwise) would have been more than adequate for the first year.<p>There&#x27;s this weird view people that have it&#x27;s either 100% AWS or hire full time developers and buy a bunch of bare metal.  There&#x27;s a lot of middle ground which can provide a good amount of value while giving you time to ramp up.<p>The fact that you&#x27;re referencing tying VPNs to a corporate network means you&#x27;re already far more advanced than a lot of the smaller orgs I&#x27;ve run in to tying themselves to AWS when far less expensive alternatives exist.<p>Again, saying this as someone who uses and likes Amazon stuff, just not exclusively.