Questions tagged with Amazon Elastic Block Store
Content language: English
Sort by most recent
adding ec2 volume to instance with powershell
I got following script to add a new volume to instanceID. However I am unsure how to get the volume ID after volume creation. Also the DeviceID what should it be? ``` Param ( [string][Parameter(Mandatory) = $True] $InstanceId [string][Parameter(Mandatory = $True)] $driveletter, [int][Parameter(Mandatory = $True)] $size, [string][Parameter(Mandatory) = $True)] $az, [string][Parameter(Mandatory = $True)] $Region, [string][Parameter(Mandatory) = $True] $volumetype New-ec2volume -AvailabilityZone $az -VolumeType $volumetype -size $size -Region $Region Add-EC2Volume -InstanceId $InstanceId ) ```
Can I use multi-attach in Windows
I am trying to decipher the following statement (first bullet from [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volumes-multi.html#considerations)): > You can attach a volume that is Multi-Attach enabled to Windows instances, but the operating system does not recognize the data on the volume that is shared between the instances, which can result in data inconsistency. If OS doesn't recognize the data, then data inconsistency is least of my concerns, no? To summarize can I use multi-attach with Windows? Or the only option is FSx, that requires full-blown AD and therefore drives the price up?
What does the "Snapshot" column indicate? Why is it all the same string?
I would like to know what exactly the Snapshot column on the EBS Volume screen shows. In my environment, I am seeing the same string "snap-0df8908c34e3...." for all volume IDs. ![EBS Volume list view](/media/postImages/original/IMfHE49ep4QN2nfLlzW5OAmQ)
Instance reachability check failed
Hi In the Instance status checks show "Instance reachability check failed" and I am unable to SSH to the Instance. The AWS Compute Optimizer was throwing an error in EBS for reading and write bandwidth, so I decided to upgrade the instance from t2.medium to t3.large, also the hard drive from 8GB to 16GB to gp3. Now It shows Running. But in Status checks, Instance status check shows "Instance reachability check failed". The instance was working fine a few days back. I tried rebooting instance. It doesn't reboot. I start stop and start, that works and shows Running, but same instance status check issue. I tried rescue option mentioned in https://aws.amazon.com/premiumsupport/knowledge-center/ec2-instance-boot-issues/, but still the same issue. Here is the system log ` [ 12.483121] </TASK> [ 12.485967] Kernel Offset: 0x10600000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 12.497046] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]--- `
Can't connect EBS volume to new EC2 instance
EC2 instance (Ubuntu 20.04 LTS) and EBS volume are both in us-east-1a. When attempting to attach EBS volume to the instance, I get this message: "The instance configuration for this AWS Marketplace product is not supported. Please see the AWS Marketplace site for more information about supported instance types, regions, and operating systems." How do I fix this?
AMI Not Working With g5.2xlarge Instance Type
I launched a g5.2xlarge (Windows) instance type about a week ago. I've configured it exactly how I need and used the console to create an image of the server. The server contains only a single 150 GB EBS root volume. The image is created successfully but when I go to launch a second g5.2xlarge instance using this AMI, it shows the following under storage. I'm not sure where the second 450 GB volume is coming from or why I can't remove it. https://dl.dropboxusercontent.com/s/55fw9zl6aoalxoi/NVIDIA_Share_gvEY7NfSrE.png When the server is launched, I can see the 150 GB volume (but not the 450 GB one) in Windows but none of the data (files, configs, drivers, etc.) from the original server are there. It just looks like a bare Windows install. Did the data copied to that second invisible volume or something? Basically, all I want is an instance that's identical to the one I've already configured. I've done this successfully in the past but usually with Linux and with different instance types. Thanks.
EBS Snapshot and Volume creation
We are currently working on designing a resilient system that can handle storage failure. I would like to know if this is even possible to achieve from an infrastructure point. The system will be consist of ELB -> ALB -> EC2. The autoscaling group will have 2 pool, one warm and one active pool (both contain a max of 1 instance). In order to achieve high resiliency we are planning on creating a snapshot of active instances EBS volume every 3 minute. In warm autoscaling pool we will have a warm instance ready to go. We will run a lambda every 3 minutes that will pull the latest snapshot and attach to the warm pool instance. In that way if any time the active goes down, the warm instance can come up with latest snapshot data. In theory this looks doable but is there any technical issues that we might run into? Also, how much time it takes for a volume to be built from a 500GB snapshot? Other info: a) There is only ~5KB/sec of data written per second during business hours only. b) The EBS volume will have around 500GB of data Thanks