Overview
Elevarq Signals is an open-source (BSD-3-Clause) diagnostic collector for PostgreSQL that runs entirely inside your own AWS environment. It connects to a managed database, collects a structured, read-only diagnostic snapshot on a schedule, and keeps every byte local — no telemetry, and no diagnostic-data egress to Elevarq.
Your data stays in your account
- The only outbound calls are the cloud-authentication and TLS requests you configure, made to your own AWS services.
- Snapshots are written locally and exported as a portable archive for downstream analysis.
Read-only by design
- Read-only access is enforced by three independent layers.
- Unsafe roles (superuser, replication) are blocked before collection begins.
Passwordless onboarding on Amazon RDS and Aurora
- Connect with RDS IAM authentication — no long-lived database password to store or rotate.
- Or use a cloud secret store: AWS Secrets Manager or AWS Systems Manager Parameter Store.
- Every connection uses verify-full TLS and a least-privilege pg_monitor role.
Production-ready packaging
- Signed, multi-architecture container (linux/amd64 and linux/arm64), shipped with an SBOM.
- Helm chart for Amazon EKS with liveness/readiness probes, least-privilege security contexts, and a persistent volume for local snapshots.
Highlights
- Read-only by design: three independent enforcement layers, with unsafe roles (superuser, replication) blocked before collection starts
- Passwordless onboarding to Amazon RDS and Aurora via RDS IAM (or a cloud secret store) over verify-full TLS with a least-privilege pg_monitor role
- Local-first: no telemetry and no diagnostic-data egress to Elevarq; signed multi-arch container and Helm chart for Amazon EKS
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Vendor refund policy
This product is offered free of charge. There are no fees and therefore no refunds. Support is community-based via GitHub Issues at https://github.com/Elevarq/Signals .
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Container image (Amazon ECS / Fargate)
- Amazon ECS
Container image
Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.
Version release notes
Patch release. Go toolchain updated to 1.26.5 (remediates GO-2026-5856). The container writes its SQLite/WAL database under /data as non-root UID/GID 10001; ensure the mounted volume is writable by that user. See the usage instructions for durable-storage requirements on Amazon ECS and Fargate.
Additional details
Usage instructions
Elevarq Signals 1.0.1 - container image for Amazon ECS / Fargate.
Signals is a read-only PostgreSQL diagnostic collector. It connects to your database, collects diagnostic signals on a schedule, stores them in a local SQLite database under /data, and produces snapshot exports. It sends no telemetry to Elevarq.
Durable storage (required). The container persists its SQLite database and snapshots under /data. On AWS Fargate the task filesystem is ephemeral, so attach an Amazon EFS volume mounted at /data. On EC2-backed ECS you may instead use an EBS-backed or bind-mount volume. Without a durable volume, collected data and snapshots are lost when the task stops. The container runs as non-root UID/GID 10001 with a read-only root filesystem, so the mounted /data volume must be writable by UID/GID 10001 (for EFS, set the access point POSIX user to 10001:10001).
-
Subscribe on AWS Marketplace to grant your account pull access to the Marketplace ECR repository.
-
Reference the image in your ECS task definition: 709825985650.dkr.ecr.us-east-1.amazonaws.com/elevarq/elevarq-signals:1.0.1 The task execution role needs ECR pull permission for the Marketplace repository.
-
Configure the target database via environment variables (for example SIGNALS_ENV, the target host, dbname, and user, authMethod aws_rds_iam, sslmode verify-full). Provide the RDS CA bundle, and for passwordless RDS IAM an IAM task role with rds-db:connect. See the product documentation.
-
Mount durable storage at /data (EFS on Fargate; EBS or bind mount on EC2-backed ECS), writable by UID/GID 10001.
-
Complete the one-time database role grant (CREATE ROLE signals, GRANT rds_iam, GRANT pg_monitor) per the product documentation.
Resources
Vendor resources
Support
Vendor support
Community support via GitHub Issues at https://github.com/Elevarq/Signals . Report security vulnerabilities to security@elevarq.com (see SECURITY.md).
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.