The primary use case of this solution is to migrate our customers into the cloud, integrating all of their applications.
In my previous organization, we moved some customers from on-premises to the cloud, and they are happy with the change.
The primary use case of this solution is to migrate our customers into the cloud, integrating all of their applications.
In my previous organization, we moved some customers from on-premises to the cloud, and they are happy with the change.
The most valuable feature is that it is simple. We don't use complex services for our small business customers.
When it was only Amazon AWS in the market, no one was concerned about the pricing. However, now that there are so many competitors, there is more comparison for cloud service providers. They should look into reducing the price of this solution to stay competitive. It would be a benefit.
The current trend is multi-cloud. They can launch the Oracle service in Azure, and we expect that this should be possible in Amazon AWS as well.
I would like to see better integration between Oracle and AWS.
I have been using Amazon AWS for two years.
Amazon AWS is stable and we have not faced any issues.
It's a scalable solution.
We have not used technical support. We provide that to our customers.
The initial setup is easy.
Deployment is not a problem for us because we have experience. For new people, they are a bit worried about new features, until they develop a routine.
The Oracle licensing is higher than it is with Amazon AWS.
The deployment varies, as some of our customers would like the hybrid cloud while others want a public cloud.
I have recommended this product to our customers and will continue to do so.
I would rate this solution an eight out of ten.
We like the that, within the public subnet of this solution, a new instance of the tool is launched when it detects an issue, in order to prevent interruptions in performance.
We would like the system documentation for configuring this solution to be improved, in order to provide better process clarity.
Similarly, we would like more templates to be available to download for performance-oriented architecture, so that we can re-purpose them for our environment.
We have been working with this solution for the last five years.
We have found this to be a stable solution.
This solution allows for easy auto-scaling.
The initial setup for this solution is straightforward.
I would rate this solution a nine out of ten.
The customer can deploy their application on Amazon AWS instead of taking care of their infrastructure.
The most valuable features of Amazon AWS are ease of use, deployment, and short lead time. If you are using an on-premise solution, you need to wait for the hardware, and nowadays it is very difficult, the lead time becomes very long. We propose to our customers to use Amazon AWS because it is very easy, no need to wait for hardware delivery.
If Amazon AWS can offer more self-paced learning tools, on their website, on CBT, it'll be easier for more people to familiarize themselves with their service. Especially when they are delivering new services from time to time. Educational tools that can help users familiarize themselves with their service. It would be great.
I know they have a Free Tier service, but they need to register their credit cards. Some of my colleagues have concerns. If the usage exceeds a certain value, they exceeded the Free Tier usage time and they will start charging your credit card. My colleagues forgot about the usage and credit card payments. They needed to pay for the additional amounts which they used on top of the Free Tier usage. If Amazon AWS could improve the free service model to be more user-friendly in a way of not using a credit card, that would be great.
For personal learning, you also need to register your credit card. You need to be careful or you will have to pay.
I have been using Amazon AWS for approximately two years.
Amazon AWS is stable. However, they have had a few outages but nothing very serious.
Amazon AWS is quite scalable. And they have a lot of auto-scaling functions for their VMs.
I don't have direct information of the support from Amazon AWS because sometimes we are relying on Amazon's partner, not directly contacting Amazon AWS support teams. We need to have some support plan with Amazon AWS, otherwise, they will not provide direct email or technical support.
The length of time and difficulty of the implementation depends on the scale and the complexity of the project.
For the implementation of Amazon AWS, having two to three engineers focusing on it would be ideal. Small to middle size companies, don't have dedicated teams or engineers for a particular service.
Amazon AWS is offering different pricing, and saving plans, it's very easy for a customer to consider the Amazon AWS service.
Amazon AWS charges based on the user usage and some software license, such as the OS are included in their monthly charge. The transparency is quite sufficient, the customer knows what they're paying for.
The usage fees are an OPEX and they are offered monthly or annually.
I have evaluated Microsoft Azure and Google Cloud.
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.
I am using it for enterprise warehousing. I am using it for web development, data warehousing, and also for building apps.
I am using its latest version. In terms of deployment, it is a platform as a service.
Macie is great. It is a service that makes recommendations on a data layer for cybersecurity. It is a great service.
Its elasticity is good, and I haven't come across any problems with it. So far, everything has been good.
One thing that Azure offers that I think is good is Migrate appliance. So, Azure has a migrate appliance that allows you to run against workloads to determine the cost, preparedness, and scalability. I haven't found a similar feature in AWS. That kind of service would be great on AWS too if you could point it to the data center.
I have been using this solution for well over five years.
I have not had any performance issues.
It's very easy to scale. Its elasticity is good. If you want to scale up or down, you can. You can scale out. There is no problem at all. That's one of the features that I like about it.
We have less than 50 people who are using this solution.
I've not used their tech support yet.
We didn't use a different solution previously. They're the first.
You need to know what you're doing. I know they're trying to make it easy. Some things are easy. Some things you have to know what you're doing.
It seems to be reasonable. It's the first one that I've used as a cloud platform, so they've set the benchmark for me, and now, I'm comparing everything else to them.
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.
General use cases of AWS are for those needing a managed cloud instance without the bulk costs for a legacy server. We are customers of Amazon and I'm the technology manager.
The benefit to the company is immense financial savings and the fact that you're able to see your monthly costs before buying anything. The AWS monthly calculator enables you to select your database, servers, volumes, and see how much everything will cost on a monthly basis. You can figure out what you'll be paying, so it enables a comparison; it's usually a third to half the cost of using an on-prem system.
Amazon is easy to upgrade, easy to expand storage and change your EC2 types. Each of those things usually takes at most five minutes to do, whereas on a legacy system you have to actually buy a new system or new hardware and have downtime for installation. Even then it may not be configured the same way and you might end up with a widespread outage. The advantage of using AWS is that all the testing's been done so you have proof that it works. We still do a cursory check, but they don't put anything out there that hasn't been vetted. Plus all the Atlassian tools are on AWS as well. The cloud instances they provide have a very robust network because there are over 160,000 companies that use the tools. Backups are really easy to access as are the automated backups of the VMs and the volumes. We're able to create a new volume from a backup in about two minutes, attach it to the server and view the data side by side to compare the old to the new. It takes 10 minutes total to get all the access needed.
I've had very positive experiences with AWS and it's gotten a lot better over time with their improved interfaces. Everything's all interconnected now and within its own framework. We pull in other tools to the OS such as Docker but AWS provides tools like Yum that enable quick installation of things. It's typically part of the OS.
While the IAM security key is very secure, they only give you one chance to capture your key. If I'm already logged in and have an email address online, it would be better if it were sent in an encrypted manner to email so that you don't lose the key. I might create the IAM and then perhaps forget to capture it off the screen and then when I do need it, I realize I don't have it and have to create another profile.
I've been using this solution for about 12 years.
I haven't had any problem with stability. We do multiple zone backups and multiple zone data and we haven't had any problems or slowdowns. We've had dealings with countries like India, where things are generally slower but with AWS there haven't been any issues. There's no wait time.
Scalability is good. I like the EFS expandable storage because it expands and contracts, you don't have to do anything with it and it's really inexpensive. Somebody may use it for temporary storage where they drop a terabyte of data that they need to give to a customer and then it shrinks back down when they're done with it. It expands and contracts as needed and that's also reflected in the cost.
The technical support is very fast, very efficient and very knowledgeable. Even when I've asked questions and they didn't know the answers, they were able to find someone within 15 minutes that was able to help.
The initial setup is pretty straightforward. The main thing is getting the security protocols set up in the proper order, otherwise it won't work. You have to go in and set up the main group and make sure to share it to your database. They've improved their documentation and it's a lot better but still lacks a little in some areas. If you've deployed before, setup takes a couple of hours, otherwise it might take up to a day. It's a lot faster on cloud; if you're working on-prem you have to jump through a lot of hoops because each team has its own security.
They have scripting tools on AWS which allow you to set up your framework and you can use it as a template. We use an AWS architect for implementation and to make sure all the security is set up. And then we have a DevOps team that manages the OS updates. That's a team of three handling over 100 servers, VMs basically. Once a month they do the non-production patching with the production patching the following week.
Licensing fees are only applicable if you're using Red Hat or an Oracle database. You have to pay for both of those. If you're using Postgres or MySQL, there are no costs for the actual database application. There are no fees for individuals using Oracle Java, but businesses pay a license. We use an OpenJDK that is vetted by Atlassian so if you don't want to buy Java you can use the OpenJDK.
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.
We use this solution in our company and for our clients' companies.
I like the IAM, the directory, and the storage.
They should implement the command shell by default. As it is now, to open the console, you have to download the command application. When you compare with GCP, they have the command shell inbuilt.
It would make it more seamless for the administrator to include this. There are times where the machine is not connecting and you can't wait for the RDP because you have to create them quickly.
Building a shell directly from the console is a good solution. This is missing by default. there are ways that it can be done and integrated.
I have been working with Amazon AWS for six years.
Amazon AWS is very stable.
It is a scalable solution, but you can only scale-out. You can't scale up.
We have approximately 200 users in our company who are using it.
Technical support could be improved, they could be better. We don't get SLA with AWS.
They give us a specific time for a solution but they don't advise further. We have to check to see if the issue has been resolved. There should be an automatic email to notify us that the issue has been resolved, by default.
The need to work on proactiveness.
I also work with GCP and with Azure.
The initial setup is easy. It is not complex.
We have a team of 50 people who maintain all of our solutions. It's spread across the team to run 24/7.
The pricing is one of the best in the segment.
They have actually reduced their prices, with the exception of the MLD which has increased.
It's by design itself.
They have placed the pricing well for a reduced market.
I would rate Amazon AWS a seven out of ten.
We use this solution predominately to reduce the amount of effort we need to migrate to the cloud.
We have had some difficulty figuring out how to monitor how many EC2 instances have been networked into our entire enterprise. We usually try to create a diagram outside of AWS. The types of information we are trying to determine are, for example, what hardware devices are interconnected, and when was the interconnection made.
It is difficult to extrapolate budgeting costs and schedules from the information gathered from the usage of the solution in our systems. We are given a large lump sum of money at the beginning of the year for our budget but it is hard to summarize costs to put down on paper for justification or projections.
I have been using this solution for approximately one year.
This solution is stable and reliable.
We are planning on moving more of our systems to the cloud. Currently, we have approximately 60% of our applications on the cloud.
Our developers found the installation a moderate level of difficulty, there was not anything that was complex. It is helpful to have some tutorials to follow.
The solution is on a pay-as-use pricing model. The price of the solution could always be better but it is priced competitively.
We have evaluated Lambda, and in some cases, it might be a better option than EC2. However, we have decided to go with EC2 because it is closer to a drop-in displacement which works better with our applications, for example, Spring Boot and other similar variations.
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.
The most valuable features of Amazon AWS are the EC2 instance for web applications with CDN Networks.
AWS Cloudfront is the official reference for the Global content delivery network (CDN) which significantly reduces latency or slow loading times.
There is a feature called Kinesis, which has to do with image processing. There are a few artificial intelligence tools that Amazon AWS should improve on.
I have been using Amazon AWS for approximately five years.
I have found Amazon AWS to be stable.
Amazon AWS is scalable.
The technical support has been challenging. I have found more tickets are being placed and the availability of the agents has been limited for some of the team members.
We selected Amazon AWS because it was the most mature at the time. It was the initial cloud provider. Then Google and Microsoft also came up with Azure and TensorFlow. TensorFlow is catching up with a few code web programming tools, and that is a point of interest as well as image processing.
In a future release, the solution could improve on the IoT integrations and API access.
The initial setup of Amazon AWS is complex due to how infrastructure is set up in different organizations.
For the initial 12 months, the solution is reasonably priced. On enterprise license contracts where you negotiate, have been reasonable too.
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.