Add ability to have multiple --local-forwarding arguments to ec2-instance-connect ssh command

[lludsubaru]

Describe the feature

The aws ec2-instance-connect ssh command already takes in one parameter for a local forwarding string; the ssh program supports multiple local forwarding options so allowing multiple would help when there is more than one forwarding rule desired

Use Case

Often when connecting into a VPC to run something locally, you might have a database instance and a elastic cache instance or something similar. Being able to forward ports for both of them on a single command is simpler than running multiple ssh commands.

Proposed Solution

Wish I was more of a python developer, but it seems like there should be a way to tag an argument as one that can be provided multiple times and then just loop through those arguments when creating the ssh command and adding the "-L" options to it.

Other Information

I tried putting multiple --local-forwarding parameters but it only seems to use the last one

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CLI version used

aws-cli/2.13.22 Python/3.11.5 Windows/10 exe/AMD64 prompt/off

Environment details (OS name and version, etc.)

Windows 11

[tim-finnigan]

Thanks for the feature request. The ec2-instance-connect customization is maintained by another team internally so I'll reach out to them for feedback on this. In the meantime others can 👍 your issue to +1 it, and if there are any additional details you can share regarding your use case please do.

[tim-finnigan]

We heard back from the team maintaining this customization, and they noted that this feature request may be a duplicate (or closely overlap with) another recent issue: #8952. We may want to consolidate these for tracking going forward, or otherwise elaborate on specific differences. Regarding #8952 — the team acknowledged that it would be a beneficial enhancement of the plugin and added the feature request to their backlog for further tracking.

[lludsubaru]

Thanks Tim ( and team ). I think that makes sense both being about parameters passed; but it sounds like two different sets of parameters. one: to have multiple of a specific parameter that is already there, and two: the ability to pass additional custom commands to the ssh call. The 2nd one would probably satisfy my use case but since there is already a specific parameter for creating a tunnel it seems like it would be cleaner to implement it with a repeated parameter. But obviously, whatever works best for your team is great.

[RyanFitzSimmonsAK]

Closing this issue as the appropriate team has acknowledged this feature request and backlogged another that covers this use case. Please refer to the AWS CLI changelog for updates going forward.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.