Amazon EBS (Elastic Block Store) Reviews

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.

I have been using services like EC2 VPC. EC2 stands for Elastic Compute Cloud. It is mainly used to create virtual servers. EC2 has multiple components within it, including storage and compute power. I use these services in my projects and have personal usage for various projects.

One of the features I appreciate about EBS is its persistent storage nature. If EBS is attached to an EC2 instance, it allows secure document storage. EBS provides vertical scaling options to add additional volumes when more storage is required. These storage expansions are valuable for securely storing documents and managing storage needs efficiently.

There is a concept called Snapshot, which is a backup of the entire EBS volume, however, the cost is quite high. In EBS, standardizing storage can be expensive as there is no optimization option. Deployment is not easy as it requires server downtime to map newly created volumes, impacting operations during additional volume additions.

I have been using EBS for the past eight years in my projects.

I have encountered stability issues in specific regions, such as the US East one, causing data fluctuations and accessibility problems. At one point, data was not readable for a certain period, which was concerning. Although Amazon recovered the data, stability during such regional downtimes can be an issue.

The scalability of EBS is satisfactory. Vertical scaling can be achieved by adding additional volumes whenever the created storage is insufficient. This scalability feature is facilitated by EBS to accommodate evolving storage needs.

The support team is quite effective. I have reached out to Amazon support multiple times and have found them responsive. They provide instant and chat support, addressing concerns in a timely manner. However, chat support sometimes gets disconnected, which can be improved.

Positive

The cost of taking a backup called Snapshot is quite high, and EBS doesn't provide options for optimizing the standardized payment, leading to continuous charges. This cost structure could be considered a disadvantage.

If given an option, I would suggest going for S3 due to its distributed storage features. S3 allows remote access, which is advantageous compared to EBS's limited single server access. 

I rate EBS eight out of ten for its features and functionality.

Amazon EBS is used primarily for professional services. We deploy solutions like servers that come with EBS for storage. The server will run applications or databases where EBS serves as the storage for the server instance or database instance.

Amazon EBS provides fault tolerance and high availability for applications, making it easier for us to ensure that the applications are always available.

One of the features I find most valuable is that EBS can be independent. You can attach and detach it from your server. If a server goes down, you can save that EBS volume and attach it to another server for failover. Amazon EBS is also scalable and provides high availability.

I would like EBS to have no limitations, similar to stream-like block storage, which can accommodate an unlimited amount of sales. EBS has limitations that could be improved.

I have been working with Amazon EBS for about a year.

Amazon EBS is very stable. In the shared responsibility model of AWS, if a downtime occurs it is usually due to the customer's lack of security awareness. AWS provides infrastructure stability like data centers, ensuring high stability.

Amazon EBS is scalable and provides good fault tolerance and high availability.

The level of customer support from AWS depends on the support plan. Enterprise support provides access to AWS developers 24/7, whereas the basic plan offers limited access. The support level is generally satisfactory, depending on the plan chosen.

The initial setup is easy, rating it ten out of ten. When setting up an EC2 instance, there is a straightforward process to choose storage type and amount.

The pricing for EBS is related to the file size stored. The larger the storage, the more you pay. For SSD IOPS, you only pay $0.125 per gigabyte.

When planning to use AWS EBS, ensure that it is attached to a server, container, or dynamic function like a Lambda function. EBS is specifically for Elastic Block Storage and should be used with servers or dynamic processes.

I'd rate the solution ten out of ten.

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.

Amazon EBS is used as a block storage solution, particularly for high-performance computing, databases, data management, snapshots, and backups. It's especially beneficial for organizations needing consistent high-throughput performance, such as those handling large databases or analytics workloads.

Amazon EBS has significantly helped in cost savings and improving the overall performance of databases. It has allowed better data management, making the process easier and more efficient, and restored confidence in complete solutions.

The integration of Amazon EBS with EC2, S3, and Amazon Glacier is seamless and easy, creating a comprehensive cloud environment. The feature of encryption is particularly beneficial, providing a higher level of security. The solution is globally available and ensures high performance and reliability, which makes it valuable for organizations that require enhanced throughput and seamless data management capabilities.

There is a lack of awareness and knowledge about Amazon EBS among potential users, which results in underutilization. Additionally, there might be a lack of marketing highlighting the capabilities of EBS, which could improve its popularity and utilization.

I have been working with Amazon EBS for almost one and a half years.

On a longer-term basis, there are no stability issues with Amazon EBS. However, initially, there were minor connectivity issues, but they were resolved quickly and easily.

The scalability of Amazon EBS has positively impacted operations. It has helped database-heavy organizations improve performance and cost efficiency.

We did not require technical support from AWS for EBS.

Neutral

Amazon EBS provides significant time savings due to increased throughput and improves overall database performance.

The cost of Amazon EBS is slightly higher compared to other competitors, approximately five to ten percent higher. However, the benefits, including high performance and reliability, outweigh the costs, making it a cost-efficient option.

I do not have much experience with other block storage solutions outside of AWS.

For clients needing high database performance or involved heavily in analytics, Amazon EBS is highly recommended. However, for those not requiring high-performance database solutions or dealing with big data, it may not be necessary.

I would rate it a seven out of ten.

I use Amazon EC2 instances, AWS Lambda, API Gateway, and EBS for storing data. EBS is primarily associated with Amazon EC2 instances.

The main advantage is the ability to scale up and scale down easily without any downtime. Amazon EBS allows seamless changes to the instance type without affecting application availability. 

It also supports encryption by default for added security.

I do not have anything in mind for improvement at the moment.

I have been using Amazon EBS for around eight years.

Amazon EBS is stable and easy to use. Detaching and attaching volumes are very straightforward, contributing to the overall stability.

Amazon EBS provides effective scalability with the ability to modify volume size easily and have it reflect instantly.

Accessing technical support requires a paid subscription plan. Once subscribed, the support team is very responsive, connecting remotely to assist with troubleshooting.

Positive

Amazon EBS is priced based on usage, and it is fairly priced. Users are charged only for the data used, not for the allocated volume.

I recommend using EBS because of its flexibility with volumes. Instead of instance-based storage, EBS is more efficient.

I'd rate the solution eight 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.