Skip to content
NexusBook a demo

Critical infrastructure use case · Amazon Web Services + Snowflake + ServiceNow

Cloud event to analytics workflow

Cloud telemetry is either analysed or acted on, rarely both. Cloud events are enriched, loaded for analysis and escalated when thresholds are crossed.

Systems involved

What each system contributes

  • EC215
  • S315
  • IAM21
  • Lambda10

Trigger source: AWS S3, AWS SNS, AWS SQS, AWS CloudWatch, AWS CloudWatch Events

Snowflake

35 actions

  • Data Loading & Stages8
  • Tasks & Scheduling7
  • Tables6
  • Views6
ServiceNow

55 actions

  • Incidents12
  • Tickets10

Trigger source: ServiceNow

Architecture

One governed run

Trigger: AWSIntegration: AWSRules + CodeSystem Action: SnowflakeHuman ApprovalAudit

How it starts: AWS CloudWatch, CloudWatch Events, S3, SNS or SQS starts the run.

Step by step

How the process runs

  1. 01

    Event

    The AWS event arrives. EC2, S3, IAM and Lambda actions add context.

  2. 02

    Load

    Snowflake data loading actions load the enriched event. Tasks update tables and views.

  3. 03

    Threshold

    Rules + Code checks thresholds and opens a ServiceNow incident or ticket if crossed.

  4. 04

    Remediate

    Any AWS remediation waits for approval.

Control

Human decision and exception path

Human decision

An operations engineer approves any remediation before it runs in AWS.

Exception path

  • Duplicate events are grouped.
  • Failed loads are retried.
  • Remediation failures reopen the incident.

Evidence

What gets audited

  • Event.
  • Enrichment.
  • Load result.
  • Incident, approval and remediation output.

Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.

Sovereignty and deployment

Related

Patterns, connectors and next steps

FAQ

Questions about this use case

Does Nexus replace any of these systems?
No. Each system keeps its own records. Nexus runs the process between them and records each decision.
How does the run start?
AWS CloudWatch, CloudWatch Events, S3, SNS or SQS starts the run.
What if a step is not covered by a pre-built action?
It runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.

Use case review

Discuss this use case

Bring your version of the process. We will map the systems, approvals and evidence it needs.