Skip to content
ClickRuntime

Connect AWS to Slack

Backups, archives and uploaded invoices all end up in S3, and it's easy to lose track of whether they actually happened. Posting to Slack after each job gives your team a simple record that the work ran, and what it found.
Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Ideas

What you can do with AWS and Slack

Backup confirmations, archive reports and invoice summaries from S3 posted to Slack. These are ready-made starting points. Anything else you can describe works too.
On a schedule

Back up your Airtable base to S3 every night

Every night each table in your Airtable base is saved as a CSV in a dated S3 folder, backups older than 30 days are removed, and Slack confirms it worked.

See how it works
On a schedule

Move old Salesforce files to S3 and report in Slack

Every week, Salesforce files older than a year are moved to your S3 bucket to free up storage, and Slack reports how many files and megabytes were archived.

See how it works
Every 15 minutes

Post a summary of each invoice uploaded to S3 to Slack

Each new invoice in your S3 bucket is read, and Slack gets the vendor, amount and due date within 15 minutes.

See how it works
The moment it happens

Save a copy of any web page to S3 and share the link in Slack

Send a URL to your automation's link and a copy of the page is saved to S3, with a download link posted to your research channel.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with AWS and Slack, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any AWS and Slack automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what should happen between AWS and Slack 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

Post to Slack only if daily AWS spend goes over $50 or any service doubles day on day.

Each Monday, list EC2 instances running over 7 days without a "keep" tag and post them to #ops.

Use cases

Why people connect AWS and Slack

How the two apps work together

  • A schedule or a check every few minutes reads AWS using your access keys.
  • The script posts results to the Slack channels you choose.
  • Commands in Slack can be read on the next check to trigger actions such as a backup.

  • DevOps teams watching costs

    AWS cost changes are posted to #ops daily. Spikes are caught early.

  • Engineers checking backups

    Each nightly backup to S3 posts a confirmation or failure. Missing backups are noticed.

  • Teams tracking uploads

    New files in S3 are posted with name and size. People know when data arrives.

  • Startups watching EC2 usage

    Running instances are listed daily. Forgotten servers are found.

More apps

AWS, Slack and other apps in one automation

An automation isn't limited to two apps. Add the next step in another app and it runs as part of the same automation.

Cost log

Post daily AWS costs to #ops and add them to my Google Sheet.

Backup on release

When a release is published on GitHub, save the release assets to S3 and post the links to #releases.

Escalate failed backups

If tonight's S3 backup fails, post to #ops and create a PagerDuty incident.

Setup

Connect AWS and Slack once

Every idea on this page uses the same two connections, so you set them up once. If one is missing, your assistant tells you and links to the right place.

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.

Slack

Team chat

  1. At api.slack.com/apps, create a new app from scratch in your workspace.
  2. Under OAuth & Permissions, add the bot scopes the automation needs, such as chat:write, channels:read and channels:history.
  3. In the ClickRuntime dashboard, open Connections, choose Slack and enter your app's details, then install it to your workspace.
  4. In each channel the automation should use, type /invite @your-app-name.

FAQ

Questions about connecting AWS and Slack

What AWS permissions are needed?
Only the S3 actions the automation uses, such as putting, listing and deleting objects in one bucket, plus Textract for invoice reading. Use a dedicated IAM user.
Does Slack get the files themselves?
No. Slack gets a summary and, where useful, a time-limited download link. The files stay in S3.
What if a backup fails?
The run fails and shows the error in your ClickRuntime dashboard. Ask your AI assistant to post failures to Slack too, so silence never means success.
Can I choose the channel?
Yes, each automation posts to the channel you name, such as #ops or #finance.
Can it post to Slack without AWS SNS?
Yes. The script calls AWS APIs and posts to Slack directly.
Which regions does it check?
The regions you list. Many services are per region.
Can it stop instances?
Yes, if the key allows it, but most teams keep that manual.

Related pages

Keep exploring

Tell your assistant what AWS and Slack should do together

Free plan. No credit card.

Add to ChatGPTAdd to Claude