Cloud / Storage / CI-CD · 61 pre-built actions
AWS integration with Nexus
Turn AWS events into governed work, not unattended scripts. Files arrive, alarms fire and messages queue in AWS. Nexus starts a governed run from those events and applies rules, approval and audit before anything consequential happens.
Pre-built actions
What you can automate
61 pre-built AWS actions, grouped by what they work on.
61
PRE-BUILT ACTIONS
- 01Representative AWS services are S3, SNS, SQS and CloudWatch.
- 02Trigger sources include AWS S3, AWS SNS, AWS SQS, AWS CloudWatch and AWS CloudWatch Events.
Workflow
How it fits into a Nexus workflow
AWS S3, SNS, SQS, CloudWatch and CloudWatch Events are listed trigger sources. A new object, message, alarm or event can start a run with the event payload as input.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Use the HTTP Request node or Rules + Code with your chosen SDK for AWS operations outside the pre-built action groups.
02
Use SSH where a host-level step is required and approved.
03
Gate production-affecting actions with human approval under policy.
Examples
Workflow examples
Invoice intake from S3
A new invoice file in S3 starts reconciliation against SAP and a SQL source.
Alarm-driven runbook
A CloudWatch alarm starts a runbook that gathers context and requests approval before remediation.
Queue-driven processing
SQS messages start runs that validate, process and record each item.
Security ticketing from telemetry
A CloudWatch event is enriched and opened as ServiceNow or Jira work.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Multi-system workflows
Use cases that include AWS
AWS S3 or Azure Blob Storage, SAP, MSSQL or Oracle
Invoice intake and reconciliation with object storage, SAP and SQL
A file lands in object storage, SAP and a reconciliation database are checked, Rules + Code matches the result and exceptions go to a named reviewer.
AWS CloudWatch, SNS, SQS, ArgoCD, Kubernetes
Event-driven cloud operations with AWS, ArgoCD and Kubernetes events
CloudWatch, SNS, SQS, ArgoCD and Kubernetes events start a governed runbook, with approval before any change that policy marks as consequential.
AWS CloudWatch, ServiceNow or Jira
Security incident enrichment and ticketing from cloud telemetry
An AWS CloudWatch event is enriched with Rules + Code and becomes a ServiceNow or Jira work item with the evidence attached.
Integration patterns
AWS integration patterns
Dedicated patterns that pair AWS with another system in one governed run.
Industry use cases
Processes that use AWS
Defense & national security
Cloud incident to controlled remediation
Cloud events become incidents and engineering tasks, and remediation runs only when approved.
Critical infrastructure
Infrastructure alert to incident and remediation
Alerts become incidents and engineering issues, and infrastructure changes run only when approved.
Critical infrastructure
Operational data to analytics
Operational files load into Snowflake reliably, and teams are told when data is ready.
Critical infrastructure
Cloud event to analytics workflow
Cloud events are enriched, loaded for analysis and escalated when thresholds are crossed.
FAQ
AWS connector questions
- Which AWS services can trigger a workflow?
- AWS S3, SNS, SQS, CloudWatch and CloudWatch Events are listed trigger sources.
- Does this page list every AWS action?
- No. Nexus includes 61 AWS actions across EC2, S3, IAM and Lambda. SNS, SQS and CloudWatch are trigger sources.
- Does using AWS change where Nexus runs?
- No. Nexus runs where you deploy it and reaches AWS over the network paths you allow.
Related reading
Continue from here
- Azure connector
The equivalent storage and event sources on Azure.
- ArgoCD connector
Delivery events alongside cloud events.
- Infrastructure automation
Infrastructure as a governed workflow step.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how AWS fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.