AWS Ping Identity
Demo home

Northline Bank on AWS, secured by PingOne

Pick a stage to see what each step adds, play a flow to follow a request, or select any service for details.

Stage
Play a flow
Northline Bank on AWS, secured by PingOne Customers reach Northline through Amazon CloudFront. Static files come from Amazon S3; pages and APIs go through Amazon API Gateway to AWS Lambda, which keeps its session key in AWS Secrets Manager and logs to Amazon CloudWatch. The browser runs PingOne DaVinci sign-in flows embedded in the page, using PingOne MFA passkeys, PingOne Verify for identity checks at account opening, PingOne Recognize for the selfie match at recovery, and PingOne Protect for bot detection. Lambda exchanges sign-in codes with PingOne SSO. An AI browser agent is blocked by PingOne Protect. Claude Code with Ping agent skills builds each step, Terraform deploys AWS and PingOne, and the PingOne MCP server lets the agent check its work. AWS Cloud ยท us-east-1 PingOne Built headlessly by an AI coding agent Customer browser Northline web app Pages and APIs Embedded sign-in Route 53 + ACM DNS, TLS certificate Amazon CloudFront Edge, HTTPS, headers Amazon S3 Static files and SDKs Amazon API Gateway HTTP API, throttling AWS Secrets Manager Session signing key 1 AWS Lambda Sessions and tokens Amazon CloudWatch Logs and metrics PingOne DaVinci Embedded sign-in flows 1 PingOne Verify ID + selfie check 2 PingOne MFA Passkeys, email codes 1 PingOne Protect Bot and AI-agent risk 3 PingOne SSO OIDC tokens, users 1 PingOne Recognize Selfie match, recovery 2 PingOne MCP server Agent access, audit Customer phone Verify ID + selfie AI browser agent Blocked by Protect Git repository One tag per step Terraform aws + pingone providers Ping agent skills PingOne, DaVinci, SDKs Claude Code Your coding agent
Scroll sideways to see the whole diagram.