Kind of crazy honestly? They were kind of famous for NOT doing this sort of thing - at all.
GCP just announced enterprise API's I see with some (pretty vague) promises about longevity.
> All AWS accounts created after December 4, 2013 are already VPC-only, unless EC2-Classic was enabled as a result of a support request.
There were announcements made at the time, but I don't remember if they explicitly called it a deprecated product at the time (hence why I hedged my wording in GP comment).
Amazon/AWS has deprecated and then put to the grave multiple payment services. I made that same comment when SimpleDB was deprecated and someone said the same thing. More recently, torrent support in S3 is being killed off with little notice.
"Amazon SimpleDB (N. Virginia) Service is operating normally" is their current status page, but their marketing materials doesn't show any SDB stuff. So if you had some old workload ticking over - you could just leave it usually.
I actually used SimpleDB in a light use case wildly past the point at which it disappeared from all marketing. I kept on expecting an email like the EC2-classic one, but it never came even though simpleDB didn't show up anywhere really
just one of those fun things that gets thrown in to make sure nobody ever fully understands the english language.
Ordnance and ordinance I don't even know the difference between though.
Were you storing PANs then?
Thats part of what people love about AWS compared to Google Cloud. Google is quick to kill off services it finds no longer convenient for it to run. AWS has historically gone out of its way to keep old services running even as it releases new, better alternatives.
Update: it looks like we're executing a migration plan this year by building seemingly-full parity between Mobile Hub and Amplify (https://docs.aws.amazon.com/aws-mobile/latest/developerguide...) such that "if you don't migrate your project to Amplify, your app will continue to function, and all your related cloud resources will continue to be available". This seems like a great solution for existing Mobile Hub customers.
Google has been doing it's best to make my life miserable. It recently killed Google Voice in the free edition, so my younger child can no longer get a phone number. With zero warning.
I've been through this each time I've (tried) to use Google for anything critical, so I've stopped.
I mentioned a family example since B2B would be confidential. But I can count at least a half-dozen instances of Google discontinuing something an employer has relied on, leading to a world of pain.
My general cloud policy is AWS, Azure, or anything-but-Google. I have a similar anti-Oracle policy too. Once you're burned a few times, you find that some companies are too expensive to do business with.
https://cloud.google.com/products/ https://cloud.google.com/blog/products/workspace
But it's a moot point in either case, if you want long-term support.
* Internal corporate lines shift with re-orgs
* Culture is shared and common
* I've had issues across Google. I listed the ones I can talk about.
My lesson, each time, has been:
Never Use Google For Business.
Ever.
The transition from Amazon Linux to Amazon Linux 2 on Elastic Beanstalk was pretty rough. The migration took a full week, and there was really only a six month window where it could be done.
One bad day, it took like 18 hours from deploy attempt started to AWS resolving the situation by fiddling knobs on their side.
Our deploys on ECS take like 15 minutes.
Would you recommend to invest time learning how ECS works or had your company hires that managed that?
My one compliant is around having fallback to on-remise providers / capacity provider etc support - doesn't seem fully fleshed out across ECS/Fargate/ECS anywhere but I may not have read docs properly yet.
Unlike Google.
From what I hear MMS stopped working a few months ago for iPhones on Google Fi.
I've been on Fi for years and its great.