Passwordless PostgreSQL and JIT diagnostics on AWS

Bastion Config 0.2.479 provides certificate-based application access and approved read-only diagnostic windows for self-managed PostgreSQL 18 on EC2 in your AWS account.

Separate approval and a configured policy bound DBA diagnostics. Application revocation blocks new connections after propagation; existing sessions are separate.

Start with fit

Is Bastion right for your PostgreSQL environment?

Release 0.2.479: self-managed PostgreSQL 18 on EC2, using a supported deployment and application integration. Answer these five questions before planning an evaluation.

  1. Where does PostgreSQL run?

    The current offer is for self-managed PostgreSQL on EC2. RDS, Aurora and other managed PostgreSQL services are outside the supported scope.

  2. Which version and application integration do you use?

    Confirm PostgreSQL 18, your runtime and driver. Documented client integrations include Java, TypeScript/Node and Rust; other combinations need verification.

  3. Which access problem do you want to solve?

    Choose certificate-based application access, withdrawal of application access, certificate operations or approved read-only DBA diagnostics.

  4. Who will operate it, and what support do you need?

    Name the owner for access, alerts, backups and recovery. Email support is in English, Monday-Thursday, US Pacific; first-response target is 5 business days, with no SLA or 24/7 coverage.

  5. Can you evaluate it in non-production?

    Choose one application and an allowed query. Agree on pass/fail evidence before considering production adoption.

Managed services and unverified combinations need a scope discussion. If guaranteed response times or round-the-clock support are required, review that requirement before evaluating. A positive fit check is not a compatibility guarantee.

Sending is voluntary and opens your email app. No form submission or account is required. Do not include secrets or customer data.

Buyer resources

A small evaluation with clear evidence

Start with one application

  1. Confirm the supported deployment and client integration; name the operating owner.
  2. Demonstrate a successful connection and an allowed query.
  3. Withdraw the identity's access; record refusal of a new connection after propagation. Treat existing sessions separately.
  4. If JIT is required, request a window, obtain separate approval and check an allowed and a denied statement.
  5. Test rotation and recovery only where supported; record results and responsibilities. No continuity or recovery-time guarantee is implied.

The 30-day trial covers software under Marketplace terms; AWS infrastructure charges still apply. You operate the installation. Backups and recovery availability depend on the deployment method.