1 Answer
- Newest
- Most votes
- Most comments
0
You will need to add to the existing volume. Here are the commands to make it happen.
## Assume a role with permissions
SIZE=50
INSTANCEID=$(curl http://169.254.169.254/latest/meta-data/instance-id)
REGION=$(curl -s http://169.254.169.254/latest/meta-data/placement/availability-zone | sed 's/\(.*\)[a-z]/\1/')
VOLUMEID=$(aws ec2 describe-instances --instance-id $INSTANCEID --query "Reservations[0].Instances[0].BlockDeviceMappings[0].Ebs.VolumeId" --output text --region $REGION)
aws ec2 modify-volume --volume-id $VOLUMEID --size $SIZE --region $REGION
Wait until finished, check with this:
aws ec2 describe-volumes-modifications --region $REGION --volume-id $VOLUMEID
After finished
lsblk
sudo growpart /dev/nvme0n1 1
df -h
sudo xfs_growfs /dev/nvme0n1p1
df -h
Relevant content
- Accepted Answerasked 6 months ago
- asked 9 months ago
- Accepted Answerasked 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
Thanks for your answer! The volumen is already working and accessible from the command line, the issue is with the C9 editor, can't point to browse files on the attached volume
Yes, if you need more space and you want to see it from C9, you will need to expand the root volume.