Does every team member need their own AWS account?

No. Loopthink holds one key or token for AWS. Your people sign in to Loopthink with their own identity, and every call to AWS is logged under their name. Seats in AWS stay where they are today.

Who has to add the connector in ChatGPT?

One person with the right to add connectors in your ChatGPT workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.

Where does the AWS key live?

In Loopthink, encrypted, in the EU. It never reaches ChatGPT and never reaches the people using the connector. Rotate it in AWS whenever you like and paste the new one once.

Can somebody write to AWS from the chat?

Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.

Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. No call needed.

We already run our own MCP server for AWS. Does it still work?

Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.

AWS · ChatGPT

AWS in ChatGPT. In five minutes.

Connect AWS in Loopthink, paste one URL into ChatGPT, ask. Hosted in the EU, every call logged.

Start free See the steps

Free for 2 connectors, no card · Pro €19 · EU-hosted

How to connect

Three steps. The third one is asking.

1
Connect AWS in Loopthink
Read-only IAM access key, one region, table and log-group allow-list.
2
Paste one URL into ChatGPT
Add a custom connector with a name and the URL. That is the whole form.
3
Ask
"What is the status of order 4711, and does the checkout log show an error for it?" Every answer comes from your data, every call is logged.

Start free

Show all steps

1
IAM: create a user for Loopthink with a read-only policy over the resources you want to expose. DynamoDB needs ListTables, DescribeTable, GetItem, Query and Scan; CloudWatch Logs needs DescribeLogGroups, DescribeLogStreams, FilterLogEvents, StartQuery, GetQueryResults and StopQuery. No write actions, no other resource.
2
Create an access key for that user and note the region, for example eu-central-1.
3
Paste key, secret and region into Loopthink, then tick the tables and the log groups. A VPC endpoint can be given instead of the public one, in which case the traffic never leaves your VPC.
4
An admin turns on Developer mode: Settings → Apps → Advanced settings. On Enterprise and Edu, admins first grant it under Permissions & Roles → Connected Data.
5
Workspace settings → Apps → Create: paste your Loopthink connector URL, choose OAuth, click Scan Tools, then Create. Publish the draft under Workspace settings → Apps → Drafts.
6
Each team member picks Loopthink from the tools menu in a chat, or @mentions it, and signs in once with their own account.

Steps checked against the vendor documentation on 17 September 2026: DynamoDB fine-grained access control · DynamoDB identity-based policy examples · VPC endpoints for DynamoDB · CloudWatch Logs data protection policies · CloudWatch Logs Insights query syntax · Managing IAM access keys · AWS Labs MCP servers · Developer mode and MCP apps in ChatGPT · Connectors in ChatGPT

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 ChatGPT 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.

Use cases

What people actually ask ChatGPT about AWS.

Support
“What is the status of order 4711, and does the checkout log show an error for it?”
Developers
“Which errors did /aws/lambda/checkout throw in the last hour, and on which instances?”
Management
“How many orders landed yesterday by country, and how often did checkout fail?”

Why Loopthink

Why not an access key in an MCP config?

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.

Loopthink runs hosted and gives ChatGPT a URL. Every colleague signs in with their own account and sees only what you ticked.

FAQ

Before you connect.

Does every team member need their own AWS account?: No. Loopthink holds one key or token for AWS. Your people sign in to Loopthink with their own identity, and every call to AWS is logged under their name. Seats in AWS stay where they are today.
Who has to add the connector in ChatGPT?: One person with the right to add connectors in your ChatGPT workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.
Where does the AWS key live?: In Loopthink, encrypted, in the EU. It never reaches ChatGPT and never reaches the people using the connector. Rotate it in AWS whenever you like and paste the new one once.
Can somebody write to AWS from the chat?: Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.
What does it cost?: Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. No call needed.
We already run our own MCP server for AWS. Does it still work?: Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.

When colleagues join

One matrix for AWS. Roles across, tools down.

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 ChatGPT user in your team gets exactly this.

AWS starts on Team, €49 a month. Roles, a login for every colleague and field masking start at €19 a month with Pro. See the plans