- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hello, it is possible to change EBS volume types that are attached to instances, depending on the volume type and instance type. The CLI command documentation[1] says "You can modify several parameters of an existing EBS volume, including volume size, volume type, and IOPS capacity. If your EBS volume is attached to a current-generation EC2 instance type, you might be able to apply these changes without stopping the instance or detaching the volume from it." Altough it's not clear what is meant by "current-generation" it's worth giving a try on you r5.
Please follow this documentation to learn how:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/requesting-ebs-volume-modifications.html
If you run into any trouble here's a troubleshoot guide that might help you (worth reading before requesting volume changes though):
https://repost.aws/knowledge-center/ebs-change-volume-type-issues
Is there any specific reason why you would like the gp2 volume ? gp3 volume are the next generation and offers better baseline performance for lower price per GB. Here's is an excellent comparison of both gp2 and gp3: https://aws.amazon.com/ebs/general-purpose/?nc1=h_ls
Hope this helps you. Let me know if you have further questions.
Have a nice day!
References
Yes you can change the volume type of an EBS volume without stopping the instance or detaching the volume. You just need to call the modify-volume api.
Hi there.
I know you may be seeing conflicting answers here but I don't think you can change the NVMe volume type. Per the instance description
With R5d instances, local NVMe-based SSDs are physically connected to the host server and provide block-level storage that is coupled to the lifetime of the R5 instance
These volumes are what is called Instance Store Volumes and are physically attached to the instance.
For instance types with NVMe instance store volumes, all of the supported instance store volumes are automatically attached to the instance at launch. For instance types with non-NVMe instance store volumes, such as C1, C3, M1, M2, M3, R3, D2, H1, I2, G2, X1, and X1e, you must manually specify the block device mappings for the instance store volumes that you want to attach at launch. Then, after the instance has launched, you must format and mount the attached instance store volumes before you can use them. You can't attach an instance store volume after you launch the instance.
Some instance types use NVMe or SATA-based solid state drives (SSD), while others use SATA-based hard disk drives (HDD). SSDs deliver high random I/O performance with very low latency, but you don't need the data to persist when the instance terminates or you can take advantage of fault-tolerant architectures. For more information, see SSD instance store volumes.
I hope this helps.
Hi,.
The only way I know to do that is to go via Snapshot of disk of type that you want to change, detach of unwanted disk, creation of new disk of proper type, and then restore on the disk of the new type that you want.
It it detailled here (for slightly different disk types): https://n2ws.com/blog/how-to-guides/how-to-change-your-ebs-volume-type
Best,
Didier
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 4 mesi fa
His instance a r5.16xlarge not r5d, it is EBS only. https://aws.amazon.com/ec2/instance-types/r5/. I think the nvme term is missused in his question.