Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
SImplify your infrastructure using Pulumi
What do you like best about the product?
I've been doing overall automation and continuous deployment for over a decade, but it wasn't until I discovered Pulumi that I went all-in for the infrastructure part. As a developer I prefer to use code compared to yaml or something else. I like it because it gives me more trust, if you use a strongly typed version of pulumi like Typescript, and faster feedback since you get answers back directly during compilation.
Having things in code also makes it possible to run "patch jobs" for resources in-process instead of running that code outside the provisioning. Being able to run the "patch job" in-process is excellent for the rare occasions when there might be a missing option in the SDK, which has happened once over three years with the Azure AD provider.
I would argue that most companies need a tool like Pulumi, since the pure cloud tools are limited to just that cloud provider. If you are a larger company, you also want to automate things like Kubernetes, GitHub, Opsgenie and other services out there, and Pulumi has support for a lot of them.
Pulumi automation is another feature we have used to build a self-service application where anyone can "order" different resources through a simple UI and then the application would create them using Pulumi in a compliant manner.
Lastly I would also like to highlight how Pulumi deals with configuration and secrets. How you both store secure configuration in Pulumi and share outputs between different deployments in Pulumi is a killer feature that has simplified a lot of work for us. I often use Pulumi to deal with configuration for more minor things where I'm testing things out since it is much more secure than copying a file. Storing secrets in the Pulumi configuration also makes it very easy to get a new user app running by creating a small script that reads the config and sets appropriate environment variables to get going.
If there is one "infrastructure as code" tool I would recommend, it is Pulumi!
Having things in code also makes it possible to run "patch jobs" for resources in-process instead of running that code outside the provisioning. Being able to run the "patch job" in-process is excellent for the rare occasions when there might be a missing option in the SDK, which has happened once over three years with the Azure AD provider.
I would argue that most companies need a tool like Pulumi, since the pure cloud tools are limited to just that cloud provider. If you are a larger company, you also want to automate things like Kubernetes, GitHub, Opsgenie and other services out there, and Pulumi has support for a lot of them.
Pulumi automation is another feature we have used to build a self-service application where anyone can "order" different resources through a simple UI and then the application would create them using Pulumi in a compliant manner.
Lastly I would also like to highlight how Pulumi deals with configuration and secrets. How you both store secure configuration in Pulumi and share outputs between different deployments in Pulumi is a killer feature that has simplified a lot of work for us. I often use Pulumi to deal with configuration for more minor things where I'm testing things out since it is much more secure than copying a file. Storing secrets in the Pulumi configuration also makes it very easy to get a new user app running by creating a small script that reads the config and sets appropriate environment variables to get going.
If there is one "infrastructure as code" tool I would recommend, it is Pulumi!
What do you dislike about the product?
If you are using a cloud tool that isn't well known, the provider for it might be lacking some features, but most users use the more prominent vendors with good coverage.
What problems is the product solving and how is that benefiting you?
It simplifies infrastructure and gives us a better overview of what we have in our system landscape. Using Pulumi definitely speeds up the time it takes for us to create things like a new environment from development to production, creating active directory groups for security and setting up GitHub repositories faster.
- Leave a Comment |
- Mark review as helpful
my insight in pulumi
What do you like best about the product?
Ability to use different programming languages as code that suits any developer .
Can be deployed for multiple cloud provider
Can be deployed for multiple cloud provider
What do you dislike about the product?
In my opinion, no downside, but it has space to improve much better with new feature
What problems is the product solving and how is that benefiting you?
its helps me when deploy serverless design, , continerization archtecture
Good tool for easy start
What do you like best about the product?
As a Software Engineer I like the ability to use the same programming language (Go in my case) I use for the main application. It's easier to start to create infrastructure with Pulumi then with other tools.
What do you dislike about the product?
Small overhead in Go, for example wrappers for basic data types like pulumi.String, pulumi.Bool, etc. I want more native support in Go language. Also will be good to have option to create Dynamic Resource Providers in Go.
What problems is the product solving and how is that benefiting you?
We don't have DevOps Engineers in our team so all Software Engineers support our infrastructure and Pulumi allows to do this using the same programming language.
Enabling modern software development for infrastructure
What do you like best about the product?
Pulumi enables for infrastructure code all the quality-of-life improvements that we software developers have come to expect for other code. With it, I have rich IDE support, excellent unit and integration testing capabilities, great static and dynamic analysis, tight integration into build and deployment pipelines, and all the other things that I now consider essential for a satisfactory development experience.
The support (both paid and community-provided) is excellent, the ecosystem of extensions is extensive, and the catalogue of examples is very good (and improving all the time).
Adopting it as a free tool initially means you have to rapidly learn some of the harder concepts; when the tool proves its worth to you and your organization, you naturally move to the paid services and quickly realize how much value they provide across a team and a company.
The support (both paid and community-provided) is excellent, the ecosystem of extensions is extensive, and the catalogue of examples is very good (and improving all the time).
Adopting it as a free tool initially means you have to rapidly learn some of the harder concepts; when the tool proves its worth to you and your organization, you naturally move to the paid services and quickly realize how much value they provide across a team and a company.
What do you dislike about the product?
I've been wracking my brain about this one. I can't think of a dislike that lasted any length of time. There were a few non-obvious learning hurdles along the way, which would have annoyed me as I was working through them, but they've just required a slight shift in thinking or an "a-ha!" moment.
I guess I don't like the implementation of some of the official Pulumi extensions. As an experienced user, I have seen some bits of sugar within their AWSX library in particular that I recommend against using. The base implementation within their classic libraries is no more difficult (albeit a bit more verbose) and avoids some recurring problems that are regularly asked about on the Pulumi community Slack.
I guess I don't like the implementation of some of the official Pulumi extensions. As an experienced user, I have seen some bits of sugar within their AWSX library in particular that I recommend against using. The base implementation within their classic libraries is no more difficult (albeit a bit more verbose) and avoids some recurring problems that are regularly asked about on the Pulumi community Slack.
What problems is the product solving and how is that benefiting you?
It shares the knowledge burden of infrastructure design and implementation across more of the team.
It allows all our developers to read (and if they want, write) infrastructure code, including the tests and related requirements, which breaks down knowledge barriers and increases inclusivity. The details of how the applications and services run in the cloud are no longer hidden from the people writing those applications and services.
It allows all our developers to read (and if they want, write) infrastructure code, including the tests and related requirements, which breaks down knowledge barriers and increases inclusivity. The details of how the applications and services run in the cloud are no longer hidden from the people writing those applications and services.
How much is a "best in class" solution worth?
What do you like best about the product?
Pulumi brings IaC to the next level by allowing to encode your infrastructure in general purpose languages. This is better than alternatives like Terraform which forces the usage of HashiCorp Configuration Language (HCL).
What do you dislike about the product?
A year into our subscription with Pulumi, my team was contacted by a Pulumi representative who told us our subscription fee would TRIPLE by the end of the year, reaching 60k-100k annually, despite us signing a contract with them previously. In addition to this, Pulumi's website and CLI can both be very slow.
What problems is the product solving and how is that benefiting you?
Pulumi brings programmatic infrastructure as code and manages the state of our stack in the cloud (thus removing the need to backup our state).
showing 21 - 25