How to set default EBS volumeType to GP3 for AWS cluster?

Problem

• How to set default EBS volumeType to GP3 for AWS cluster ?

Environment

• Platform9 Managed Kubernetes - v5.6.8 and Higher
• AWS cluster

Procedure

1. Update the AWS Launch configuration for GP3 volume type:

   1. Call edit operation on the cluster:

      1. Edit operation will update the AWS launch configuration from gp2 volume type to gp3.(It will update the launch configuration with VolumeType=gp3, VolumeThroughput: 125 and VolumeIops: 3000)Users can use the PF9 UI or directly edit API:

UI method: Infrastructure > Clusters > Legacy > [select your cluster] > edit > update cluster

        2. **API method**: PUT /qbert/v4/<project_id >/clusters/<cluster_uuid>

Note

For custom VolumeThroughput/VolumeIops customers can use the Edit API with the below payload:

PUT /qbert/v4/<project_id>/clusters/<cluster_uuid> Payload: { "ebsVolumeThroughput": 250, "ebsVolumeIops": 4000 }

1. We can use the aws cli to migrate the volumes:

   1. Configure the AWS cli with accessKey/SecretKey/region [Configure the AWS CLI - AWS Command Line Interface ]
   2. Get the volume information to migrate AWS Console > Instances > select the node > Storage > Block device >
2. Modify the volume: aws ec2 modify-volume --volume-type <type of volume> --iops <value> --throughput <value> --volume-id <volume_id> modify-volume — AWS CLI 1.29.20 Command Reference

Example:

      Modify volume with default throughput/iops:

aws ec2 modify-volume --volume-type gp3 --volume-id vol-0ae4dff010dfdd799

     Modify volume with custom throughput/iops:

aws ec2 modify-volume --volume-type gp3 --iops 3500 --throughput 130 --volume-id vol- 0ae4dff010dfdd799

1. Check the status of the modification: Once the "ModificationState" is "completed", migration is completed.

aws ec2 describe-volumes-modifications --volume-id vol-0ae4dff010dfdd799