What advice do you have for others considering Amazon AWS?

I can address a few questions to update the information. Concerning compliance certifications, 800 NS 800 security compliances are in place, and audit data must be managed depending on customer requirements. The data is encrypted during rest and in transit. I believe that Amazon AWS supports IoT devices and machine learning capabilities, and Amazon AWS is also supporting AI features. These capabilities are still being expanded. I do not work with some other products from Amazon AWS. I want to clarify that I am not using AWS SageMaker. Secrets Manager falls under KMS. Elastic Load Balancer is one service, and Elastic Block Store is another service that allows me to create external drives using EBS. My overall review rating for Amazon AWS is 8 out of 10.

My company works closely with Amazon AWS, so we have resident architects deployed into our organization. In terms of compliance, I do not directly work with it, but there are teams responsible for that aspect. We mainly use GitHub Actions and Jenkins for deployment, so we do not use Amazon AWS global deployment tools. We usually go to third-party tools for enhanced security features. We use Snyk, GitHub security, and TruffleHog for these purposes. On a scale of one to ten, I would give Amazon AWS a rating of eight for stability. Overall, I rate Amazon AWS a nine out of ten.

I can recommend Amazon AWS for every type of company, even a company with only one server using Amazon AWS is doing very well. I prefer Amazon AWS when comparing it with Azure. The reason I choose Amazon AWS over Azure is that it was the first cloud platform I learned, followed by Azure, making Amazon AWS always near and dear to me. I use their Generative AI service, where you ask questions and receive answers, but I don't use it regularly. Overall, the product is excellent. They are doing many innovations and new integrations while providing good services. However, they have started changing their pricing, which will cost customers more. It's a good overall product, and I rate it as 8.5 out of 10.

Most people prefer Amazon AWS due to its accessibility. Between Amazon AWS, Azure, and Google Cloud Platform, Amazon is considered number one, followed by Azure and then Google Cloud. I rate Amazon AWS overall as eight out of ten.

I recommend AWS as it's very scalable and cheap for some services. I rate the overall solution nine out of ten.

For those considering AWS, it's advisable to discuss cost reductions with vendors to make it more accessible for smaller organizations. I'd rate the solution nine out of ten.

I recommend the solution to others because of our smooth experience. I rate it an eight out of ten.

You can just go ahead with AWS with your eyes closed. You won't regret it. Overall, I would rate the solution an eight out of ten.

Overall, I would rate the solution a nine out of ten.

As of now, our company does not need to leverage Amazon AWS for Amazon Big Data Analytics or Amazon Machine Learning. In the future, Amazon AWS can be used to leverage the benefits of Amazon Big Data Analytics or Amazon Machine Learning. Presently, my company plans to stick with the microservices model. There is no need to maintain the product from our company's end since Amazon AWS takes care of the maintenance of the services the tool covers. For cost saving, shut down instances when not in use and use spot instances while implementing step scaling policies. Doing regular audits, you will get to know what resources in your environment are leading to cost consumption. AWS Global Cloud Infrastructure does not directly impact our company's application performance and availability. My company just consumes the services covered under Amazon AWS, after which we plan our application architecture. The impact is felt if Amazon removes support for some of its global products, as it may impact some legacy applications, but my company does not face many issues since we mostly upgrade such applications. I rate the overall tool a seven or eight out of ten.

I would recommend it as I believe the market is shifting towards a hybrid model. For optimal usability and enhanced availability, cloud solutions are preferable where applicable. Conversely, for in-house operations and specific requirements, AWS solutions can be leveraged effectively for cloud transitions when deemed suitable. Overall, I would rate it eight out of ten.

Same as I am telling my clients, When you are using AWS cloud you should think of the 5 pillars which are called AWS Well-Architected framework, these are :-

1- security

2- performance

3- cost

4- Reliability

5- operational excellence

Each one of them it's a very long topic, but to make it simple it's like when you need to build a building if the base it's not solid, in the future for sure you will have an issue and maybe in the middle of construction you the building will fall, same as for the cloud when you are using the cloud, you need to know exactly which services you will use and architect these services very well, the idea of the cloud is Automation, and eliminate human interaction as much as you can, I have seen client doing a lot of manual work in the cloud because they didn't take the 5 pillars into their consideration, the cost if you don't know what you are doing you will end up paying a lot of money for things you don't even use. it's a long discussion but I tried to make simple

