Amazon EBS (Elastic Block Store) Reviews

When it comes to development environments, we have some applications that we deploy from those volumes. Sometimes, we use them for backups mainly due to limitations.  

So there are some clients who listen to set up that kind of structure in one availability zone.  

One of the examples I can use is what we have in our department, which we deploy in EDS. But this one, already far, when it comes to workload, if you have those clusters in high volume or workload, we tend to use provision ISPs. But we use those that are regularly accessed for general purposes.

The most important feature is the volume types in those hundred EDS. For example, if you need a volume with high IOPS, you should choose an io2 or io2 Block Express volume type. The default volume type for EBS is GP3, which is a good balance of performance and price for most workloads.

It is hard to access EBS volumes in different Availability Zones (AZs) because most EBS volumes are created in a single AZ. This can be a problem for workloads that require high availability or performance.

I would recommend that Amazon improve the accessibility of EBS volumes across AZs. This could be done by making it easier to create EBS volumes in multiple AZs or by providing a way to automatically replicate EBS volumes across AZs.

Currently, if you want to get the ability to access EBS volumes in different AZs, you need to use a different service.

I have been using this solution for two years. The companies I've worked for have used EBS volumes internally. However, they have since reduced the number of EBS volumes they use. They now mainly use Amazon Simple Storage Service (S3) buckets for their storage needs.

The exact version of EBS depends on the client, but it varies. Some prefer at least, while others depend on the client's requirements. Some engineers choose not to use a general purpose. Some clients request us to come up with a comprehensive policy where they can be changed automatically or replaced performance-wise, and when it comes to the high-performance aspects.

I would rate the stability a nine out of ten. The stability of the solution is good. 

Scalability is good. I would rate the scalability an eight out of ten. 

Sometimes the support is a little bit complicated. When it comes to support, since you can access it via one AZ, it gives you a lot of tasks to handle. 

Neutral

The setup is straightforward when it comes to the cloud. It's not so hard at all.

You just need to do as long as you know how to mark them and how to create snapshots to help the other vendors be able to access that particular EBS volume.

There is an ROI. 

The price is okay and fair. Especially if you go for general purpose because it requires low latency accessibility.

I would suggest that if a new company is not very busy, particularly if it's in the setup phase, it's okay to opt for something like EBS. This is because it is a cost-effective solution. You might not need to rush into overly complicated solutions, especially for additional storage. Therefore, if you have a limited budget, and especially if you're aiming to acquire the essentials, it's better to consider EBS. This holds true for me, especially if I'm making a recommendation.

Overall, I would rate it a nine out of ten. 

In my company, we use Amazon EBS whenever there are cases involving our servers having low space or there is some migration of servers required. We also deal with Amazon EFS often, but now we have an NFS tool for support. I use EFS very less since NFS is already present in the current products we deal now.

I provide updates from Amazon to my clients. If a client has Ubuntu Server that has EBS, and if the storage has less space, I directly connect my AWS account to add and increase the storage capacity of my client's servers, resolving the client's problems.

Every company is required to have its own servers, which means that every server requires storage. The need for storage depends on two kinds of storage, including Amazon EBS, which is a primary kind of storage. The file server or file systems and managing the objects inside require Amazon EBS as it is an important tool for day-to-day operations.

The most valuable feature of the solution is backup. If we deal with a gaming company client, then such a company requires a high IO throughput, which will give them only Amazon EBS instead of storage, including NAS, NFS, and similar tools. Since Amazon EBS is a good product, we deal with highly critical and hospitality-oriented tools, like RDBMS, for high-end data fetching from customers with high throughput.

Amazon EBS is a single product or service. 

