Reversible PII de-identification round trip (T1–T7) #1
Reference in New Issue
Block a user
No description provided.
Delete Branch "feat/deid-round-trip-t1-t7"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Builds the AWS side of the HNCB reversible PII de-identification demo end to end (region
ap-southeast-1). Advisor query with a real name → tokenized before it leaves for the cloud → AgentCore agent reasons on tokens only → identity restored on-prem before the advisor sees the answer.Tasks (all live-verified)
/tokenize+ T2/restore— Lambdas behind a public API Gateway (shared-secret auth), Presidio detection, random per-request tokens, DynamoDB vault. Overlap resolution keeps a ROC ID asTW_ROC_ID(notPERSON)./tokenize+/restoreare public.agentcore_setup.sh+ a SigV4 MCP invoke test./demo) chaining tokenize → runtime → restore.The money shot
In the cloud AgentCore/Bedrock trace for a run, the token
CUST_*appears in 13 events while the real name王小明and ROC ID appear in 0 — the cloud only ever saw tokens.Notes
/demoorchestrator only stands in for the Fusion-less dry run.terraform/local.auto.tfvars; no creds/PII committed.scripts/teardown.shto stop spend.🤖 Generated with Claude Code