Amazon EBS (Elastic Block Store) Reviews

I have worked on Amazon EBS for more than five years. Amazon EBS is primarily used with Amazon EC2, EKS, ECS, or any other service that includes compute resources. I use it for storage, and it acts like a hard drive for servers.

Amazon EBS offers diverse features. It can be used for multi-purpose storage, supporting single, multiple, or heavy loads. It has different types for various use cases, allowing me to choose based on my specific requirements. The primary advantage of Amazon EBS is affordability compared to other solutions like EFS or FSX. It acts as a hard drive for servers, making it essential for operation.

If Amazon could add the auto-scaling feature that exists in RDS to the EBS volumes for EC2 or EKS, it would be beneficial. This capability is currently missing and would greatly enhance scalability.

I have worked on Amazon EBS for more than five years.

Amazon EBS stability depends on the server. If the server is stable, then EBS is stable. EBS itself can't be down if the server is running.

Amazon EBS is scalable, but not auto-scaling. I have to manually scale it, especially in Windows instances, which requires downtime. In Linux instances, there is less downtime. EBS does not automatically increase memory without disturbing in certain cases, like RDS where auto-scaling is supported.

Some of my customers have used EBS support, and they told me it's good and really effective.

Positive

The initial setup of Amazon EBS is ten out of ten. Whenever I create any type of instance, like EC2 or EBS, I need to create an EBS volume with the same setup process.

In some EBS types, costs are slightly higher compared to other cloud platforms. The cost can vary greatly depending on the use case, ranging from one dollar to over $1200 dollars per month. Discounts or bundle propositions would be useful.

Some customers use solutions like EFS or FSX, however, they find Amazon EBS cheaper.

Everyone using services like EC2, EKS, ECS, or RDS with compute resources must use EBS. It's essential to understand the scenario and select the right EBS type according to your needs. 

Overall, I would rate Amazon EBS ten out of ten. It's very effective and meets various use cases. 

I primarily use Amazon EBS to attach and launch an instance. However, I do not use it to store a lot of data. My main usage is to launch instances.

Amazon EBS helps my organization by acting as a hard disk in the cloud. I see a lot of benefits because it allows for flexibility. If I need to store something, I can, and if I no longer need to, I can delete the EBS without incurring further costs.

One valuable feature of Amazon EBS is that I can put something on an EBS, attach it to an instance, and preserve EBS without needing an instance. For example, I don't need to delete or remove everything from an EBS when terminating an instance. This is beneficial for my usage. 

Another feature is that each EBS can attach only one instance, and this isolates the usage effectively. EBS is a very crucial tool as it acts like a hard disk on cloud, providing cost savings compared to physical hard disks, and only incurring costs based on actual usage.

I see a need for improvement in the scalability of Amazon EBS. If I need something more scalable, I rely on another storage solution like S3. I also think the pricing of EBS is high. It's very expensive to store a lot of data.

I have been using Amazon EBS for more or less two and a half years.

Amazon EBS is quite stable. I rate the stability as eight out of ten, and I have never had problems with its stability.

I don't see good scalability with EBS, as it is attached to an instance. If I need scalability, I use other tools, like S3. I would appreciate better scalability options in future versions.

The technical support for Amazon EBS is rated at eight out of ten. Recently, I needed help migrating data from DynamoDB to MongoDB Atlas, and AWS support was helpful in configuring a private link.

Positive

Before using Amazon EBS, I have used Amazon S3 and sometimes Amazon EFS. The choice depends on the use case. For instance, team access storage is better managed with EFS.

The initial setup was easy, rated as a ten out of ten. I faced no challenges or issues; the setup was smooth.

I carried out the implementation myself. Only one person is required for this, and there's no need for a specific maintenance team.

Using Amazon EBS provides clear returns on investment. As a cloud storage option, it is flexible and cost-effective, eliminating the need for a permanent investment in hard disks.

The cost of Amazon EBS storage is high. I rate the price as eight out of ten. It is expensive to store a lot yet provides significant cost-efficiency as I pay only for the storage time required.

