Reveille on AWS — Cloud-Native Content Observability | Reveille
Deployment · Amazon Web Services

Run Reveille inside your AWS cloud — independent of the platform vendor.

Your Enterprise Content Management (ECM), Intelligent Document Processing (IDP), and automation platforms moved to AWS. The workflows running on them still need an independent watcher. Reveille operates inside your AWS environment — on your EC2 compute, your Amazon RDS databases, and your AWS Secret Manager — then feeds the CloudWatch stack your team already uses. Independent of the platform vendor. Native to the cloud.

Request a Demo Read the Technical Overview
Native to your cloud EC2 · RDS · S3 · CloudWatch Deployment-agnostic by choice
At a glance · Reveille on AWS

Content Observability that runs natively on AWS — the facts.

  • Compute
    Runs on AWS EC2 Windows VM instances
  • Database
    Amazon RDS — SQL Server, Oracle, PostgreSQL, and Aurora-compatible PostgreSQL
  • Storage
    Monitors Amazon S3 bucket performance and availability
  • Native services
    CloudWatch, CloudWatch Logs, SNS, RDS, and S3
  • Containers
    Reveille collectors run as sidecars in Amazon EKS
  • Topology
    Reveille and your content platform in any mix — both in AWS, split, or hybrid
  • Security
    FIPS-compliant AES-256; credential key stored in AWS Secret Manager
  • Independence
    Independent of your ECM/IDP cloud vendor; native to AWS
How it deploys

One observability layer, wherever your content lives.

Reveille is deployment-agnostic by choice. Run it entirely in AWS, split it across the cloud boundary, or span a hybrid estate — the collectors carry the content-layer signal back to the Reveille server over a compressed, encrypted TLS session, and out to the AWS services you already operate.

AWS CLOUD Users & content apps Reveille collectors Reveille server on EC2 Amazon CloudWatch Metrics + CloudWatch Logs Amazon SNS Alert & incident notifications Amazon RDS SQL Server, Oracle, PostgreSQL Amazon S3 Bucket performance & availability TLS
01

Fully in AWS

Reveille and your content platform both run in AWS. The Reveille server and collectors live on EC2, the databases on Amazon RDS — one cloud-native estate, watched from inside.

02

Split across the boundary

Reveille collectors in AWS with the Reveille server on-premises, or the reverse. Collectors send data compressed and encrypted over TLS, with an optional client-side certificate.

03

Hybrid estate

Content on-premises or in another cloud, Reveille in AWS — or any mix. The same observability layer crosses the boundary single-vendor monitoring stops at.

Native AWS services

Reveille speaks the AWS stack you already run.

Reveille doesn’t bolt a separate console onto your cloud. It generates the content-layer signal your AWS observability tools can’t produce on their own, then feeds it straight into the services your team already operates.

Amazon CloudWatch

Publish Reveille metrics to CloudWatch dashboards so content-layer health sits alongside the rest of your AWS telemetry.

Amazon CloudWatch Logs

Stream Reveille events into CloudWatch Logs for centralized search, retention, and correlation.

Amazon SNS

Route Reveille alert and incident notifications through Simple Notification Service to the channels your responders watch.

Amazon RDS

Host the Reveille and User Analytics databases on managed RDS — SQL Server, Oracle, PostgreSQL, and Aurora-compatible PostgreSQL.

Amazon S3

Monitor S3 bucket storage performance and availability, so the object storage your content depends on is observed too.

Amazon EKSContainers

Run Reveille collectors as sidecar containers alongside your application pods, using Windows or Linux OCI-compatible images.

AWS Secret ManagerSecurity

Store the Reveille credential encryption key in an external vault. Credentials are encrypted at rest with FIPS-compliant AES-256.

OAuth 2 & REST APIs

170+ Reveille REST API methods with OAuth 2 authorization through OpenID-compliant providers integrate Reveille data into your AWS-hosted apps.

Independent by structure

Reveille operates inside your AWS cloud — and answers to you.

Native to the cloud. Independent of the vendor. Reveille is the only observability layer not built, sold, or operated by the platforms it measures. Platform SLA is not workflow SLA — and your vendor can’t grade their own homework.

Other ways to deploy

Same observability layer, every environment.

Microsoft Azure SQL, Monitor, Sentinel, Blob Google Cloud Cloud SQL, Storage, Logging On-prem · Hybrid · Private Cloud Traditional & mixed estates
Questions

Reveille on AWS — answered.

Does Reveille run on AWS?
Yes. Reveille supports operation on Amazon Web Services (AWS) EC2 Windows VM instances, with full capability inside the AWS environment. Reveille uses native AWS services including Amazon CloudWatch, CloudWatch Logs, Amazon Simple Notification Service (SNS), Amazon RDS, and Amazon S3.
Which AWS database services does Reveille support?
Reveille supports Amazon Relational Database Service (RDS) with database authentication for SQL Server, Oracle, PostgreSQL, and Aurora-compatible PostgreSQL. These can host both the Reveille and Reveille User Analytics databases.
Can Reveille monitor Amazon S3?
Yes. Reveille monitors Amazon S3 bucket storage performance and availability, so the object storage your content services depend on is observed alongside the rest of the workflow.
Does Reveille integrate with Amazon CloudWatch and SNS?
Yes. Reveille publishes its metrics to Amazon CloudWatch, sends events to Amazon CloudWatch Logs, and routes alert and incident notifications through Amazon Simple Notification Service (SNS). The content-layer signal Reveille generates flows into the AWS observability stack your team already uses.
Can Reveille run in containers on AWS?
Reveille collectors run as sidecar containers in Amazon Elastic Kubernetes Service (EKS) using Windows or Linux OCI-compatible images, and the Reveille Platform collector runs as a separate Linux OCI container. The Reveille Platform server itself runs on an AWS EC2 Windows VM rather than in a container, because of third-party ECM/IDP system API dependencies.
Does Reveille have to run in the same cloud as my content platform?
No. Reveille is deployment-agnostic. You can run Reveille and your content platform both in AWS, run Reveille collectors in AWS with the Reveille server on-premises (or the reverse), or span a hybrid estate. Reveille collectors bridge the boundary, sending data compressed and encrypted over an HTTP/HTTPS TLS session with an optional client-side certificate.
How does Reveille secure credentials on AWS?
Reveille encrypts all application credentials in its database with a FIPS-compliant AES symmetric algorithm using a 256-bit key. The Reveille Key Manager can store the credential encryption key in an external vault such as AWS Secret Manager, and the Reveille REST APIs support OAuth 2 authorization across 170+ methods.

The content layer is where your business runs. Reveille makes sure it holds.

See Content Observability running inside your AWS cloud — on your compute, your databases, your services.

Request a Demo Read the Technical Overview