Cost is the main issue one needs to consider. Need a whole heuristic view of what you use the AWS for, mainly for the data reporting, storage, backup/restore, etc. 

Data storage, for example. How you will use your existing data (if you have 30 years of them) or do you need just 10% of them for your current daily business. Then, 90% of your data could be site in AWS Glacier to save the storage cost.

Make sure you understand the cost structure of AWS. If you are coming from a traditional environment you need to identify the actual operation cost and the future state in AWS. You will have an important change on the financial cost, the main concern is to be able to explain cost integration and support benefits in the long term.  

From a technical point of view, this is the way to go or you will not be able to keep your technology up to date and take advantage of IT evolution. You will need to develop a roadmap to migrate while learning along the way.  

I would not select any specific public cloud provider without doing due diligence to what the customer specifically requires.

We work with the 3 primary cloud providers for our customers; AWS, Azure, and GCP.  A customer recently asked us to provide a comparison of AWS and Azure.

There's really not great differences between AWS and Azure but there are some.  The choice really needs to come down to the following criteria:

Region Availability, Sizing Availability (Depending on Application Requirements), Licensing costs, and finally the overall costs for services selected.

If your customer is a large Microsoft shop, getting the benefit of re-negotiating licensing costs by going to Azure can provide a very large benefit.

AWS is the Market Share leader but Azure is very close behind.  If Market Share is one of your primary selection criteria, then choose AWS.

Don't just pick one because you like them or your friend recommended them.  Get with a Cloud Partner and do the analysis for the customer's specific requirements.

For most of the customers looking for any public cloud service provider; as per my understandings, public cloud services should be acquired based on two basic going forward blocks/zero points/starting points to understand your needs.

1) The scale of business requirements and type.

2) Agility/Flexibility of existing IT infrastructure in-placed

For example, if you don't have any hardware/IT infrastructure in-placed and need to have a webserver for your new small business marketing website then instead of buying hardware/IT infrastructure it would be wise to get cloud services from any public cloud service provider or even you can get services from a web-hosting company that fits your budget; and then use it until you can afford it.

Then later on you can decide (based on business growth) to move further ahead to make your own IT setup or a Datacenter/IT infrastructure or even a private cloud. This example is lightning up the scale of requirement and type.

Another example, if you have a private cloud setup or IT infrastructure in place and need private cloud services to extend your business efficiency, flexibility, availability and simplicity. Then it would be a far cheaper and simple option if you choose that private cloud service provider who has the same manufacture public cloud connectors available from whom you setup your private could. This example is lightning up the Agility/Flexibility of existing IT infrastructure.

However, it is not wise in many cases and extremely expensive to put everything on a public cloud for small/medium business organizations.

I hope that it will help to get what you were asking for.

comprehensive cloud services solution, but need a strategic roadmap to implement. It's a journey. 

I would recommend the solution. Overall, I rate the product a ten out of ten.

I rate the product an eight out of ten.

I would rate the product a nine out of ten.

Amazon AWS was deployed on the cloud in my organization. Overall, I rate Amazon AWS an eight out of ten.

The amount of people for the maintenance of the solution depends on the engagement we have with our customers. Some of our customers are sophisticated with modern infrastructure and can handle most of the maintenance themself. The engineering team responsible for development also handles maintenance, upgrades, and support without any differentiation. However, some customers still follow an older mindset, where a separate ops team is responsible for platform maintenance and operations. One approach is to have a centralized model where a team of 20-30 members manages all the applications, including operations and maintenance. Alternatively, a distributed model may be used, where four or five different teams manage different aspects. However, on average, the team size for the entire IT organization is typically around 20-30 people. I strongly recommend this solution to others. I rate Amazon AWS an eight out of ten. I gave my rating of eight because the price of the feature is more expensive than the competitors.

I would rate this solution a nine out of ten.

I rate AWS eight out of 10. It's well designed and well documented. Overall, AWS is a good public cloud platform. Before signing up for AWS, it's probably a good idea to think about pricing because some of their services can be obtained elsewhere for a better price.

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.

It boils down to two points. The first point would be to have correct planning. You need to know what you want to do and you need to be familiar with what you can do in AWS. The second very important point is that you need very stable and very good monitoring of your AWS instances. This is mandatory because if you fire up a very expensive environment and forget it over weeks, you need to pay for that. I've seen a lot of companies struggling to get an overview of all these AWS machines. It starts by tagging and so on. I would rate it an eight out of ten.

