"No longer does the process involve the purchase of heavy proprietary software with multi-year contracts that include annual maintenance fees. "
I guess the two sides really don't know how each other works....
What does AWS have to do with Prime? And what type of license lock-in do they have that compares to Oracle's? You can cancel anyone at any time almost without penalty (other than forfeiting a refund if you cancel before your contract), nor do you have a pervasive multi-thousand-dollar per-core license lock-in with either, do you?
I've worked in multiple Oracle shops, so I know what that lock-in entails. With that comparison of yours, I don't you know what you are talking about?
Additionally, as long as you don't really lock yourself to a AWS-specific framework or architecture, like, say, AWS Lambda, you really have little lock in. Whether is is a JEE system or a Ruby system or whatever backed by any major data store (MySQL, Postgress, Cassandra, whatever), if you are deploying on an AWS instance, you very much can do the same with a local instance using the same OS.
OTH, and I known from experience, when you work with the Oracle stack, not just the database but also any or all products built on top of its database or WebLogic, you lock yourself in architecturally very easily. Oh shit, there you go, you are now tied to say, Oracle SOA or ADF, or IDM or with WebLogic JEE extensions.
I actually like Oracle products, and having access to their support network is awesome. But I recognize the significantly devious ways in which Oracle ties you in if you are not careful (and let's face it, most developers and architects aren't.) Ergo the lock-in.
You barely see that with AWS, or even Azure. So...