Questions tagged with Amazon Elastic Block Store
Content language: English
Sort by most recent
cloudformation to create ec2 using volume attachment for root.
Hello I am trying to create one EC2 using cloudformation. The requirement is to use volume attachment with a snapshot id. This snapshot id is coming from my AMI and the snapshot id provided is the root device. (AMI only consist of one snapshot) I got the error message: Property ImageId cannot be empty when deploying the resource. When I input the ImageId for AWS::EC2::Instance, it will crash with AWS::EC2::VolumeAttachment property. Can someone help to modify my template and point out how can I fix this issue? ``` --- Description: "AWS CloudFormation sample template. Create a new EC2 instance" Resources: myEC2Instance: Properties: IamInstanceProfile: ec2role InstanceType: t2.micro SecurityGroupIds: - sg-123456 SubnetId: subnet-123456 Tags: - Key: Name Value: ec2test Type: "AWS::EC2::Instance" myMountPoint: Properties: Device: /dev/xvda InstanceId: myEC2Instance VolumeId: myVolume Type: "AWS::EC2::VolumeAttachment" myVolume: Properties: AvailabilityZone: !GetAtt myEC2Instance.AvailabilityZone Size: 10 SnapshotId: snap-123456 Tags: - Key: Name Value: ebstest VolumeType: gp2 Size: 10 Type: "AWS::EC2::Volume" ```
How do I transfer data from EBS volume to EFS site using DataSync?
Hi There, I want to copy some data from my EBS volume to EFS site and for this purpose I want to use AWS DataSync. When I am trying to choose source location (while setting up Datasync Task) there is no option to choose EBS volume as source point. Can someone guide on how can I accomplish data transfer from EBS volume to EFS using DataSync service?
EBS Unoptimized Product
Hello Everyone, We have an AMI product on AWS and I have been updating the version as we make progress on our application. I have never changed from the way I have created the AMI that I am associating with the new version of the product. Last night I tried to change the version of the AMI product and put in the new AMI and received the following error which I have never seen before and can't find any information on it on the interwebs. Ebs unoptimized product This product does not support EBS optimized AMIs. Provide a new AMI that has EBS Optimization disable. Did I click on something by accident that would make this message appear? Any help would be greatly appreciated. Thanks!
DLM cloud watch matrics
Hi All, I have setup the DLM for daily & weekly backup of EBS volumes. I have setup the cloud matrics to get the total count of the Snapshot completed & failed. The sum of data is based on the period filter not the duration i.e., 1) If the period =1day and Duration : 1 months, it shows sum= 1 2) If the period=7days and Duration : 1 Months, it shows sum = 7 3) If the period=30days and Duration : 1 Months, it shows sum = 30 I want that when I select the duration, it should show total count of completed & failed snapshot. Please suggest. Regards, Nikhil Shah
InternalError creating EBS snapshot
With both web console and awscli, I get InternalError when trying to create a snapshot of an (8120GB gp3) EBS Volume. Running awscli with --debug shows no additional error information. I can find no prior snapshots for the volume(s). I've never made snapshots with this account before.
How to attach EBS volume from original EC2 instance to a new EC2 instance?
currently my website is running under a t3a.small EC2 instance (Origin - N California) and the volume size is 10 GIB. Now i have launched a new EC2 t2.micro instance (Origin - Mumbai) and the volume size is 8 GIB. All i'm doing for avoiding charges as i am a free tier user and the original instance is not cover the free tier promotion. So how can i attach EBS volume from original instance to new instance without losing any data?
EC2 Instance with recurrent I/O errors, but fsck reports filesystems as clean
I have a Linux (Ubuntu) instance running as m3.xlarge - this server is getting IO errors across multiple EBS volumes. I have unmounted the volumes and run fsck on them. One found some problems that were fixed, the others reported as clean. On restart, after a while (hour) I received more IO errors. As multiple volumes are involved, I wondered if there was an underlying hardware problem (I have multiple other very similar instances which are functioning as normal). I have stopped/started the instance to see if that would move it to a new host, but there is no way of telling. Suggestions on finding the issue? Is there a way to confirm if an instance has moved to a new host?
MBT to GPT format change
Hi, We have a 2TB volume m5.2xlarge instance, the root volume limit is 2TB and cannot increase the size because of size limit of it being MBR partion. Model: Amazon Elastic Block Store (nvme) Disk /dev/nvme0n1: 2147GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: The only way out seems https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ubuntu-convert-mbr-to-gpt/ Is that the only way out here, is there a better way of increasing the limit without data loss?
Conditions to attach EBS volumes
#### Hello, I have created an EBS volume and i am wondering if it would be possible to attach it to an EC2 instance which is created in another aws account. I have found some informations about the AZ (which has to be the same for EC2 and EBS volume). But "another account" ? Thanks in advance
EBS gp3 volumes in Severely Degraded state
Hello, We are running 3 i3.xlarge EC2 instances for a database cluster. We also attach a 750 GB gp3 EBS volume to each instance. We have a process that copies our backup snapshots from the i3.xlarge's instance store volume to the attached EBS volume for backup purposes. We've noticed that when initially attached, our EBS volumes are getting expected throughput and backups are completing quickly. After a few hours, the EBS volumes start going into the warning state and say that they are either getting degraded or severely degraded I/O performance. As such, throughput is very low and backups take a long time to complete. We are wondering why the volumes start out with expected performance and seemingly degrade over time. Here is how the bandwidth looks once the volumes enter the severely degraded state: https://imgur.com/a/uDmPfnl
In order to shrink the root volume of the AWS EBS
In order to shrink the root volume of the AWS EBS, the following steps were taken 1. acquire a snapshot of the root volume from the EC2 to be shrunk (set the EBS to be shrunk as v1) 2. create a volume from the snapshot created in step 1 (set the created EBS as v2) 3. Start a new EC2 from the same AMI as the EC2 to be downsized 4. Detach the root volume from the EC2 created in step 3 (the detached EBS is designated as v3) 5. Attach the v2 and v3 EBSs to the EC2 to be downsized 6. Synchronize the contents of v2 to v3 7. Change the root volume of the EBS to be shrunk to v3 After completing the above steps, when checking the connection to the server, I received a "Permission denied" error on Teraterm. Also, the Tereterm error message drops out as soon as it pops up. Is anyone else experiencing similar problems? I would like to borrow the wisdom of those in the know. Is anyone else experiencing similar problems? I would like to borrow the wisdom of those in the know. https://blog.e2info.co.jp/2021/10/29/aws-ebs%E3%83%AB%E3%83%BC%E3%83%88%E3%83%9C%E3%83%AA%E3%83%A5%E3%83%BC%E3%83%A0%E3%81%AE%E3%82%B5%E3%82%A4%E3%82%BA%E3%82%92%E7%B8%AE%E5%B0%8F%E3%81%99%E3%82%8B/