Implement AWS Rekognition Face Liveness detection to confirm a live selfie capture during identity onboarding
domain: docs.aws.amazon.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call CreateFaceLivenessSession to start a session, configuring Settings.ChallengePreferences (defaulting to FaceMovementAndLightChallenge) and Settings.AuditImagesLimit (0-4)
Pass the returned SessionId to your client application to run the liveness capture using the Amplify UI or AWS-provided face-liveness component
After capture completes client-side, call GetFaceLivenessSessionResults with the SessionId to retrieve the outcome
Read the Status field (CREATED, IN_PROGRESS, SUCCEEDED, FAILED, EXPIRED) and the Confidence score before accepting the capture as live
Persist the reference image and any audit images alongside the decision for later dispute resolution or manual review
Known gotchas
A SUCCEEDED status alone isn't sufficient — pair the numeric Confidence score against your own threshold rather than treating success as binary
Sessions expire; calling GetFaceLivenessSessionResults too long after CreateFaceLivenessSession returns an EXPIRED status with no usable result
AuditImagesLimit only controls how many audit images are returned for review — set it above 0 if you need evidence images for manual dispute handling, since 0 returns none
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?