I have a couple of issues related to Amazon EBS from the clients regarding the use of space, which have not been resolved. If a customer increases from one TB to two TB and wants to go back to needing one TB instead of two TB, then there is a long process involved to do so currently, even though going from one TB to two TB was very easy. Returning back to one TB from two TB or reducing the space is a problem in Amazon EBS, like S3. S3 is a scalable tool, meaning that you can increase or decrease its size. In Amazon EBS, it is difficult to reduce the space chosen by the customer. The cost increases the moment the size of the storage increases, and I will have to pay for two TB of the tool instead of one TB. If my clients want to change something in the tool, they need to get approval from their company, making it a long process. It would be better if Amazon EBS had the same features as S3 since we could easily revert back to one TB from two TB easily, which is not possible right now.

If I place Amazon EBS in South Asia, there will be an increase and decrease in terms of costs. Cost optimization is one challenge I have faced since placing Amazon EBS is the reason why basic costing is applicable. S3 is very cheap compared to Amazon EBS, and because of this, some clients request S3 and not Amazon EBS.

Depending on the requirements of my clients, I may want extra features in the product's future releases. Scalability is very important for our company since the tool's availability is already there. Most often, we use the product's scalability feature apart from the security feature. Amazon KMS, along with CRM, is a feature we deal with in our company, areas where we face issues due to low latency. If I want access to data in ESB, then it is dependent on the encryption method which I allocate in Amazon EBS.

I have experience with Amazon EBS for more than seven years. I am a customer of the solution who works in the service area of helping my company's customers deal with the issues arising from the use of the solution. I am a service provider involved in research and development activities for automation. I get direct service from Amazon for the version of the tool I use.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a seven out of ten.

As of now, I deal with three customers, and those three customers are different kinds of services for which they want to deploy Amazon EBS in their environments. My company caters to around nearly fifty endpoints.

My company's clients consist of one medium-sized business and two small businesses.

I can't give a full rating to the support since they are sometimes late to respond to my issues. I rate the technical support as an eight out of ten.

Positive

I have experience with storage services from AWS.

I rate the initial setup a nine on a scale of one to ten, where one is difficult, and ten is easy. The setup phase is very easy.

The solution is deployed on AWS cloud.

The time taken for the deployment depends on the size and the customers' requirements, so it can be deployed in less than an hour.

We implement everything as a backup recovery or DR tool. Sometimes, Amazon EBS is required, along with DR. When there are two branches and one of them says that the other has to work simultaneously are scenarios where the deployment can take time. It might take 24 hours to deploy the solution since the two replicas simultaneously work together.

Price is a big challenge for Amazon EBS. The price of the product is the reason why Azure is gaining popularity in the market.

On a scale of one to ten, where one is low price, and ten is high, I rate the price a seven.

The addition of networking solutions is an additional cost in Amazon EBS. If the process or storage capacity is increased in the product, the cost also increases.

Amazon EBS is a very good product since it is very easy to enhance or increase and migrate your servers immediately, in a matter of seconds. Sometimes, we require a critical server to take backups from images for which we use a snapshot. EBS is a kind of hardware for keeping a separate drive in our box. We can connect to Amazon EBS directly whenever required, after which we can simply clean up the server. Amazon EBS helps in different kinds of scenarios, like backup, storage increase, and migration of the servers, and such related support is offered in the solution's services.

Google has started offering some bundle kinds of products. If features offered by Kubernetes are made available in Amazon EBS, then it would be great. The bundle from Google can help if I want to implement a game product. In Amazon EBS, if a bundle similar to the one offered by Google is made available at a lesser price, then it would be good. Nowadays, there are instant requirements from our customers for which you can set up everything. Offering simple services in a bundle can be a good idea.

The product has been in the market for more than ten years, and to date, the customers are dependent on the solution.

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

We keep the data generated by the applications in the solution. We also store application logs. It is very easy to integrate the tool with the EC2 instance. I use the AWS console to integrate the products. Sometimes, I use CLI.

When the data is created, we save it in EBS. It's data-intensive, and sometimes, the data is very important. To avoid losing the data, we create a snapshot of the volumes every hour or once every two hours. We select volumes like gp2 and gp3 based on our requirements. EBS is customizable. We can select any volume depending on speed and size. The integration is very easy. We can mount EBS within seconds. We can also delete or unmount it.