I am a partner and reseller. I would advise them, before they use the account before they open an account with Amazon, to do their account around just to learn a bit about that solution and then start using it, because it will take a long time to understand how that platform works, how you're going to create a VM on there, how you can create an SMTP. It is not a simple procedure that we point to and then follows some steps to complete. You must be familiar with information technology. You must have at least basic IT knowledge of a hosting site. This is a platform, and before they begin using it, they must check a number of things and understand how they will proceed. I would rate Amazon AWS a seven out of ten.

My job role is as a Cloud Security Architect. I prepare solutions and I sell them to the customers. My work primarily involves working on identity systems. I primarily work on the identity federation side. You have identities and disparate sources, and we prefer to have a single identity source using federations and then we prepare solutions around it and sell them to our customers. Those kinds of solutions are the ones I work in. My advice for first-time users is, if you wish to migrate your private data center to a private cloud where you have servers like VPN servers, radio servers, you have servers for your own applications, whether it's Windows, Linux, Unix, or ADFS, it's better to go for an AWS cloud. However, if you are looking for identity Federation or identity provisioning, then you need to go for a Microsoft Cloud. I'll rate AWS at a seven out of ten due to the fact that it's very secure. It has very good migration categories for the on-premises servers and applications to the AWS private cloud. I can't rate it ten out of ten due to the lack of IdAM features I've seen, and AWS has less of a user base as it's not very user-friendly. This is where Azure scores a lot higher for me. It's very user-friendly and it's feature-rich, actually. If AWS can develop a more feature-rich offering, it will be on par with Azure.

I would recommend this solution to others who are interested in using it. I would rate Amazon AWS an eight out of ten.

I would encourage the student package for someone who is starting out, they can get acquainted with the interface and the tools available. I rate Amazon AWS a seven out of ten.

I would recommend this solution to others who are considering using it. It's very scalable and serverless. We are only charged for the functions that we use. This includes Lambda, which is a nice feature, in my opinion. I would rate Amazon AWS an eight out of ten.

I'm not an expert. I don't have any advice at the moment, but whenever they're looking to host some applications, when there's a lot of traffic or bandwidth, they should think about it carefully. I would rate Amazon AWS a seven out of ten.

I rate AWS nine out of 10. Everything is moving to the cloud now, and AWS covers a lot of services, including computing, networking, storage, IoT, and management, and they are good in every way. They face competition from GCP and Azure, but Azure is entirely a Microsoft stack, so people will go with that when they're working with Microsoft solutions. It is a little cheaper than AWS. In the end, the cloud you choose depends on the use case. It's up to the customer.

I would recommend this solution. I would rate it a nine out of 10.

I would recommend Amazon AWS to others. Amazon AWS are the market leaders in the public cloud service and after them, we have Microsoft Azure, and maybe Google Cloud. I rate Amazon AWS an eight out of ten.

We would recommend Amazon Web Services to someone who is looking for a global rollout or deployment. I would rate this solution a seven out of ten.

I would rate this solution 7 out of 10. My advice is to read about the solution. All of the learning is logical, and you can follow it and put it in practice. I believe it's a great product and great technology.

I rate Amazon AWS an eight out of ten.

It's quite good, I would rate Amazon AWS a ten out of ten.

Yes, I would recommend this solution. If we compare the three, I would rank Google first, Microsoft second, Amazon third, and the rest would follow. I would rate Amazon AWS a seven out of ten.

I would rate this product a seven out of ten.

We create some processes to resolve some questions the customers have. They want to improve and have more visibility of their data, and how to extract information about their data. We help them with this problem. Amazon AWS is the most important provider in the market. They have helped many of my customers. I rate Amazon AWS a nine out of ten.

If you are looking to implement Amazon AWS within your company, I would suggest finding someone that already knows some AWS as it has a harder adoption curve. I would rate it a six out of ten.

