Connect · AWS

Connect AWS to your AI client. For your whole team.

Two AWS services carry the answers people ask a chat for: DynamoDB holds the records, CloudWatch Logs holds what happened to them. An access key pasted into an MCP config reaches both with whatever its IAM policy allows, for whoever holds the config file. Pick the client your team uses:

Free for 2 servers, no card · Paid plans from €39 · EU-hosted

Who may do what

One matrix for AWS, whichever client asks.

Tool	Developers	Support	Management
List tables and log groups	Developers may use List tables and log groups	Support may use List tables and log groups	Management may use List tables and log groups
Get item by key	Developers may use Get item by key	Support may use Get item by key	Management may not use Get item by key
Query by key condition	Developers may use Query by key condition	Support may use Query by key condition	Management may use Query by key condition
Scan a page of rows	Developers may use Scan a page of rows	Support may not use Scan a page of rows	Management may use Scan a page of rows
Search log events	Developers may use Search log events	Support may use Search log events	Management may not use Search log events
Logs Insights query	Developers may use Logs Insights query	Support may not use Logs Insights query	Management may use Logs Insights query
List log streams	Developers may use List log streams	Support may not use List log streams	Management may not use List log streams
Write actions off by default	Developers may not use Write actions	Support may not use Write actions	Management may not use Write actions

Masked for every role: e-mail, phone and delivery address attributes in every item, payment and token attributes, whatever they are called, e-mail addresses, IPs and bearer tokens inside log lines, including ones written before you set the rule, attributes that appeared after discovery, until somebody classifies them.

You set this once. Every user in your team, in every client, gets exactly this.

What you connect

Two services, one key.

An AWS account holds two kinds of answer: the records, in DynamoDB, and what happened to them, in CloudWatch Logs. Loopthink reaches both from the same read-only key and publishes them as separate tools, so the client can follow an order from the table into the log without anybody switching windows.

The records

Amazon DynamoDB

You tick the tables that may be reached. Loopthink reads each one's key schema once, so the tools it publishes name the actual partition and sort key instead of asking the model to guess.

Tools per table

List tables the enabled ones only, with what each holds, so the model finds the right table before it reads anything.
Get item by key one row, by its primary key.
Query by key condition rows under one key, filtered, capped at 200 per call and paged from there.
Scan a page of rows for the questions that have no key, with the same cap and the same paging.

Read-only, by construction. No write tool exists for DynamoDB in Loopthink. Not switched off, not present. The IAM policy you paste has no write action in it either, so both layers say the same thing.

The DynamoDB MCP server AWS publishes now does data modelling; item operations moved to the AWS API MCP server, which states it is not built for more than one user.

Where the IAM policy stops for DynamoDB →

What happened to them

Amazon CloudWatch Logs

You tick the log groups. Everything else in the account stays invisible, and inside the ones you picked, masking runs at read time, so it covers the months written before anyone thought about it.

Tools per log group

List log groups the enabled ones, with what each one carries.
Search log events a filter pattern over a window, the last hour by default, up to 200 events per call.
Logs Insights query counts, stats and grouped results, with the log group supplied by the tool so a query cannot reach past its scope.
List log streams newest activity first, to see which instance or invocation wrote recently.

Read-only, by construction. Only the describe, filter and query APIs are implemented, so nothing here can delete a log group or write an event, whatever the connection is set to.

The CloudWatch MCP server AWS publishes says it can only be run locally on the same host as your LLM client, with that machine's AWS profile.

Who may read the log line? →

Both sit behind the same permission matrix above, and behind the same masking. A support colleague can read an order and the log line that mentions it, with the customer's e-mail address removed from both on the way out, and every one of those calls is logged under that person's name.