Can you imagine working on that team and having to explain it to other people?
Uhm... as opposed to using it for what, exactly? I can't imagine how that would even look.
That's typical for Oracle clauses since the 90s. That's why I laugh whenever @FakeOracleLarry makes claims about how performant Oracle is. Put up or shut up.
I'm not making this up.
Someone reading this just dropped a cup of coffee on the floor.
Reasonable given what the service is, but you know some Microsoft attorney forced that phrasing into the terms.
That's not reassuring.
GovCloud: "AWS Services may not be used to process or store classified data. If you or your end users introduce classified data into the AWS Network, you will be responsible for all sanitization costs incurred by AWS."
AWS Lambdas: Use Them or Lose Them
"How many days is that?"
"I dunno, our docs suck. Make it Engineering's problem."
and then
"You agree not to use Amazon API Gateway for load testing."
If you're "MySQL compatible", you can't use DMS.
This is notable just because it's the first time I've seen this referenced in their terms for a service.
Did... Amazon Legal just tell me it's a violation of their terms for me to *receive* spam?
I want them enforcing that on GitHub PRs.
Well that explains why it's showing my BI analyst pictures of beer.
You know the lawyer drafting this fantasized about contracting the quotation marks to just surround the word "Professional."
*spit take* This is coming from *AMAZON*?! The "we will compete with EVERYONE" company?!
"Don't blame us when you drive into the bay because Alexa said to!"
Wait it does what?
You can just FEEL the hatred for flat, understandable pricing seeping out of this document.
I found the plot hard to follow, the characters unrelatable, and the climax generally unsatisfying.
...but I do moderate Reddit's /r/legaladvice in my off hours.