I've also used the server I built via Amazon AWS for our Android applications, and found the reliability and the stability of that server to really good. I can use it again next time when I'm into development. The server's always good. I had four customers on Amazon AWS. Those customers were architects working in technology and IT companies. I also created a server for our taxi application client as one of my projects. I have a local user. I had three to four people for deployment and maintenance. Some were nontechnical, while some were technical, with an IT background. Because I was on the free trial version of Amazon AWS, I didn't get to use their technical support. I used the free trial of Amazon AWS for my clients. I used it during the testing period. I developed applications for clients, then recommended AWS servers to them for the applications. I highly recommend this platform to others who are considering using it, because its stability is good. We have different requirements vs other users, so I'm not in a position to recommend features, especially because I have not used all the features of Amazon AWS. I can't say that this feature is good, or that feature is bad. I can't say which features to add to the next release. I'm rating Amazon AWS a nine out of ten and this is both from an integrator and customer perspective.

We are customers. We are using the latest version of the solution. I'd rate the solution at an eight out of ten.

We're a customer and an end-user. I'd rate the solution at a seven out of ten.

I rate AWS seven out of 10. My advice is to watch out for the cost. A public cloud means you can use any resource, and there is no upfront cost. That means someone can use an expensive computing solution that might cost them tons of money. No one is holding your hand, so you can use it, but you need to be conscious of the cost before using the solution.

We have customers who use the solution. I would rate the solution at a nine out of ten.

My advice for anybody who is implementing this solution is to have a strategy for calculating or monitoring the price. For example, have some alerts set up. I would rate this solution an eight out of ten.

I rate AWS nine out of 10.

I do recommendations for the development of cloud solutions. I would rate the solution at an eight out of ten.

I rate AWS 10 out of 10. AWS is a solid product. I feel confident I can provide a good level of service to my customers using AWS. To anyone thinking about using AWS, I would suggest carefully designing your implementation. This is very important because it will impact the monthly cost of the solution. You need to think ahead and talk with your staff to find opportunities to make this more efficient.

I would rate AWS 7.5 out of 10. There are a lot of options in this space, and Microsoft is also good. We are evaluating the data on each. We would rate Azure close to eight, so they're both great solutions.

This was deployed on the cloud. I don't remember which version because I didn't deploy it. I was not the person running the project of implementing AWS, but I know the client used it, but I don't know which version. It's not so difficult to use because there's a lot of tutorials. I'm not completely sure about the number of AWS users in our organization. We have a partnership with them so we have some accounts, but we don't completely have our load on AWS. We are mostly on Azure. Our main server is on Azure. On AWS, we mostly have some internal projects and services, but most of the main load is on Azure. We have a small workload on AWS. Sometimes we use it to deploy some of our best projects. We use it on some internal projects. It's a random thing so it could be 1,000 users or 50 users. I'll say approximately 200 to 500 users. We don't require too many people for deploying this solution because our projects are proof of concepts. Up to ten people from different departments would be needed for deployment if it's a business requirement e.g. people from Approvals and Projects, etc. As for increasing AWS usage, the organization sometimes thinks of moving some of the load to AWS because of good pricing, because currently, our main streams are on Azure, but it's not a sure thing. I'm unsure if there's any additional cost aside from the need to pay the license annually because I don't directly manage it. My advice to organizations looking into implementing AWS, especially if they're going to use it on a big scale, is to take advantage of AWS' organization model to make integration with their policies easier. It will also make administration easier for the different accounts, departments, and structure of the organizations thinking of moving to AWS. I would rate this solution a nine out of ten.

If you are considering Amazon AWS you should think about the cost of solutions and the ability to create systems and instances. I would rate this solution a 9 out of 10.

On the DevOps side, make sure you know what you're doing for security before you implement it. Make sure it is secure. I would rate it an eight out of 10.

Amazon AWS is a good solution. I rate Amazon AWS a nine out of ten.

I guess I would rate Amazon AWS eight out of 10. AWS works as advertised, but they're expensive if you don't know what you're doing. I'm not sure if I can knock them for not being transparent about pricing. Cloud costs are challenging. There's an entire industry popping up for managing cloud costs with consultants who can tell you how to get the most out of your AWS allocation. I don't have a lot of advice. If you're planning to implement a cloud solution, just pick one. I mean, if you're a Microsoft shop, it probably makes more sense to go Azure. If you're not, then I would recommend AWS. It depends on what you're looking to get out of it. There are references, architectures, case studies, and a million other things that would off better advice on whether to go with AWS or not. But if you're looking to go to the cloud, AWS is as good as everybody else. AWS is probably better than Azure and GCP, but that's a tricky thing to pin down. It depends on what your goals and requirements are. My best advice is to evaluate your goals before making a decision. I hope that people take what I say about AWS with a massive grain of salt because it's like asking an ant about an elephant. What's an ant going to know about an elephant? It's just too big for any one person to know.

