11–20 of 38 posts
This never supported a "multi cloud" solution in the sense that things are running on two clouds simultaneously, but it did let you fail-over to a different cloud. Now it only lets you fail-over to Amazon if I read the docs correctly.
I have no faith in AWS executing on this successfully. I'd imagine an offering like the suggested one would have some kind of: a) UI to inspect the state of other clouds, b) provisioning capability that allows creation of resources in other clouds. On the UI front: - AWS UI toolkit has aged by this point and each day it feels more dated - CloudFormation, as their main cloud management UI is particularly bad (e.g. lim…
I agree with you on Terraform and Pulumi (I'm especially excited about the latter, due to extra benefits over Terraform). However, I think that you are missing the main point / theme of the post - it is not specifically about AWS' approach to multi-cloud, but rather about general dynamics of the multi-cloud trend.
This article is not far off in its prediction that AWS would support multi-cloud natively eventually if that's what the market demands (See also: AWS Marketplace). We are very early in our journey and are multi-cloud already and because we're bootstrapped, cost ultimately decides what we use. And no, I don't mean multi-cloud in a way Netflix does it, but in a way where different parts of our system are hosted wholly…
How do you keep the costs down with egress pricing? If the parts of your applications are distributed through cloud providers you all the time are exporting data to egress. Thats not a cheap concept or did you build your software with this in mind?
Edit: You probably would want it for performance first though
Earlier quoted context omitted.
I agree with you on Terraform and Pulumi (I'm especially excited about the latter, due to extra benefits over Terraform). However, I think that you are missing the main point / theme of the post - it is not specifically about AWS' approach to multi-cloud, but rather about general dynamics of the multi-cloud trend.
Check out Terraform CDK for a thing that is native to TF, allows real code, and is progressing real fast
I have no faith in AWS executing on this successfully. I'd imagine an offering like the suggested one would have some kind of: a) UI to inspect the state of other clouds, b) provisioning capability that allows creation of resources in other clouds. On the UI front: - AWS UI toolkit has aged by this point and each day it feels more dated - CloudFormation, as their main cloud management UI is particularly bad (e.g. lim…
I would like to try it out as a Terraform replacement, but but the popularity and corresponding module availability and maturity is hard to match.
I have no faith in AWS executing on this successfully. I'd imagine an offering like the suggested one would have some kind of: a) UI to inspect the state of other clouds, b) provisioning capability that allows creation of resources in other clouds. On the UI front: - AWS UI toolkit has aged by this point and each day it feels more dated - CloudFormation, as their main cloud management UI is particularly bad (e.g. lim…
Do you have practical experience with Pulumi in large deploymenets? Is it bug free and dependable? I would like to try it out as a Terraform replacement, but but the popularity and corresponding module availability and maturity is hard to match.
While we did have to write some of our own tooling to reduce the boilerplate over different services, Pulumi has been by far the best tool we've found to do the deployments. Being able to automatically provision a resource in AWS, then use results from that in a Kubernetes service (env var) in the same deployment, is not something I ever expected to be able to automate.
We haven't had any issues with module availability (I think it uses/adapts Terraform modules to a large extent). The config as code feels way more approachable and reusable than any other tool I've seen.
I've never had any production issues because of Pulumi. It also allows you to preview changes before applying them, giving a nice confidence boost in the changes.
Earlier quoted context omitted.
Do you have practical experience with Pulumi in large deploymenets? Is it bug free and dependable? I would like to try it out as a Terraform replacement, but but the popularity and corresponding module availability and maturity is hard to match.
My team has a lot of practical experience with Pulumi, after using custom bash scripts, manually-managing AWS config, some Terraform and CloudFormation in the past. We use it for dozens of services on Kubernetes and AWS. While we did have to write some of our own tooling to reduce the boilerplate over different services, Pulumi has been by far the best tool we've found to do the deployments. Being able to automatical…
FWIW we do that with a small amount of glue code in our deployment tool that takes terraform outputs and passes then as values into helm.
Earlier quoted context omitted.
Do you have practical experience with Pulumi in large deploymenets? Is it bug free and dependable? I would like to try it out as a Terraform replacement, but but the popularity and corresponding module availability and maturity is hard to match.
My team has a lot of practical experience with Pulumi, after using custom bash scripts, manually-managing AWS config, some Terraform and CloudFormation in the past. We use it for dozens of services on Kubernetes and AWS. While we did have to write some of our own tooling to reduce the boilerplate over different services, Pulumi has been by far the best tool we've found to do the deployments. Being able to automatical…
Terraform does this very well too, using either the Kubernetes provider or the Helm provider.
Is that the "multi-cloud management tool" The Information heard about? Not exactly how I would have characterized it...
[0] https://aws.amazon.com/blogs/containers/advice-for-customers...