It also provides API support. The durability and snapshot capabilities are good. The way they are designed is very good. We rarely find our EBS corrupted. It's very robust and easy to use. I never faced any issues with durability. The maximum size is 1000 GB. The solution is available whenever we need it.

The features could be improved.

I have been using the solution for five to seven years.

I rate the tool’s stability a ten out of ten.

I rate the tool’s scalability a ten out of ten.

We need to pay for support.

Negative

Integrating EBS into EC2 is very easy. Even people who are not from technical backgrounds can do it.

The solution is quite costly. There was an instance when we were not using 50 volumes. They were available and were costing us even though we were not using them. We ran a script to delete them. It's better to keep a watch on it and delete it whenever it is not needed. AWS has a pay-as-you-go model.

We have been using the solution since we have deployed our applications on AWS. If we track 100 GB of EBS volume, we know that the total data collected from the application will not cross 100 GB. Sometimes, we use Amazon S3 for object storage. If there is any transit data, we store it directly in S3. Our EBS volumes are free most of the time.

Logs mostly fill the EBS volumes quickly. We have an instance to monitor our Kubernetes cluster, and it fills the EBS volume very quickly. So, we have written a script to delete the older logs. I will recommend the solution to others. Anyone using EC2 must use EBS by default. It's very easy to use and integrate. Overall, I rate the solution a ten out of ten.

I primarily use Amazon EBS (Elastic Block Store) to host our cloud infrastructure on AWS. Currently, I'm using a disaster recovery solution, DRS, as the main stack. Additionally, I utilize several services inside AWS, such as EC2 instances, which are like virtual machines, and S3 buckets for storage.

Amazon EBS scalability allows for resource optimization and efficient infrastructure management, significantly impacting both our operations and those of our customers.

Amazon EBS is valuable because it allows you to store data permanently. It enables detachment from one virtual machine and reattachment to another EC2 instance. 

This feature ensures data portability, even if an EC2 instance is terminated since the EBS volume retains the same data and can be attached to a new instance. Additionally, it's scalable and allows for resizing, providing durability and high performance.

One area for improvement is the ease of scaling down the EBS volume. Having more flexibility in resizing, especially scaling down, would be beneficial. Automating the process of attaching a new volume to an existing EC2 instance would also be a valuable enhancement.

I have been using Amazon EBS for two to three years since I started my career in cloud computing.

I have not experienced any stability issues with EBS. It has been reliable so far.

Amazon EBS is highly scalable, allowing easy expansion of resources. It is straightforward to scale up, though more complex to scale down due to the need to migrate data to a new volume.

I have not had to escalate any issues to EBS technical support.

Positive

I have not worked with competitor solutions and have primarily been using AWS.

The initial setup process is quite straightforward, albeit slightly challenging, when adding a new EBS to an existing EC2 instance.

Amazon EBS offers measurable benefits such as increased capacity, scalability, and durability. It enhances infrastructure performance and ensures permanent data storage.

Pricing is reasonable if storage is utilized and optimized efficiently.

I haven't used solutions from competitors like Azure, Google, or Oracle.

I recommend not overutilizing or underutilizing your EBS storage. It's best to use what you need while leaving some room for backup. Additionally, new types of EBS volumes should be utilized for high performance and lower costs.

I'd rate the solution eight out of ten.

Amazon EBS (Elastic Block Store) is the hard disc for an EC2 machine. The EC2 machine is a server and needs hard disc space like a computer, and Amazon EBS is the storage for the EC2 machine.

The most valuable feature of Amazon EBS (Elastic Block Store) is its scalability. When you create an EC2 machine, you have to provision the amount of EBS. When you are out of space, you can increase the size of the EBS. Amazon EBS is not automatically scalable, but we have to scale it.