I rate Amazon AWS 10 out of 10. For me, it's perfect. AWS is effortless to configure and has high availability.

I rate AWS nine out of 10. It's a complete solution. If Amazon added any more features, that would just be a pleasant surprise for me because AWS perfectly fits the needs of my current job.

I rate Amazon AWS a ten out of ten. I usually recommend AWS because I have loved using this tool. Most of the time, I recommend it as a real-time information and patching service with Lambda.

I rate AWS 9.5 out of 10. I would recommend it.

All the services and features provided by AWS are good. They are always improving their features. I recommend implementing the products on Amazon Web Services. It is a stable environment and mature cloud platform. I would rate the product an 8 out of 10.

Broadly speaking, there is a need to rely on specialists for properly setting up one's accounts and addressing his needs. This is not specific to Amazon, however, but is something prevalent with all providers. I have assumed the role of both customer and integrator. In the past, I worked as a project manager with different projects employing Amazon products, services and software. For the most part, the solutions I used have been public, not private, such as AWS cloud. The number of users of the solution varies with the individual project. This can range from 20 to 200 to 500 users. Our teams have undertaken every role, be them architecture, development, design or testing. They are all internally integrated. I am a fan of Amazon products and generally recommend them to others. Of course, we employ Azure and Google products when the customer specifically requests these. Since all products have room for improvement, even when this is not apparent to me, I rate Amazon AWS as a nine out of ten.

This solution is one of the top tools available for legacy migration. I would rate this solution as eight out of ten.

I would tell potential users to create a plan. It's very important to have a plan, especially if it's your first time. This is because different solutions and levels are charged separately with separate bills. On a scale from one to ten, I would give Amazon AWS a nine.

As a cloud-based solution, we are using the latest version all the time. I'd rate the solution at an eight out of ten. I would recommend the solution to other users and organizations.

I rate AWS a five out of ten, but it's mainly because I don't feel very experienced in AWS. I have gone to the console many times and seen many features that I have never used. I'm sure I can learn quickly, though, because there is a lot of information shared on the internet about how to use it—there are a lot of resources that you can use to learn, and there are a lot of features available on AWS. They're working very hard on their platform, and I can only see their usage growing in the future. I would certainly recommend AWS to others.

I'm just a customer and an end-user. I'd highly recommend the solution to other users. It's one of the best cloud options out there right now. I'd rate the solution at an eight out of ten.

I rate this solution a 10 out of 10. I would recommend it to others who are considering implementation.

I rate AWS eight out of 10. I used to work in Cognizant and TCS before that, and we used different cloud services, such as Amazon and Azure. If you want some kind of public cloud infrastructure, I would go with one of these or maybe Google Cloud. The university is in the process of setting up its own storage or server ecosystem. We plan to store massive amounts of video, images, and other objects, like our AI/ML workloads.

I would rate Amazon AWS an eight out of ten. I recommend this solution to anyone who wants to start using it.

I rate Amazon AWS a nine out of ten, primarily because I have a background in Java. Someone else with more experience in Microsoft technologies would probably prefer Azure. I recommend AWS to anyone considering implementing it because it's easy to use.

I absolutely recommend Amazon AWS to anyone who wants to start using it. I would rate Amazon AWS a 10 out of 10. That's the main reason why we're using it.

I would advise others to just plan out what they are looking for in terms of use cases. I would rate Amazon AWS an eight out of 10.

Training is critical before implementing the solution. There are very good AWS certifications like the certified practitioner, and there's a lot of free training on the AWS webpage that customers can use. Most of the training is hands-on so you can experience how things would be done in a work environment. AWS recently deployed 100 free courses on amazon.com to help people better understand their products. I would recommend looking at those. I rate this solution nine out of 10.

Amazon has a great customer base and lot of success stories. That is one advantage that AWS has, whereas the others are catching up. Recently they have more case studies, but for overall breadth of the industry and breadth of the customer experiences, AWS has more customers. AWS has more services than the other competitors. My advice to anyone thinking about using Amazon AWS is that they need to set up the foundation well, and they need to choose the right partner to do the implementation. The more experience the partner has, the better the implementation will be. On a scale of one to ten, I would give Amazon AWS an eight.

