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
Helm chart (Amazon EKS)
- Amazon EKS
Helm chart
Helm charts are Kubernetes YAML manifests combined into a single package that can be installed on Kubernetes clusters. The containerized application is deployed on a cluster by running a single Helm install command to install the seller-provided Helm chart.
Version release notes
Elevarq Signals 1.2.0. Adds scheduled auto-export of a diagnostic snapshot to a configured file location after each collection cycle; exposes constraint validity (is_validated, from pg_constraint.convalidated) in the pg_constraints_v1 collector so NOT VALID constraints are visible; and Helm chart support for multiple PostgreSQL targets in one release. Fixes the FC-05 false-clean export gap: an export with no successful collection is refused (HTTP 422) instead of returning an empty clean snapshot.
Additional details
Usage instructions
Elevarq Signals 1.2.0 - Helm chart install on Amazon EKS.
The chart enables persistence by default, so a fresh EKS cluster needs the Amazon EBS CSI driver and a StorageClass before install.
-
Subscribe on AWS Marketplace to grant your account pull access to the Marketplace ECR repositories.
-
Prepare durable EBS storage. Install the EBS CSI driver via IRSA and create an encrypted gp3 StorageClass:
eksctl utils associate-iam-oidc-provider --cluster <cluster> --region us-east-1 --approve eksctl create iamserviceaccount --cluster <cluster> --region us-east-1 --namespace kube-system --name ebs-csi-controller-sa --role-name signals-ebs-csi-<cluster> --role-only --attach-policy-arn arn:aws:iam::aws:policy/service-role/AmazonEBSCSIDriverPolicy --approve eksctl create addon --cluster <cluster> --region us-east-1 --name aws-ebs-csi-driver --service-account-role-arn arn:aws:iam::<account>:role/signals-ebs-csi-<cluster> --force --wait
Then create a StorageClass named signals-gp3 (provisioner ebs.csi.aws.com, volumeBindingMode WaitForFirstConsumer, allowVolumeExpansion true, parameters type gp3 and encrypted true).
- Authenticate Helm to the Marketplace registry:
aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin <marketplace-ecr-registry>
- Install the chart. Put config in signals-values.yaml (target host, dbname, user; authMethod aws_rds_iam; sslmode verify-full; and persistence.storageClass signals-gp3):
helm install signals oci://<marketplace-ecr-registry>/elevarq/elevarq-signals-chart --version 1.2.0 --namespace signals --create-namespace -f signals-values.yaml
- Wait for storage and workload readiness:
kubectl -n signals wait --for=jsonpath='{.status.phase}'=Bound pvc/signals-signals-data --timeout=5m kubectl -n signals rollout status deployment/signals-signals --timeout=5m
- Verify. The Deployment is named <release>-signals, so with release name signals it is signals-signals:
kubectl -n signals exec deployment/signals-signals -- signalsctl status kubectl -n signals exec deployment/signals-signals -- signalsctl export --output /data/snapshot.zip
Signals connects passwordless over verify-full TLS with a least-privilege pg_monitor role and sends no telemetry to Elevarq. 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.