Charles Trinh · Las Vegas, Nevada · AWS healthcare architecture

Charles Trinh - AWS healthcare architecture in Las Vegas, Nevada

The BAA is the beginning of the work, not the end of it. Signing it does not make a workload compliant; the services you chose and the way you configured them do.

Charles Trinh designs AWS architectures for regulated workloads from Las Vegas, Nevada: which services are in BAA scope, how keys and identities are separated, what the audit trail captures, and what the monthly bill will be before it arrives.

Charles Trinh - T markCharles Trinh · Las Vegas, Nevada · trinh.io
AWS healthcare architecture and HIPAA-eligible services, Las Vegas Nevada

Eligible is not configured

AWS publishes which services are covered by the business associate agreement. A covered service can still be deployed in a way that fails the requirement: an unencrypted volume, a public bucket, a log that is never reviewed.

The design names each service, its configuration baseline and the control it satisfies. That table is what a security review asks for and what a rebuild uses.

Identity and keys

One account per environment, roles rather than users, and keys that the workload can use without a human holding them. Rotation is automated or it does not happen.

Where protected data is encrypted, the key policy is part of the design: who can decrypt, under what condition, and what happens when that principal is removed.

The audit trail

CloudTrail, VPC flow logs and application logs are only evidence if they are retained, protected from modification and searchable. A log bucket the workload can delete is not an audit trail.

The design states the retention period, the access path and the query that answers the question 'who touched this record' within the response time the policy promises.

Cost that is defensible

Regulated architectures are usually over-provisioned because nobody measured. Right-sizing, storage tiering and a budget alarm turn the bill into a number that can be explained line by line.

The same discipline applies to the exit: what would it cost to leave, and which services create the lock-in. That answer belongs in the design, not in a post-mortem.

Sequencing a migration

Migrations fail on ordering more often than on technology. The first workload moved should be the one that proves the pattern - identity, network, logging, deployment - with the smallest possible blast radius.

After that the order is chosen by dependency and by risk, not by enthusiasm. Each wave has a rollback, a definition of done, and a person who signs off that the old path can be retired. Workloads that stay behind are documented as staying behind, with a reason.

How an engagement runs

It starts with a scoping call of thirty to forty-five minutes. The point is not to sell; it is to establish what decision has to be made, what constrains it, and whether this is the right kind of work for one architect rather than a team. If it is not, the call ends with a referral.

If it is, the next artefact is a written plan: scope, sequence, price and the evidence each step will produce. Nothing starts before that plan is agreed in writing, and nothing in it is a surprise later. Plans change, and when they do the change is written down with its effect on price and date.

Delivery runs in weekly checkpoints. Each one ends with something that exists: a document, a design, a working system, a test result. That is deliberate, because a programme that reports progress without artefacts is a programme that cannot be audited, handed over or defended.

Pricing and terms

Two shapes. A fixed price for a defined deliverable - an assessment, a design, a due-diligence report - where the scope is clear enough to price honestly. Or a monthly seat for continuing advisory work, with a set number of days and a standing slot for decisions.

Invoices are monthly, net fifteen, and the terms are the same for every client. There is no percentage of savings, no success fee and no commission from a vendor, because an advisor paid by the seller is not an advisor.

What to prepare before the first call

Nothing formal. What helps is a one-page description of the problem in your own words, the names of the systems involved, the deadline that is driving the timing, and who else has to agree before anything changes.

If a vendor proposal is already on the table, send it. Reading someone else proposal is often the fastest way to find the question nobody asked, and it costs nothing to look.

Why the written record matters

Every engagement leaves a record: the map, the decisions, the trade-offs that were rejected and why. That record is what makes a change of staff survivable, what an auditor reads, and what a buyer inspects. It is also the part most consultancies keep for themselves.

The record settles arguments. When a decision is questioned a year later, the note that states what was known, what was chosen and what it would cost to change is usually the only thing that ends the discussion.

Working in Las Vegas, Nevada

Las Vegas companies often run a small platform team against a national security review. The architecture has to be simple enough for three people to operate at two in the morning.

Scope and terms

Scope is a fixed number of hours per month or a defined project, agreed in writing before work starts. Every engagement carries a written plan, a weekly checkpoint, and a closing pack that states what was built, what was verified and what is left.

What the engagement produces

Services and expertise in Las Vegas, Nevada

Charles Trinh is a Las Vegas-based technology architect and fractional CTO/CIO serving health systems, payers, enterprises and government programmes in Nevada and nationally. Every discipline below is offered in ten engagement forms - consultant, architect, advisor, contractor, specialist, expert, services, support, solutions and consulting - so an engagement can be a review, a build, a retainer or an interim role.

The full catalogue, every discipline in all ten engagement forms, sits on the Las Vegas, Nevada services index. Delivery is remote-first from Las Vegas with on-site coverage across Clark County, and the same ten disciplines carry to engagements anywhere in the United States and in 264 countries.

TRINH - Charles Trinh, technology architect
Charles Trinh

Charles Trinh

Fractional CTO/CIO and Technology Architect - Las Vegas, NV

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

(702) 559-3489 Email Charles Trinh

TRINH

Services near me — Las Vegas, Nevada, the United States and worldwide

Serving customers in Columbus, Ohio, United States and worldwide.

Teams searching for AWS healthcare architecture near Las Vegas usually need the BAA question answered with a design, not a document library.

Questions about AWS healthcare architecture

Do you sign a BAA with AWS on our behalf?

No. The agreement is between the client and AWS; the architecture is designed to stay inside its scope.

Can you migrate an existing workload?

Yes, with a staged plan and a rollback for each stage.

Do you write Terraform or CloudFormation?

Either, if the engagement includes implementation.

How do you handle key management?

KMS with a documented key policy and rotation, or an HSM where the requirement demands it.

What does a design engagement cost?

A fixed price for a defined architecture and review.

trinh.io · Services · Las Vegas, Nevada · charles@trinh.io · 702-559-3489