#8946 copr backend needs larger volume, but we miss AWS some permissions
Closed: Fixed by praiskup. Opened by praiskup.

I'm testing with staging for now:

$ aws ec2 modify-volume --volume-id vol-0e346bab1f067b279 --size 550
An error occurred (UnauthorizedOperation) when calling the ModifyVolume operation: You are not authorized to perform this operation.

We have remaining 250G (yesterday we had ~350G). Remaining space goes up and
down (repo pruning) but it is pretty urgent.


We wanted to increase the size of volume vol-0c34460f33abc05f3 from 8TB
to 12TB. So perhaps, instead of granting us the needed permissions,
someone could enlarge the volume for us .... but if we go this way,
please consult with copr team first here so we can synchronize ourselves:

  • create the snapshot first
  • test our workflow on staging vol-0e346bab1f067b279 first

If you were to be granted access to do this the following permissions should be enough with the usual tag conditions.

"Action": [
"ec2:AttachVolume",
"ec2:CreateVolume",
"ec2:DescribeVolumeAttribute",
"ec2:DescribeVolumeStatus",
"ec2:DescribeVolumes",
"ec2:DetachVolume",
"ec2:EnableVolumeIO",
"ec2:ModifyVolumeAttribute",
"ec2:ModifyVolume"
]

Note: ec2:ModifyEbsDefaultKmsKeyId may also be necessary if the volume is encrypted
Note: The resource block will have to be * for this to work through the API

Another thing to note is that when the volume size is increased the partitions and file systems on the instance will also need to be edited to use the extra space.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: groomed, high-gain, medium-trouble

@praiskup I've added the perms @mobrien mentioned there... can you see if it allows you now?

Resize works, thank you!

Metadata Update from @praiskup:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata