Cloud & Containers

Every AWS service.
One tool.

InTouch AI eats the specialized cloud tool. InTouch AI wraps the AWS CLI v2 as a first-class tool — every service, every command, every region — with no per-service plugins to add and no SDK stack to maintain. And it reaches well beyond AWS: a first-class Google Workspace tool for Gmail, Calendar, Drive, Docs, and Sheets, plus the spawn tool for Azure, GCP, and anything else a CLI can do. One engine reaches every cloud; a single-cloud point tool can't grow that center.

We ship light — on purpose

The install is clean and minimal. The power is the InTouch Hub: 2,000+ ready-to-run tools, skills, workflows, and monitors, one click to install — you add only what you need, no bloat. Need something the Hub doesn't have yet? Describe it and the AI builds it. The cloud connectors below are all a click away.

AWS (CLI v2)

S3, EC2, Lambda, DynamoDB, RDS, ECS, ECR, SQS, SNS, Secrets Manager, Systems Manager — anything the CLI can do, InTouch AI can schedule. Credentials via the vault; assumed-role support; region routing per tool.

Google Workspace

Drive file ops, Sheets read/write, Docs export, Gmail send/search, Calendar. Service-account authentication. Wraps the Google Workspace gcloud CLI and native APIs.

Azure / GCP via Spawn

No native Azure or gcloud tool today — use the spawn tool to invoke the az or gcloud CLI with credentials sourced from the vault. Same audit trail as a native tool.

HTTP / REST

Any cloud or SaaS REST API. Inline credentials or vault references, header templates, JSON body templates, response-to-property extraction.

Kubernetes via Spawn

kubectl through the spawn tool with a kubeconfig from the vault. Deploy rollouts, run jobs, inspect pod logs — all orchestrated from InTouch AI.

What Teams Actually Build

Every pattern below is a contract, now intelligent: what to run, when, what to do when it works, what to do when it doesn't, and who to notify. The "doesn't work" clause isn't a dumb retry-N-times-and-email-a-log rule anymore. InTouch AI reads the failure — an expired AWS token, a throttled API, a container that exited non-zero — knows why, smart-retries or refreshes the credential, and surfaces the one sentence that matters. It broke. Here's why. I fixed it. No older cloud scheduler can say that.

Scheduled S3 → DB

Pick up new objects from an S3 prefix (folder trigger via the AWS tool), parse with the DataFrame tool, load into the warehouse. Move processed files to an archive prefix. Alert on parse failures.

Periodic Cost Report

Call aws ce get-cost-and-usage on a Weekday schedule, pipe into a DataFrame transform, email the Top-10 line items to finance. Turn the determinism dial: swap Anthropic for Ollama if account data must never leave the network, or graduate the whole workflow to zero-AI-cost and identical-every-time once it's earned your trust.

Inbox to Action

Watch a shared Gmail inbox with the Google Workspace tool, pull the request with an AI call, file it and reply — the recurring triage a person does by hand, now scheduled and audited.

Google Sheets Sync

Pull a Sheet into a DataFrame, enrich rows via an AI call, write the result back. Schedule hourly during business, cutoff at 18:00.

Cloud Credentials Belong in a Vault, Not a File

This is the trust floor. Every cloud credential — AWS access keys, GCP service-account JSON, Google Workspace service accounts — lives in the strongly encrypted credential vault, never pasted into a script, never exposed even to the AI itself. Never in ~/.aws/credentials on a server someone forgot about. access control on the credential object controls who can run workflows that resolve it.

Cloud Automation, Without the SaaS Relay

One InTouch AI for every cloud, self-hosted, credential-safe, audit-logged. Free Personal edition.

Download InTouch AITalk to Sales