Questions tagged with Amazon Elastic Block Store
Content language: English
Sort by most recent
instance keeps crashes in intervals after extending ebs volume
My EC2 instance keeps crashing (unreachable) after I extended the EBS volume. When I reboot the instance, it comes back up and then become inaccessible after 24-48 hours and the circle continues. Please help. I need it to stay up continuously like before
Can I reduce an over-sized EBS volume?
Amazon Linux 2 EC2 instance with an EBS GP2 boot volume that has one GPT partition and XFS file system: The EBS volume was extended from 1.5TB to 3TB. Turns out this is greater than necessary. The Linux partition and XFS file system were *NOT* extended to use the additional volume capacity; the partition and XFS file system are still 1.5TB. Can I reduce the EBS volume to, perhaps, 2TB without damaging the XFS file system? I am aware that I can replace the volume using a snapshot, etc. I'm looking to avoid that effort if possible.
Unable delete a volume - struck with deleting status
I created a EBS volume and attached with an instance. Partitioned, mounted, created files. Unmounted, detached, created snapshot and then tried to delete the volume. But unable to delete the volume and its struck with "Deleting" status. And also I terminated the instance as well. Only the volume is deletion is pending. How to delete this volume forcefully?
How to decrease size of a root volume EC2 Amazon Linux2?
I want to decrease the size of a root volume in an EC2 running Amazon Linux2. I have followed some posts from internet and a post from [here](https://repost.aws/questions/QUypl3Te6QSxGMbRRA6RuCPQ/how-to-decrease-size-of-boot-volume-on-m-5-instance-using-nv-me) but it does not work for Amazon Linux2.
Increasing EBS Volume disk size created a 3rd drive on Windows Disk Management
I have 2 EBS storage volumes attached to a Windows EC2 instance. The volumes were 40gb and 100gb. I increased the 100gb disk to 300 gb, and RDP'ed to the EC2 Windows box ran disk management to allocate the new space to the D drive, but this is what I found instead: https://pasteboard.co/swhXG4lEqQDA.png It shows a new drive W that isn't formatted, but has 200gb unallocated to it. Now if I look at the total amount of space available I'd have 40gb (C:/) + 100gb (D:/) + 300gb (W:/)= 440gb!? But in the AWS console I show only 340gb total between 2 EBS volumes. Which brings up the issue that if I format the disk I might be overwriting data because there isn't 440gb allocated. I've tried rebooting the box without success it still shows this extra drive. And I can't find any information about this situation or how to fix it.
EBS IOPS, Throughput and EBS bandwidth
we need to deploy ec2 with following EBS configuration- random 4k write : 2,00,000 IOPS sequential read-2000Mb/s sequential write-2000Mb/s this is database server requirement. 1. I have some confusion if I select **io2** EBS type with 200000 provision IOPS let say for 24 hours and after that I have modified EBS type to GP3 do AWS charge me for full month or only for 24 hours? if AWS would accrued 24 hours charge what would be charges? 2. what ec2 type I should go for any suggestions? Or am I making any mistake in selecting EBS type please guide me.
Snapshots of encrypted EBS volumes
We know that the first snapshot of an EBS volume is a full copy and the next snapshots are incremental i.e. only the blocks that have been changed since the last snapshot are copied to S3. I want to know if this is true for **encrypted volumes** as well. Are the subsequent snapshots of an **encrypted EBS volume** full or incremental?