I wonder if Amazon’s theory here is that by offering multi-cloud support they can put decision makers at ease when choosing cloud vendors by making them feel like they’re not getting locked into AWS - but Amazon also expects most customers to mostly only use AWS out of convenience<p>Disclaimer - I used to work for AWS
Don’t read too much into this — they are just catching up with GCP and Azure here. AWS has a history of introducing half-assed products with great fanfare when the lack of such a product could be a disadvantage for customer acquisition (think Beanstalk, Cognito or Amplify).
Posts like these always seem buried in deep marketing lingo. Can anyone "in the know" ELI5 how this is different than Google Anthos? [1]<p>If they are in fact similar, I can't help but be left wondering why ACG didn't devote at least a sentence or two to comparisons that already exist in the industry.<p>[1] <a href="https://cloud.google.com/anthos" rel="nofollow">https://cloud.google.com/anthos</a>
How long before someone releases a multi-multi-cloud solution so that we don't have to lock ourselves into a particular vendor's multi-cloud solution?
Isn't this the same thing Google is doing with Anthos and Azure is doing with Arc? As I understand it, those solutions are both wider in scope than this. I'm not entirely up to date on those, but this seems more like AWS half-heartedly following the pack than something new.
Finally. I made a very similar suggestion to the ECS product manager about 5 years ago. We were moving from Mesos to ECS and I was losing the ability to manage Docker containers on our on-premises servers so I suggested allowing us to run the ECS Agent on our on-premises servers. This would allow us to centrally manage those servers and would get AWS into our on-prem infrastructure...
Unrelated but is ACG a good learning platform?<p>I'm never sure with these types of platforms because I am not interested in any certifications and such, so it is hard to tell whether they just teach the stuff needed for these certifications and nothing more...
Isn't EKS just Kubernetes with custom integrations for various AWS services? If so, how do you meaningfully bring EKS to another cloud without bringing those services? Does EKS call over the public Internet into those other AWS services (and thus lower latency, paying for network usage, etc)? If so, what's the advantage of running EKS anywhere other than on Amazon?<p>Presumably with EKS you can already run your worker nodes on prem or on GCP or wherever, so is this just moving the masters over as well? If you're willing to run your other AWS services on AWS, what's the big advantage of running EKS outside of Amazon as well?
Can someone comment on what does this mean for VMware? On one hand this supports their new vSphere offering, but on the other it provides a competition for managed Kubernetes clusters. In the FAQ they write "Adding bare-metal support will address customer desire to eliminate the license cost and operational overhead of managing VMware." But is this really going to happen with enterprises running on bare metal serves? Seems rather unrealistic.
There has been a player in "AWS compatible workloads" for quite some time, the french company Outscale:<p><a href="https://us.outscale.com/products/compute/aws-compatible-cloud/" rel="nofollow">https://us.outscale.com/products/compute/aws-compatible-clou...</a><p>They have PoPs in several "exotic" locations, but I'm not entirely sure the list is public. They also run AWS-compatibles clouds for state actors.
All these multi-cloud things by the big clouds are more like ways of putting each big cloud in control of other clouds. They're more a way for them to fight over their center of gravity.<p>A true multi-cloud solution would be cloud agnostic and independent.
It feels like a commoditize the competition strategy. Essentially the single deployment structure makes your competitors impossible to differentiate other than on price, while still being the access point to the cloud.