-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document "Connect VSCode to EC2 Instance" #6434
Comments
Thanks for the notes, we are eager to hear feedback on the EC2 features.
Did AWS Toolkit give useful hints about the required permissions? Or how did you end up finding those? |
There was a pop-up message with the list of permission above and stated which IAM instance profile it (i.e., assuming inline policy) would be attached to. |
Note also that as an alternative, either of these policies is sufficient:
|
Oh interesting, the instance I'm connecting to does have |
To confirm, when you attached the explicit permissions to the EC2 Instance Profile, that worked, but attaching a policy containing the required permissions didn't work? |
Updated documentation: https://docs.aws.amazon.com/toolkit-for-vscode/latest/userguide/ec2-overview.html |
This request was addressed in AWS Toolkit 3.44.0 and/or Amazon Q 1.45.0! AWS Toolkit changelog: https://github.com/aws/aws-toolkit-vscode/blob/master/packages/toolkit/CHANGELOG.md |
To use this feature, it seems like a few steps are required:
First, this feature is still experimental, so you must enable it:
Second, the EC2 Instance Profile must have the following IAM permissions
VSCode will attempt to attach these permission to the instance profile, but unless you've IAM edit privileges, you are stuck here.
Documentation for this at AWS docs doesn't exist yet.
The text was updated successfully, but these errors were encountered: