NGINX REVERSE PROXY

nginx and Reverse Proxy Architecture, Las Vegas NV

nginx and Reverse Proxy Architecture, Las Vegas NV — Las Vegas NV
nginx and Reverse Proxy Architecture, Las Vegas NV

Reverse proxy design for regulated web estates: TLS termination, header hygiene, rate limiting, upstream health, and logging that survives review.

Where TLS terminates

Termination point determines where the audit trail begins; decide it deliberately rather than by default.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Header hygiene

Forwarded headers are trusted input; a proxy that believes them lets a client choose its own identity.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Rate limiting

Limits protect availability and slow credential stuffing; undocumented limits break legitimate clients.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Upstream health and failover

Health checks that test the socket and not the application produce confident failovers into broken backends.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Static and cache strategy

Caching is a correctness problem in a regulated estate, not only a performance one.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Access logs as evidence

Log format must capture who, what, when and outcome, and retention must outlast the investigation window.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Certificate lifecycle

Expiry is the most common outage in a well-run estate; automate it and monitor from outside.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Configuration as reviewable text

One file per concern, version controlled, with the diff as the change record.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Termination point decides the audit trail

Where TLS terminates determines where identity is established and where the log begins. Terminate at the edge and every upstream trusts a header; terminate deeper and the edge must pass the connection through without rewriting it. Either is defensible and the choice must be deliberate, because the default is an accident.

Forwarded headers are trusted input. A proxy that believes X-Forwarded-For from an untrusted source lets any client choose its own address, and every downstream rate limit and audit record inherits the fiction.

Access log format is a control, not a preference: who, what, when, and the outcome, with retention that outlasts the investigation window. A log that rotates in seven days cannot answer a question asked in week three.

Health checks that mean something

A health check that tests the socket and not the application produces confident failovers into a broken backend. Check the endpoint that proves the service works, and treat a 500 as unhealthy even when the port accepts connections.

Rate limiting protects availability and slows credential stuffing; undocumented limits break legitimate clients. Publish the limit, return a documented 429 with a retry contract, and keep the exceptions list small and owned.

Certificates belong to automation with an external check, because the internal one tests the estate's opinion of itself — and it shows green while a browser shows an expiry warning.

Upstream failure should be visible before it is fatal

A backend that is up but slow passes a socket check and fails a clinician. Health checks that measure the application's own response, with a timeout shorter than the client's patience, convert a slow failure into a fast one — which is the whole value of a proxy.

Log the upstream response time separately from the total, so a slow dependency can be distinguished from a slow client. That single split resolves most arguments about where the latency lives.

And version the configuration with the change record. A proxy config edited in place during an incident is a config nobody can reproduce afterwards, which is precisely when you need to.

What the proxy is actually protecting

Three things and no more: the certificate boundary, the rate boundary and the logging boundary. Everything else a proxy can do — compression, caching, header rewriting — is either an optimisation or a way to introduce a defect that takes a week to diagnose.

Keep the configuration small and readable. One file per concern, version controlled, with the diff as the change record. Proxy configs grow into archaeology because each incident adds a line and none remove one.

Test from outside after every change, because the internal check passes through a different path than the customer's request and the two disagree exactly when it matters.

Where this work is delivered

Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide. Las Vegas, Nevada 89101.

How an engagement runs

1. Trace one real case

Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.

2. Written findings

A findings list naming the defect, the system, the owner and the date.

3. Monthly review

Review the list monthly and check whether the dates held.

Frequently asked

What is this service?

This page describes nginx and Reverse Proxy Architecture, Las Vegas NV — the scope, the failure modes it prevents and how the work is measured. It sits in the Cloud and Operations category at trinh.io.

Where is the work delivered?

Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.

What does it cost?

Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.

Who is Charles Trinh?

A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.

How does an engagement start?

With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.

Engagement

Available for architecture review, conformance work and fractional leadership. Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more.

Talk to Charles

702-559-3489 · charles@trinh.io

Proof

  • ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
  • 67 public hostnames, 51 serving, one AWS account
  • 104 clearinghouse enrolments across 53 jurisdictions
  • USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
  • AWS Business Associate Addendum active since 18 August 2026
TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh

Record

Profile

Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.

Selected engineering scale

  • Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
  • FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
  • Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
  • X12 005010 pipelines across eight transaction sets.
  • Designed, built, deployed and operated end to end by one person.

Credentials and standards work

  • Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
  • USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.

Technical environment

AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.