It is not very easy to increase the size. You can give a request to increase the size, and the size will be increased. But to actually make the EC2 machine see the newly increased size is a little difficult. You have to log in to the EC2 machine, do some commands over the terminal, and only then only it would be able to see the newly increased EBS storage.

It would be good if the solution added a button to increase the size and make the EC2 machine recognize the increased capacity of the EBS.

Amazon EBS is a very stable product.

Amazon EBS is a scalable solution. Only two people are using Amazon EBS in our organization.

The solution’s initial setup is very easy.

We use Amazon EBS (Elastic Block Store) on-cloud. Users can use the solution but should search a little about the kind of EBS services they offer. They should also know the difference between SSD and HDD. If you want to increase the space later, you can learn about it then. You don't have to know it beforehand.

Overall, I rate Amazon EBS (Elastic Block Store) a nine out of ten.

In our company, almost every department is looking for specific features for the whole project. Right now, I have almost two years of major experience with AWS for the deployment side of our projects. Basically, my individual experience is almost two years for deployment in AWS' features. In our company, all of our departments deal with the tool's deployment module for the projects.

As there are some sorts of firewalls handling the load balancing part, we need to deal with Elasticsearch Loader for our individual deployment. We may specifically have to deal with multiple EC2 instances, and we may also need to integrate with these features, but specifically, this is the way the microservices work. We are dealing with some monolithic architecture for which we need to use Amazon EBS (Elastic Block Store).

The most valuable feature of the solution stems from the fact that during the deployment, the tool indirectly provides our company with resources for our core side and cloud-based resources.

One of the major issues in the tool arises whenever it handles a large amount of traffic in the system, making it an area where improvements are required.

I have two years of experience with Amazon EBS (Elastic Block Store). I am just a customer of the tool.

Stability-wise, I rate the solution an eight out of ten.

Regarding scalability, Amazon is pretty good at providing upgrades in solutions, and I think from Amazon's side, the features are enough for projects.

I rate the technical support an eight out of ten.

Positive

If one is easy and ten is difficult to install, I rate the tool a two out of ten.

The solution can be deployed in a couple of hours.

On a scale of one to ten, if one point is a cheap solution and ten points is very expensive, I rate the product price an eight.

Everything depends on our company's maintenance engineers, who work on it and utilize Amazon's architecture.

From the AI features that the tool provides, we have used translators. Right now, the tool is offering chatbots that are really helpful. Regarding the AI perspective, there are a lot of other third parties that are providing good features. Mostly, what my company does is that we develop custom models for our client side. There were a couple of AI models that third parties were giving out, and they were the best solutions on which we were totally dependent.

I rate the tool a seven out of ten.

We use EBS Elastic Block Store for data storage.

EBS can handle Apex, which helps us manage many issues. EBS is easy to use and has high performance.

There are limitations in sharing resources across multiple regions and availability zones. I recommend improving EBS by introducing multi-availability zone support to enhance its functionality. 

I have been using EBS Elastic Block Store for one year.

I rate its stability an eight out of ten.

I rate its scalability an eight out of ten.

We've used Google Cloud Storage in addition to Amazon EBS.

The initial setup is straightforward. The deployment takes around five seconds. I would rate it a nine out of ten. 

In terms of ROI, using Amazon EBS has helped save time and resources due to its ease of use and scalability.

I find the price reasonable for our environment. 

My advice for those considering Amazon EBS is to ensure proper configuration for optimal performance.

Overall, I would rate Amazon EBS an eight out of ten.

I am using Amazon EBS as a storage service.

The most valuable features of Amazon EBS are the ease of mounting any file system and good for block storage. We can use secondary storage for our difficult instances and it performs well.

Amazon EBS performs well but it could improve.

I have been using Amazon EBS (Elastic Block Store) for approximately one year.

The stability of Amazon EBS is good.

Amazon EBS can scale up and down well.

I have not used the support from Amazon EBS.

I would recommend this solution to others, it is easy to use.

I rate Amazon EBS an eight out of ten.