Case study

Digital Umbrella. Reviewed and live.

TNA Pro scopes an engagement, prices it, and produces the architecture and scope of work — sold through AWS Marketplace to other AWS partners. It went through the AWS Foundational Technical Review with zero high-risk issues, and it is live.

Practice AWS Cloud · DevOps Engagement Product build · multi-tenant SaaS Status Delivered · FTR passed · live on Marketplace
FTR high-risk issues
0
The AWS Foundational Technical Review passed with none outstanding.
Long-lived credentials
0
No standing AWS credential exists anywhere, on any machine.
Deployment paths
1
Deploys run from the pipeline only. There is no local path to production.
Marketplace
Live
Sold to other AWS partners through AWS Marketplace.
The brief

An internal tool is not a product.

The tool worked. It had been used internally for real engagements and was correct for that job. Selling it to other AWS partners was a different proposition, and the gap was not features — it was the assumptions underneath.

An internal tool can resolve a customer by hostname, keep preferences on the machine that set them, and push results into a system every user happens to share. A product sold on a marketplace can do none of those things. It has to provision a stranger in seconds, keep their data provably separate from everyone else’s, and survive them changing laptop.

It also has to pass a review. The AWS Foundational Technical Review is a gate for anything listed on Marketplace, and it is assessed by someone other than the people who built it.

What we did

Six decisions that carried the product.

Chose pooled tenancy, deliberately

A Marketplace subscription has to provision a tenant in seconds, which rules out a project per customer. Pooled was the requirement talking, not a preference — and the alternative was documented so the decision stays legible later.

Made tenant isolation a rule, not a habit

Tenant identity is taken from the verified token and never from a request body, a query string, or a hostname — a Host header is client-controlled. One function builds the partition key, so a handler that accepts a tenant id as an argument is a bug you can find by searching.

Wrote the test that fails on a leak

The suite includes an isolation test that fails if one tenant can see another. Multi-tenancy claims are cheap; a test that breaks the build is not.

Removed the human deployment path

Deploys run only from the pipeline, with no long-lived AWS credential on any laptop. The fastest way to lose a customer’s data is a standing key on a machine that leaves the building.

Defined every resource as code

The whole environment is one template. Nothing in production was created by hand, so what is running can always be traced to what was reviewed.

Built the Marketplace integration properly

Registration, entitlement, and subscription events handled as first-class paths, so a subscription, an upgrade, or a cancellation lands as a change in the product rather than a support ticket.

The outcome

Assessed by someone else.

TNA Pro passed the AWS Foundational Technical Review with zero high-risk issues, and is live on AWS Marketplace. That is the part worth stating plainly: the review is external, the criteria are not ours, and the result is a matter of record rather than a description we wrote about our own work.

The brief

The person you brief is the person who solves it.

One conversation · 30 minutes · no monologue