My advice to anyone considering Amazon AWS is that they should plan properly for their spending and they should have good control over their technology team. Otherwise, if the technology team doesn't know enough and they keep on creating more services, you'll be surprised with the invoice. Technology and finance should work very, very closely in the cloud. On a scale of one to 10, I give Amazon AWS a 10. It's a really good product.

The solution is good for integration. It's very flexible and customizable with other services, public, cloud and on-premise.

I would recommend this solution to others. I rate Amazon AWS a nine out of ten.

I rate Amazon AWS a seven out of ten.

I recommend trying Amazon AWS. You have nothing to be afraid of, as long as you're clear that you can handle your build. This product is suitable for any company, whether small, medium, or large. I would rate Amazon AWS an eight out of ten, just because there's always room for improvement.

My advice for those thinking about the implementation of Amazon AWS is to start using it, do not have fear to use these services. If you know how it works and you receive the right support, it always helps to reduce the cost and headache of IT. I rate Amazon AWS an eight out of ten.

I would recommend this solution to others. I rate Amazon AWS an eight out of ten.

I would recommend this solution to others. I rate Amazon AWS an eight out of ten.

I rate Amazon AWS eight out of 10

I would rate AWS a ten out of ten.

I would rate Amazon AWS seven out of 10. We're really satisfied.

I would recommend this solution to others because I am not familiar with Azure and only have experience with AWS. We don't have any issues with this product. I would rate Amazon AWS a ten out of ten.

A lot of organizations are moving from on-premise solutions to the cloud. There are a lot of case studies already in the marketplace which you can go there and find case study solutions to your business requirements. I would recommend this solution to others. I rate Amazon AWS a nine out of ten.

I would recommend this solution to others. I rate Amazon AWS an eight out of ten.

There are 50 users making use of the solution in our organization. I would recommend the solution to others. I rate Amazon AWS as an eight out of ten.

I rate Amazon AWS nine out of 10. I would definitely recommend it to others.

I rate Amazon AWS eight out of 10.

I would recommend this solution to others. I rate Amazon AWS an eight out of ten.

My advice would be to do some homework, read as much as you can about the setup before you dive in. If you take an hour to review the setup and then put together your own process so you know all the steps required and you use a checklist, it simplifies things. Have some kind of system, whether it's a spreadsheet or a Confluence page where you're documenting the steps and keeping track of where you're at. Whenever I'm asked to do something, I can find a tool on AWS that I can vet for our customers, and for that reason, I rate Amazon AWS 10 out of 10.

As a cloud-based solution, we're always using the latest version. I'd rate the solution at an eight out of ten. I'm pretty happy with the stuff you can do with it, however, I would like it to be more secure. I would recommend the solution to other users and organizations.

Considering the product, support, service, and maturity, I would rate Amazon AWS an eight out of 10.

I would recommend this solution to new users. On a scale from one to ten, I would give Amazon AWS a nine.

I would recommend this solution to potential users. On a scale from one to ten, I would give Amazon AWS an eight.

AWS is definitely best of breed. All three major cloud providers are very close though. 

So you really need to assess the features, costs, geographical availability, of each cloud provider and see which one suits your needs best. There are subtle differences in each so users should be aware. You should have a good DevOps leader who has the experience to evaluate your needs and suggest the best cloud provider. 

Best of luck. 

I would recommend this solution to others who are interested in it. I would rate Amazon AWS a nine out of ten.

When it comes to cloud management, I have no complaints at present. I am a customer of Amazon. As we are, basically, only hosting cloud services, this is geared towards the end user. We manage two or three people. I would recommend the solution to others. Owing to the pricing, I rate Amazon AWS as a nine out of ten.

Empower your in-house people to start building and running their workloads in AWS. Let them learn as they go. There are multiple online courses for a few dollars that can assist with specific, individual AWS services, as well as running through the AWS workshops. Incentivize AWS certifications. Involve your tech people with business solution prototyping. Tag your resources, name them well, and set budget thresholds. Assign people to tune the resources being used. Incentivize communications and publish the AWS services and features being used to deliver your business capabilities.

I would advise potential users to use Azure if they want more stability, but I always warn about the costs. That's why I don't bring infrastructure to the business, and I find the customers with their own environment. There are multiple portions, and it's not straightforward for anybody to do. That's the bad side of it, but anybody can prepare. On a scale from one to ten, I would give Amazon AWS a seven.

