Add ec2:ModifyVolume action

[zodiac12k]

Add ec2:ModifyVolume action to get authorization to resize volume.
I think it needs to be added to example permission policy json file

Is this a bug fix or adding new feature?
I think it is Improvement?

What is this PR about? / Why do we need it?
If it doesn't have this action in the permission policy, you should see the following error log when resizing volume.

I1230 05:25:14.083279       1 event.go:209] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"ebs-claim", UID:"6dc884e0-2ac4-11ea-95ac-025d239d2fe4", APIVersion:"v1", ResourceVersion:"547846", FieldPath:""}): type: 'Normal' reason: 'Resizing' External resizer is resizing volume pvc-***
I1230 05:25:14.083201       1 connection.go:181] GRPC request: {"capacity_range":{"required_bytes":5368709120},"volume_id":"vol-***"}
I1230 05:25:14.157532       1 connection.go:183] GRPC response: {}
I1230 05:25:14.157906       1 connection.go:184] GRPC error: rpc error: code = Internal desc = Could not resize volume "vol-***": could not modify AWS volume "vol-***": UnauthorizedOperation: You are not authorized to perform this operation.
	status code: 403, request id: e4cbf4d1-311f-48d8-b9a1-147f9cf90c0c
E1230 05:25:14.157919       1 controller.go:342] Resize volume "pvc-***" by resizer "ebs.csi.aws.com" failed: rpc error: code = Internal desc = Could not resize volume "vol-***": could not modify AWS volume "vol-***": UnauthorizedOperation: You are not authorized to perform this operation.
	status code: 403, request id: e4cbf4d1-311f-48d8-b9a1-147f9cf90c0c
I1230 05:25:14.157985       1 event.go:209] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"ebs-claim", UID:"6dc884e0-2ac4-11ea-95ac-025d239d2fe4", APIVersion:"v1", ResourceVersion:"547846", FieldPath:""}): type: 'Warning' reason: 'VolumeResizeFailed' resize volume pvc-*** failed: rpc error: code = Internal desc = Could not resize volume "vol-***": could not modify AWS volume "vol-***": UnauthorizedOperation: You are not authorized to perform this operation.
	status code: 403, request id: e4cbf4d1-311f-48d8-b9a1-147f9cf90c0c

What testing is done?
After I add this action in the permission policy, resizing volume succeeded!!

I1230 05:29:31.434951       1 controller.go:211] Started PVC processing "default/ebs-claim"
I1230 05:29:31.441255       1 connection.go:180] GRPC call: /csi.v1.Controller/ControllerExpandVolume
I1230 05:29:31.441386       1 event.go:209] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"ebs-claim", UID:"6dc884e0-2ac4-11ea-95ac-025d239d2fe4", APIVersion:"v1", ResourceVersion:"548274", FieldPath:""}): type: 'Normal' reason: 'Resizing' External resizer is resizing volume pvc-***
I1230 05:29:31.441267       1 connection.go:181] GRPC request: {"capacity_range":{"required_bytes":6442450944},"volume_id":"vol-***"}
I1230 05:29:43.771331       1 connection.go:183] GRPC response: {"capacity_bytes":6442450944,"node_expansion_required":true}
I1230 05:29:43.771715       1 connection.go:184] GRPC error: <nil>
I1230 05:29:43.771722       1 controller.go:345] Resize volume succeeded for volume "pvc-***", start to update PV's capacity
I1230 05:29:43.782629       1 controller.go:351] Update capacity of PV "pvc-***" to 6Gi succeeded
I1230 05:29:43.787106       1 controller.go:401] Mark PVC "default/ebs-claim" as file system resize required
I1230 05:29:43.787175       1 event.go:209] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"ebs-claim", UID:"6dc884e0-2ac4-11ea-95ac-025d239d2fe4", APIVersion:"v1", ResourceVersion:"548274", FieldPath:""}): type: 'Normal' reason: 'FileSystemResizeRequired' Require file system resize of volume on node
I1230 05:29:45.981975       1 reflector.go:370] k8s.io/client-go/informers/factory.go:133: Watch close - *v1.PersistentVolumeClaim total 20 items received

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @zodiac12k!

It looks like this is your first PR to kubernetes-sigs/aws-ebs-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/aws-ebs-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @zodiac12k. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[coveralls]

Pull Request Test Coverage Report for Build 971

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 70.706%

---

Totals
Change from base Build 969:	0.0%
Covered Lines:	1231
Relevant Lines:	1741

---

💛 - Coveralls

[leakingtapan]

/ok-to-test

[leakingtapan]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leakingtapan, zodiac12k

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [leakingtapan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[leakingtapan]

/retest

[leakingtapan]

/retest