We do have quite a lot of AWS deployments and clients in certain countries.
We use it for spinning up environments, using infrastructure as code. We use it for disaster recovery and high availability for creating BMs for testing. Mainly on the service side, we use it for setting up environments and spinning up environments.
The monitoring is the most valuable aspect of the product.
Technical support is available if you need it.
The solution is stable.
The scalability is okay. It's similar to what you would get with Azure.
The interface needs a bit of work. It's not intuitive.
The solution's initial setup can be complex.
I've been using AWS for about 15 years. It's been a very long time.
The stability is fine. I haven't had issues with crashing or bugs or glitches.
The solution's scalability is pretty good. These solutions are pretty well known for not being able to scale well. They behave very differently at scale. I wouldn't say it's any better or worse than Azure is; it's probably on par.
Internally, we have about 500 people using the solution right now.
I have never used technical support myself, although it's my understanding that our team does from time to time. We do all the first line ourselves. Anything that escalates to the third line, we have contracts in place to help us get assistance.
I found the initial setup to be pretty complex. It's just getting more and more complex, with the infrastructure as CodePipelines and that sort of thing. On a scale of one to five, one being the worst and five being the best in terms of complexity, I'd say it's a three.
I have no idea what the operational side does in terms of maintenance. It's not an aspect that falls under my responsibilities.
I don't handle the licensing side of things and therefore cannot comment on the price of the solution.
We also looked at Azure DevOps.
I'm a customer and an end-user.
We use various deployments, including on-premises, public, private, and hybrid clouds. The deployment is dependent on the customer, the solution, and the service level agreements that we have. We use all of those models. We make our choice based on the requirement.
I'd advise potential new users to actually do a shootout between the different products based on your use case and choose the right one.
I would rate the solution seven out of ten. I'd rate it higher, however, the UI needs improvement first.