11–20 of 145 posts
EKS Anywhere sounds promising, but I fear the data transfer charges between the two.
Are most multi-cloud setups just very careful about intra-cloud data transfers?
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 Disclaimer - I used to work for AWS
I get its heavily dependent on the team, just wondering from your perspective.
Posts like these always seem buried in deep marketing lingo. Can anyone "in the know" ELI5 how this is different than Google Anthos? [1] 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. [1] https://cloud.google.com/anthos
The post does mention Azure's Arc and Sentinel, but definitely should have called out Anthos specifically. The interesting part of this to me isn't so much that other solutions already exist -- Azure and GCP, due to their catch-up position, have always been far more conciliatory toward the reality of other cloud workloads than AWS. It's that AWS is signaling, however grudgingly, that they will have to play ball with…
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 Disclaimer - I used to work for AWS
Posts like these always seem buried in deep marketing lingo. Can anyone "in the know" ELI5 how this is different than Google Anthos? [1] 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. [1] https://cloud.google.com/anthos
The post does mention Azure's Arc and Sentinel, but definitely should have called out Anthos specifically. The interesting part of this to me isn't so much that other solutions already exist -- Azure and GCP, due to their catch-up position, have always been far more conciliatory toward the reality of other cloud workloads than AWS. It's that AWS is signaling, however grudgingly, that they will have to play ball with…
Edit, screenshot: https://postimg.cc/kRmGmSJh
Earlier quoted context omitted.
The post does mention Azure's Arc and Sentinel, but definitely should have called out Anthos specifically. The interesting part of this to me isn't so much that other solutions already exist -- Azure and GCP, due to their catch-up position, have always been far more conciliatory toward the reality of other cloud workloads than AWS. It's that AWS is signaling, however grudgingly, that they will have to play ball with…
Hi Forrest, hopefully constructive feedback - your choice of font color (rgb(74, 93, 133) I think) for text overtop #fff background is extremely washed out for me, not quite unreadable but heading in that direction. I might suggest a darker choice of font color for better readability, I just gave up trying to finish reading the article due to eye strain. Edit, screenshot: https://postimg.cc/kRmGmSJh
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?
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 Disclaimer - I used to work for AWS
This should answer your question and hint what's to come.
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? Presumably with EKS you can already run your worker…
Then before switching providers write new interface pods?
Sounds easier said than done but I guess that's one option.