I'm a customer and an end-user. I'd rate the solution at a nine out of ten. We have been quite happy with the solution and its capabilities. I would recommend it to other users and other organizations.

We are just customers and end-users. We don't have a business relationship with Amazon. I'm not sure which version of the solution we're using. I'd recommend the solution. It's a good choice and one we stand behind. I'd rate the solution at an eight out of ten. We are very satisfied with the product so far. Likely, if the price was lower, we would rate it higher.

It is important for people who want to use Amazon AWS to have a very good implementation strategy to make the migration. Amazon has provided some framework to help those wanting to start the migration process. I rate Amazon AWS an eight out of ten.

I think at the cloud maturity level, I would rate AWS first, Azure second and GCP has just started. In 2015/16, AWS had a lot of issues, but now they are coming up with better solutions and better flexibility. That said, the transparency issue is still there. Azure is good for the Microsoft product line and if you are using that you should go with Azure - they will give you better service. But for third parties, it's the same transparency issue, just like any other cloud provider. I rate this solution an eight out of 10.

We are an implementor. I'd rate the solution at an eight out of ten. We've mostly been pleased with the solution's capabilities.

As a cloud service, we are always on the latest version of the product. I'd rate the solution at a nine out of ten based on the feedback I've gotten from my team. I'd recommend this service for particular use cases. However, it is important that users understand how it works. For example, it's not like you buy a server and running in a data center.

I'm a reseller. As a cloud-based solution, we're always on the latest version. We don't have to manually update it. I'd rate the solution at a ten out of ten. Even compared to other solutions, such as Oracle and Azure, it is much better. I've been a specialist for AWS for installation, however, I recommend solutions based on the company's requirements. However, it will help them in many ways.

We are using the latest version of the solution. I'm not sure of the version number off-hand. I'd rate the solution at a nine out of ten. We're very happy with its capabilities. I'd recommend the solution to other users and companies.

I feel the solution has been working very well. We have worked with around eight companies over the past year involving a variety of solutions. For some of these we implemented solutions that will be utilized by a large clientele. My role is that of an integrator. Editors and designers are other roles. As of now, we do not have a partner relationship with Amazon. I rate Amazon AWS as a nine out of ten.

Definitely, I would recommend this solution to others. I would rate Amazon AWS a nine out of ten.

As a cloud-based solution, we're using the latest version at all times. It's consistently updated. I'd rate the solution at an eight out of ten. I would 100% recommend this product to other users and companies.

We advise people to go on AWS. We also do a readiness assessment for our customers. We do a kind of a TCO analysis for our customers, and depending on the use case, workload, and pricing model, we advise our customers. We do it for AWS, Azure, and GCP. I would expect customers to do the same thing. They should do a proper analysis because it depends on what workloads they want to move to the cloud. Based on that, they should select a hyperscaler. I would rate Amazon AWS an eight out of 10.

I've worked as a consultant. We've been quite pleased with its capabilities. I'd rate it at a nine out of ten. I'd recommend the product to other users or companies.

On a scale of one to ten I would rate Amazon AWS a nine. To bring that up a bit, as I mentioned, I would like to have a direct connection to the EC2 server console. That's why I'm just not giving a 10. For anyone interested in using Amazon AWS, I would advise them to read the online documentation. It's very clear and shows you step by step how to use the system. If you need more advanced features, you can find a lot of resources on the internet and on their website. So if you want to use a public cloud, I strongly advise using AWS.

Amazon AWS is the most powerful tool and is at the top for cloud and for virtualization. It has many features and products. It is wonderful and I keep learning from them. I would highly recommend this solution to others. I rate Amazon AWS a ten out of ten.

On a scale from one to ten, I would rate Amazon AWS at eight.

We are using different services. We are using Alexa, for example, and static hosting. We do have a corporate account, however, we're not using a lot of services on it. I'm not sure which version of the solution we are using. We don't have a dedicated private cloud and therefore use a public cloud. I'd recommend the solution to others. Overall, we enjoy using it. I'd rate the solution at a seven out of ten.

I would rate Amazon AWS a seven out of ten.

On a scale from one to ten, I would give Amazon AWS a nine.

