AWS · Cloud service
Amazon Simple Notification Service with OrchestrAI
Catalog exported 2026-09-02
Set up Amazon SNS from chat: create topics, add subscriptions, and set topic access policies.
OrchestrAI exposes 4 SNS operations: 2 are low-risk (read-only or low-impact), and 2 create or modify resources and run only after you confirm the plan.
What teams use it for
Teams use OrchestrAI to create a topic for alerts, subscribe an email address, SQS queue, or Lambda function to it, and apply a topic policy that lets CloudWatch or S3 publish to it. Topic creation and subscriptions are medium risk and create resources that can be removed later. There is no operation to publish a message, list topics, unsubscribe, or delete a topic, so testing a topic with a message or cleaning up subscriptions is done in the console.
Every SNS operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Create SNS Topic (Terraform-style) |
Create an SNS topic for notifications | Low risk | No |
Set SNS Topic Policy |
Set access policy on an SNS topic | Low risk | No |
Create SNS Topic |
Create an Amazon SNS topic | Creates resources | No |
Subscribe to SNS Topic |
Subscribe an endpoint to an SNS topic | Creates resources | No |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Create an SNS topic called ops-alerts in us-east-1 and subscribe oncall@example.com
- Subscribe the order-events SQS queue to the orders-topic SNS topic
- Set a policy on ops-alerts that allows CloudWatch alarms to publish
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Can OrchestrAI publish a test message to an SNS topic?
- No, publishing is not in the current operations; coverage is topic creation, subscriptions, and policies.
- Which SNS subscription types does OrchestrAI support?
- The subscribe operation accepts any protocol SNS supports, including email, SQS, Lambda, and HTTPS endpoints.
- Which SNS operations need an extra approval step?
- None of the SNS operations currently carries a step-level approval gate; they are read-only or run after plan confirmation like any other change.
Other AWS services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.