Gives devs granular access to what is required rather than a generic login with broad access
We use it with software development of FMCG e-commerce websites.
How has it helped my organization?
It allows us to continuously deliver new builds quickly.
Also, devs at different levels can get granular access to whatever is required rather than getting a generic-style login that gives them access to large sections. This provides an audit trail for mistakes (not for finger-pointing but just to learn from them).
What is most valuable?
* Ease of access control (granular)
* Scalability
* Analytics
What needs improvement?
It can be slow producing Beekeeper reports but I think this was ironed out in a later release. (It was a multi-thread issue).
There are a lot of features, so some really good learning materials in various formats would be handy. I know there are a lot of webinars, but more high-level resources would be great for new staff; we all had to start somewhere.
How was the initial setup?
AWS makes it simple to use most products, as that’s its bread and butter: "Whatever you want to use, we can provide you with an environment." And it's the same with CloudBees. It’s no different to loading into a server in a back room, offshore, near-shore, virtual environment, etc. We didn’t have issues setting it up to run in a container on a Linux machine.
It's super-simple to start a stack, bootstrap, IAM role, SSH key pair, command-line updates, etc. These are fundamentals of AWS anyway.
What's my experience with pricing, setup cost, and licensing?
We chose to procure this solution via AWS Marketplace because the devs are a load of button-pushers so they are always trialing software on AWS to see how we can leverage AWS’ flexibility, scalability, and granular pricing model. Also, it made sense for us to use this as we had multiple clients. We got great control out of our builds this way.
What other advice do I have?
There are no comments to display