Elastic Cloud

QuotaGuard routes your application's Elastic Cloud traffic through the two fixed IPv4 addresses assigned to its subscription. Add both addresses to an Elastic ingress IP filter and associate that organization-level policy with the intended deployment or project. QuotaGuard has provided static-IP proxy service since 2013.

• Two-Minute Setup: Store the QuotaGuard connection URL as an environment variable, configure the HTTP client used for Elastic Cloud requests to use the proxy, and register both dashboard IPs as allowed sources. The existing QuotaGuard Elastic Cloud technical guide carries the client-specific implementation details.
• Elastic Policy-Aware: Elastic creates IP filters at the organization level and enforces them only after they are associated with a Hosted deployment or eligible Serverless project. Policies accept IPv4 addresses or CIDR ranges, not domain-based sources.
• Multi-Platform Support: Works on Heroku, Render, Railway, Fly.io, AWS Lambda, Vercel, Netlify Functions, Kubernetes, and direct VPS hosts. The Elastic policy sees the QuotaGuard source pair rather than each platform's dynamic egress.
• Production-Grade Reliability: Each subscription receives two load-balanced static IPs with health checks and automated failover. Add both to the Elastic policy so either approved route can reach the resource.
• Shield for Regulated Elastic Data: QuotaGuard Shield encrypts the customer-to-proxy hop while preserving the application's HTTPS session to Elastic without decrypting its payload. Use it when QuotaGuard's regulated-data position or an internal control requires that additional protected hop; it does not make the workload compliant by itself.

Policy scope note: Elastic policies are region-bound and resource-type-specific, and Elastic Cloud Hosted's managed OTLP endpoint is not covered by an IP filter. Confirm current Serverless eligibility in the Elastic Cloud Console because Elastic’s official pages currently describe the required packaging differently.