Connect AWS (local CLI) to Oh My Pi
Give Oh My Pi 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 Oh My Pi in four steps
Admins approve the server once. Everyone in Oh My Pi 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 Oh My Pi to Runlayer
Install the Runlayer CLI so Oh My Pi can reach AWS (local CLI), which runs on the user’s machine.
Oh My Pi 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 Oh My Pi
AWS (local CLI)’s approved tools appear in Oh My Pi. Every call is checked against policy and recorded.
Tools
2 AWS (local CLI) tools in Oh My Pi
Runlayer policy decides which of these Oh My Pi 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 Oh My Pi
Some controls apply to every client at the gateway. Others depend on what Oh My Pi exposes to Runlayer.
Gateway policy (available)
Every AWS (local CLI) call from Oh My Pi passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Oh My Pi as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Oh My Pi yet, so control happens at the gateway.
Frequently asked questions
Connect more