anomalyco/sst · error · VisibleError

Reader endpoint is not currently supported for RDS Proxy. Pl

Error message

Reader endpoint is not currently supported for RDS Proxy. Please contact us on Discord or open a GitHub issue.

What it means

The `reader` getter on the Aurora component returns the reader endpoint of the cluster. When an RDS Proxy is configured for the cluster, SST does not support routing reads through the proxy's reader endpoint, so it throws this VisibleError instead of returning a wrong value. The message asks users to report the need on Discord/GitHub so maintainers can prioritize support.

Source

Thrown at platform/src/components/aws/aurora.ts:1251

  /**
   * The host of the database.
   */
  public get host() {
    if (this.dev?.enabled) return this.dev.host;
    return all([this.cluster!.endpoint, this.proxy!]).apply(
      ([endpoint, proxy]) => proxy?.endpoint ?? output(endpoint.split(":")[0]),
    );
  }

  /**
   * The reader endpoint of the database.
   */
  public get reader() {
    if (this.dev?.enabled) return this.dev.host;
    return all([this.cluster!.readerEndpoint, this.proxy!]).apply(
      ([endpoint, proxy]) => {
        if (proxy) {
          throw new VisibleError(
            "Reader endpoint is not currently supported for RDS Proxy. Please contact us on Discord or open a GitHub issue.",
          );
        }
        return output(endpoint.split(":")[0]);
      },
    );
  }

  public get nodes() {
    return {
      cluster: this.cluster,
      instance: this.instance,
    };
  }

  /** @internal */
  public getSSTLink() {
    return {

View on GitHub (pinned to a0bd20f762)

Solutions

1. Remove the `proxy` option from the Aurora component args so `reader` returns the cluster reader endpoint directly
2. Access `aurora.cluster.readerEndpoint` (parse host) directly instead of `aurora.reader` when a proxy is configured
3. Disable the proxy temporarily until RDS Proxy reader support is added, or file/upvote the GitHub issue

Example fix

// before
new sst.aws.Aurora("MyDB", { proxy: true });
const host = aurora.reader;
// after
new sst.aws.Aurora("MyDB", {});
const host = aurora.reader;

if (aurora.args?.proxy) {
  throw new Error("Use cluster.readerEndpoint directly; reader is unsupported with RDS Proxy.");
}
const readerHost = aurora.reader;

function supportsReader(a: { proxy?: unknown }): boolean {
  return !a.proxy;
}

When it happens

Trigger: Accessing `aurora.reader` while `proxy` is enabled in the Aurora component args (e.g. `rds.Proxy` created and passed in), in a non-dev (deployed) stage. In dev mode (`sst dev`) it returns `dev.host` without hitting this check.

Common situations: Developers add an RDS Proxy for connection pooling and then try to read the reader endpoint for read replicas; upgrading SST with a proxy config from an earlier version.

Related errors

• Proxy is not enabled. Enable it with "proxy: true".
• Database instance not found in cluster ${cluster.id}
• Failed to get password for Postgres ${name}.
• Cannot configure "pauseAfter" when the minimum ACU is not 0
• Cannot create more than 15 read-only replicas for the "${nam

AI-assisted analysis of anomalyco/sst@a0bd20f762 (2026-08-30). Data as JSON: /api/errors/ec836221cbde39e2. Report an issue: GitHub.