Skip to content

Automate AWS

Use S3 buckets, Textract, Transcribe and Cost Explorer from plain requests: store files sent to a link, pull totals out of receipts, transcribe recordings, and see yesterday's bill by service. Spend spikes and buckets growing past a size you set get flagged before they surprise you. Ask your AI assistant for the job, check the actions it lists, and it keeps working on AWS without you.

Try asking

Create a ClickRuntime automation: give me a link I can post a file or file URL to. Upload it to my S3 bucket acme-uploads under today's date and email me a download link that works for 7 days.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in AWS

Files stored and shared from S3, documents and recordings turned into text, and AWS costs and storage reported before the monthly bill arrives. These are ready-made starting points. Anything else you can describe works too.

Build your own

Build any AWS automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what AWS should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every morning, check AWS Cost Explorer for yesterday's spend by service and alert me if any service costs 30% more than its 7 day average.

Every day, list EC2 instances running for more than 7 days without an owner tag and post them to Slack.

Every Monday, pull last week's AWS costs per account into Google Sheets, post the totals to Slack, and email the finance team the sheet link from Gmail.

Works with

AWS with the apps you already use

S3 is good at keeping files, less good at telling anyone about them. Pairing it with sheets, chat and email puts extracted data and download links where people actually look.

AWS works with hundreds of other apps

Name any of them when you ask your assistant, and your automation connects them. Over 248 apps are ready to go, and anything with an API works too.

  • Cloudflare
  • DigitalOcean
  • GitHub
  • GitLab
  • Datadog
  • PagerDuty
  • Sentry
  • Amazon SES
  • Google Drive
  • Dropbox
  • Microsoft Teams
  • Discord
  • Notion
  • Airtable
  • BigQuery
  • Snowflake
  • Heroku
  • Vercel

Beyond chat

Have AWS work when you're not in the chat

Connecting AWS to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect AWS

AWS connects with an access key pair from a dedicated IAM user that you limit to exactly the buckets and services an automation needs.

AWS

Developer / Cloud infrastructure

  1. In the IAM console, create a user without console access just for ClickRuntime.
  2. Attach a minimal policy, for example s3:GetObject, s3:PutObject and s3:ListBucket on one bucket ARN, plus ce:GetCostAndUsage or Textract and Transcribe actions only if you use those automations.
  3. Open the user, go to Security credentials, choose Create access key and select Application running outside AWS.
  4. Copy the Access key ID and Secret access key, then save them with your region as secrets on Connections & secrets in the ClickRuntime dashboard.

Good to know

AWS limits that affect automations

  • The secret access key is shown only once when you create it. If you lose it, create a new key; each IAM user can hold at most two.
  • Never use root-user keys. A separate IAM user with a narrow policy limits what any automation can touch.
  • Cost Explorer charges $0.01 per API request, Textract bills per page and Transcribe per second of audio, all on your AWS account.
  • S3 bucket size metrics in CloudWatch update about once a day, so size reports reflect yesterday rather than this minute.
  • Zipping very large folders can run into script memory and time limits, so split big archives by prefix.

FAQ

Questions about automating AWS

What can ClickRuntime do in my AWS account?
Only what the IAM policy on your key allows. A policy covering one bucket keeps it to that bucket; cost and transcription actions need their own permissions added.
Who pays for Textract, Transcribe and Cost Explorer calls?
You do, on your AWS bill, since requests are signed with your keys. Plain S3 uploads and listings are billed by AWS as normal storage and request usage.
How soon does it spot a new file in a bucket?
These automations list the bucket on a schedule, every five or fifteen minutes or hourly depending on the job, and compare against what they saw last time.
Can I share files from a private bucket?
Yes. The automation creates a presigned download link that expires, such as after seven days, so the bucket itself stays private.
Is AI needed for these AWS jobs?
Textract and Transcribe are AWS services, not ClickRuntime AI. An optional summary of a transcript uses the AI included in each ClickRuntime plan, without any key from you.
Is this a AWS connector for ChatGPT or Claude?
Not for chatting with AWS data. A chat connector lets your assistant read and change AWS while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each AWS event.

Tell your assistant what AWS should do

Free plan. No credit card.