Connect AWS (local CLI) to GitHub Copilot
Give GitHub Copilot governed access to AWS (local CLI)’s 2 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add AWS (local CLI) to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.
- 1
Approve AWS (local CLI) in Runlayer
Add AWS (local CLI) from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot to Runlayer
Install the Runlayer CLI so GitHub Copilot can reach AWS (local CLI), which runs on the user’s machine.
GitHub Copilot setup guide - 3
Sign in to AWS (local CLI)
Sign in the way AWS (local CLI) requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use AWS (local CLI) from GitHub Copilot
AWS (local CLI)’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
2 AWS (local CLI) tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot users can call. 1 read data only and 1 can change or delete data.
Suggest AWS CLI commands
Suggest AWS CLI commands based on a natural language query.
Execute AWS CLI commands
The command MUST start with "aws" and follow AWS CLI syntax
Control
What Runlayer can see and stop in GitHub Copilot
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every AWS (local CLI) call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more