I have mainly evaluated AWS solutions. However, I know that other clients use Azure or Google Cloud Platform, but I primarily use AWS.

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

It is generally stable and effective, yet there is room for improvement, particularly in scalability.

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.

My use case involves wanting to use AWS EBS for storage purposes. For instance, if I want to create additional data, I have an instance with only ten GB, or 20 GB volume. I need more, like 50 GB, to run the current instance. So I went into EBS, added 50 GB of volume, and mounted this EBS to the current running instance, attaching the EBS volume to the running instances. These are my current use cases. is used to copy, save, or secure data.

Initially, I mentioned easily copying files and mounting one volume from one drive to another, or splitting the drive. For example, splitting a 30 GB volume into multiple five GB parts. I recommend doing this to others. This feature allows me to easily mount data, services, or drives anywhere in virtual services. Just specific features involve copying data without loss. Adding to this, EBS helps in cost-reduction and is beneficial for freelancers.

I want to add a firewall in the free tier, and there is a need for more services to reduce costs, especially if many people use it as freelancers. AWS services could improve by including services in the FreeTier, like Route 53 domains or SSL certificates. When we use certain applications, they incur high charges. If we add services in FreeTier, it could be beneficial. It's based on my company. Regarding EBS, if an instance is terminated, the volume is also deleted, which leads to data loss. This is why I copy files between volumes.

I have been using AWS EBS for the last two years.

I did not encounter any issues since I am using the free tier.

This solution is scalable based on the free tier instances. If we use the t2.micro, the volume should be free, however, for t2.medium or t2.large, there are charges. It may scale per hour or as per usage, such as an on-demand option, with charges based on use.

I do not want to ask any questions to technicians as the account is not important to me. However, I am using AWS services with another email. This account is important, and I do not use MFA for security, however, I have a fingerprint setup on my laptop. Currently, there are no questions for technicians.

Positive

Sometimes it takes a long time to run or stop instances. I also lost my previous AWS account using MFA. There is no proper guidance for MFA in AWS services or practical application. I lost my previous account due to complications with tokens while connecting my mobile device. AWS could make MFA easier. When using MFA, options include a token and device. If a device is connected to AWS, there isn't a need for codes. However, if the phone is switched off and on again, the previous MFA code changes. This issue persists even with AI models trying to troubleshoot it, which is why I lost my previous AWS account. I am now using a new one.

I think everything is great. The review sticks to the point with nice, direct answers. My overall rating for EBS is nine out of ten. 

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.

The primary use case for Amazon EBS is the attachment of virtual machines and file shares. I also use it for mounting EC2 machines with storage for EC2 instances, intending to use it for applications requiring high throughput or IOPS, big data analysis, log processing, data warehousing, EBS backup, or data recovery, and hosting file stores, such as NTFS and XFS.

I am using Amazon EBS mainly for the attachment of virtual machines and file shares. I find it valuable for applications requiring high throughput or IOPS and mention its stability and performance as significant factors. 

I use it for big data analysis, log processing, and data warehousing. Additionally, I use EBS for backup or data recovery and hosting file stores, such as NTFS and XFS.

The main challenge with Amazon EBS is cost management, as it is a high-performance volume. Sequencing and IOPS relative to cost are also areas of concern. 

Additionally, data durability can be an issue, with risks of accidental deletion or corruption.

I have three years of experience using Amazon EBS and S3.

The stability of Amazon EBS is characterized by its performance and scalability. It is designed to provide high throughput and low transaction costs.

Amazon EBS is scalable only vertically, meaning I can scale up yet not down.

I have experienced high costs as a primary issue with Amazon's support. I have raised a ticket regarding the high costs related to EBS technical support.

Positive

Last year, my company partnered with AWS, however, we currently have a partnership with Microsoft Azure.

The initial setup of Amazon EBS is easy, depending upon the requirement.

The main challenge with using Amazon EBS relates to cost management. Managing high performance and IOPS volumes can be costly.

Currently, my company is partnered with Microsoft Azure and we are using various Azure services.

I would recommend Amazon EBS to other people. I rate Amazon EBS a nine out of ten.

When clients need solutions, I use Amazon EBS for presenting the data to the servers. I use EBS for storing data of SQL and different data of the clients.

Amazon EBS stands out due to features like its configuration and IOPS, which can be beneficial for the servers in my organization. The scalability allowed by cloud solutions, such as auto-scaling and this storage capability, is an important feature of Amazon EBS. EBS is a cost-effective solution, where I pay as I go, making it a favorable option.

Amazon EBS could improve by offering immutability of the data. This feature is not certain, but it could be beneficial.

I have been using Amazon EBS for around one year. I am not entirely sure of the exact duration.

All cloud solutions permit scalability, and this is an important feature. The storage capabilities ensure stability and are significant for operations.

I have not had contact with Amazon's customer service, however, I have heard it's really good.

Neutral

The setup of Amazon EBS is easy. On a scale of one to ten, with ten being the easiest, I would give it an eight.

In my company, I have eight people working on cloud solutions, including AWS.

The ROI varies depending on the project, with a return ranging from 20% to 25%.

Amazon EBS is not expensive. It is equal in cost to other cloud storage solutions like Azure.

Amazon and Microsoft Azure are both solutions I have worked with. I predominantly use AWS in my work.

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

Positive

I primarily use Amazon EBS for my storage needs and for creating backups. It is highly compatible with other AWS services, which allows for easy data storage and retrieval.

I have utilized Amazon EBS in different ways, and it has worked very smoothly and perfectly. There have been no disruptions.

Amazon EBS offers features such as cloud migrations and different deployments, which are incredibly beneficial in moving data from on-premises to the cloud. The platform is stable and can be replicated across different availability zones and data centers.

There are no current recommendations for improvement. However, implementing more AI-based capabilities could enhance the service.

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

Amazon EBS is very stable. It replicates data across different availability zones and ensures data is reliably backed up and accessible.

Amazon EBS is easy to scale up or down as needed. I would rate its scalability as ten out of ten.

The AWS customer support is very cooperative, fast to reply, and solutions-oriented. They are highly recommended.

Positive

The initial setup of Amazon EBS was very easy. Even for beginners, the setup is seamless and easy to perform.

Amazon EBS is a cost-efficient solution. It is very cost-effective and offers great value.

I highly recommend Amazon EBS for enterprises and small businesses due to its cost efficiency and ease of use. 

I rate the overall solution ten out of ten.

I mainly use Amazon EBS for EC2 configuration. We use it for the EC2 purpose to store data and mount with the running EC2 instances. EBS is the backbone of the compute instances. It is not only a disk; it is the main support for running EC2 instances. Moreover, if you want to use the EBS volume in your EKS cluster, like a Kubernetes cluster, you have to use it.

In a traditional setup, if you want to add a disk to legacy systems, you need to purchase, find the hardware vendor, and insert it, which is a lengthy procedure. 

With Amazon EBS, if you want to add an additional disk to an EC2 instance, you can simply attach an EBS volume by clicking through a few options, and it's done.

There is room for improvement in AWS support. They have technically strong people. However, sometimes there is a lag in providing technical solutions to customers.

I have been using Amazon EBS since approximately 2019 or 2018.

Based on stability, I would rate EBS more than nine, possibly 9.5 out of ten.

For scalability, I would also rate it at 9.5 out of ten. It is amazing.

AWS support is good, but there is space for improvement. They follow the SLA, but the technical solution responses have room for enhancement.

Neutral

The initial setup of Amazon EBS is straightforward. Even if you want to add an additional disk after deployment, you can do it. If you wish to expand the volume, it is also possible.

Amazon EBS is the backbone of running instances, and most people are aware of using it. However, to cut costs, you must choose the right size when provisioning. 

Ensure your data's security by selecting the right encryption keys, AWS region, and availability zone to avoid duplicate work. Additionally, if your image is from the marketplace, read the instructions given by third-party vendors. If you use a global encryption key for EBS volume, ensure approval from your organization for global KMS key or EBS encryption key for your account.

I'd rate the solution nine out of ten.