Skip to main content
Book a demo

Connect AWS (local CLI) to Gemini CLI

Give Gemini CLI governed access to AWS (local CLI)’s 2 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Gemini CLI setup guide

Set up

Add AWS (local CLI) to Gemini CLI in four steps

Admins approve the server once. Everyone in Gemini CLI then gets it through the same governed connection.

  1. 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. 2

    Connect Gemini CLI to Runlayer

    Install the Runlayer CLI so Gemini CLI can reach AWS (local CLI), which runs on the user’s machine.

    Gemini CLI setup guide
  3. 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. 4

    Use AWS (local CLI) from Gemini CLI

    AWS (local CLI)’s approved tools appear in Gemini CLI. Every call is checked against policy and recorded.

Tools

2 AWS (local CLI) tools in Gemini CLI

Runlayer policy decides which of these Gemini CLI 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 Gemini CLI

Some controls apply to every client at the gateway. Others depend on what Gemini CLI exposes to Runlayer.

  • Gateway policy (available)

    Every AWS (local CLI) call from Gemini CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Gemini CLI as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Gemini CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Gemini CLI’s model sees it.

  • Redact output in place (not available)

    Gemini CLI can only add text to a tool result, not replace it, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

In Gemini CLI

  • Enforcement needs Gemini CLI 0.26.0 or newer.
  • When Runlayer blocks a call or its output, Gemini CLI shows the model the block reason instead.

Frequently asked questions

Connect more

Find another combination