We're a software development group building specialty LAN/WAN optimization solutions, so we don't use a lot of canned products per se. We do tend to sue reasonably new software versions of the OS...whatever is the latest LTS selections. If you already have your workload ready, that's helpful, as you can actually trial it under a free tier and then see what the cost is, and extrapolate what the ongoing cost is. In the end, that's what gets you. Being able to do some benchmark testing on how much it's going to cost for your particular workflow across the three public clouds is definitely something you probably want to do. Especially if you're going to scale, as, obviously, it can suddenly creep up to not just tens or hundreds of dollars a month, but thousands a month, depending upon what you're doing. I definitely would recommend doing some reference testing of your workflows before deciding on a solution. I'd rate the solution at an eight out of ten. They're pretty solid. You've got all the services that you can imagine, and then some. There's a very broad breadth of products and services. We haven't had too many SLA issues for recovery or downtime. Maybe we've just been lucky or good so far...

We are a customer and an end-user. We don't have a business relationship with Amazon. Overall, I would rate the solution at a nine out of ten overall. We've been very, very happy with the capabilities we've been able to experience so far.

I rate this solution an eight out of 10.

I would recommend this solution to others. I rate Amazon AWS a nine out of ten.

It is a good solution. I would rate Amazon AWS an eight out of ten.

My advice to others is EC2 has its specific use case needs like other solutions, such as Lamda. If you have the need for a specific use case this solution could be the right choice. For example, it is possible to have your monolithic application on the cloud and decompose it into your microservice architecture or use it with Lambda capabilities. You can do this and have a high percentage of your application on the cloud. However, you need to be sure it is the right choice, it is something you need to be careful of. I would recommend this solution to others. I rate Amazon AWS a seven out of ten.

I rate Amazon AWS as a nine out of ten.

On a scale from one to ten, I would rate Amazon AWS at nine.

I would definitely recommend this solution. I rate this product a nine out of 10.

The type of deployment of the solution depends on the need of the organization. There are some solutions that we deploy for the clients that we need in a more stable environment. In this case, we use the cloud. For testing purposes for internal projects, we use our own servers within the company. I think by the IP numbers, we can request to create a certain server and they created this for us. There are some clients that require a cloud-based solution, we have this capability but it is still in testing and it is not what we use our servers for. I would recommend this solution for companies like small companies just starting out. It would be really helpful for them. I rate Amazon AWS a nine out of ten.

We are an enterprise with thousands of applications. We have really a broad mix of infrastructure. We have a technology standard list of several thousand products. We use a lot of AWS services. We're a customer and an end-user. As a cloud-based solution, we're always using the latest version. I'd rate the solution at a nine out of ten. We've been very happy with it overall. I would recommend the product to other users and companies.

This is definitely a product that I recommend. I would rate this solution a nine out of ten.

I would recommend this solution to others. I rate Amazon AWS a seven out of ten.

We plan to continue using this solution, and I would definitely recommend this solution to others who are interested in using it. I would rate Amazon AWS an eight out of ten.

I rate this solution a nine out of 10.

I would recommend this cloud solution to new customers. On a scale from one to ten, I would give Amazon AWS an eight.

We are consultants. We are using the latest version of the solution. I cannot recall the exact version number at this time. I'd rate the solution at a nine out of ten. We've enjoyed its capabilities so far. I would recommend this solution to other companies and organizations. There's a lot of due diligence which happens before organizations choose cloud solutions and then, of course, it needs to fit into the scenario. There is a cost-benefit analysis that has to be performed. It's a good idea to compare it to other platforms as well. Companies need to make sure it factors in the strategic landscape and the tools and technologies that the organization already has. If clients need assistance, we do participate in those strategic initiatives.

I would rate Amazon AWS a nine out of ten.

I would advise others to use the platform. I would rate Amazon AWS an eight out of ten.

I would advise others to do a test before going ahead and buying it. They should look at other cloud options as well. If you are going to use mostly Microsoft products, then go with Azure. For non-Microsoft products, go with AWS. I would rate Amazon AWS an eight out of ten.

As a customer, I would wholeheartedly recommend this solution to others. From our use cases and standards, most of the things are pretty much covered, so we're happy. I've been pretty happy with my experience with AWS. I would rate Amazon AWS a solid nine out of ten.

I would recommend this solution to others. I would rate Amazon AWS an eight out of ten.

I would recommend this solution. I would rate Amazon AWS a ten out of ten.

I recommend this solution to others and I plan to use the solution in the future. I rate Amazon AWS a ten out of ten.

I would rate Amazon AWS an eight out of ten.

I would recommend this solution to others who are interested in using it. I would rate Amazon AWS a nine out of ten.