What to Do When You Have Duplicate AWS Candidate IDs
Duplicate AWS Candidate IDs split exam history, delay renewals, and break certification audits. Here's how to identify, merge, and prevent them.
At Sapior, we see duplicate AWS Candidate IDs mostly when an engineer has one foot in a corporate identity provider and another in a personal email. It is not a naming problem; it is an identity problem. AWS Training and Certification treats each unique login and email combination as a separate profile, so exam history and continuing education can split across two or more Candidate IDs.
What an AWS Candidate ID actually is
An AWS Candidate ID is the identifier AWS Training and Certification uses to connect Pearson VUE exam attempts, certification records, and continuing education credits to a single person. You can find it in your AWS Certification account, on old exam confirmation emails, and in some Credly badge metadata.
Duplicate IDs usually appear when:
You used a personal email for an old exam and a work email for a new one.
You signed in through AWS Skill Builder separately before using Partner Central or Pearson VUE.
Your company changed SSO providers and the new identity did not map to the original AWS profile.
A contractor or vendor registered on your behalf with a slightly different name or email variant.
Why duplicates are dangerous
The failure is silent until an audit or renewal. One profile may hold an active certification while the other holds the required continuing education credits. Security teams see a fully qualified person, but AWS sees two incomplete records.
Common downstream impact includes:
Split certification history across multiple Candidate IDs.
Continuing education credits that do not aggregate.
Partner program compliance failures when validating certified individuals.
Slow renewal or recertification workflows.
Confusion during background checks or client audits that verify a specific Candidate ID.
How to fix duplicate AWS Candidate IDs
Do not create another account. That makes the problem worse.
1. Collect every Candidate ID
Look at your AWS Certification account, old Pearson VUE emails, Credly badge history, and any internal credential inventory. Record each ID and the email associated with it.
2. Choose the canonical profile
Pick the profile that should survive. Prefer the one tied to your current work email, APN Partner Central, or the profile with the most complete certification history and continuing education credits.
3. Open an AWS Training and Certification support case
Open a case under the AWS Training and Certification or AWS Certification account area. Use a clear subject such as `Duplicate AWS Candidate ID merge request`.
Provide:
All known Candidate IDs.
The email address used for each profile.
Your legal name as it appears on government ID.
The canonical profile you want to keep.
Any old exam confirmation numbers or Credly badge URLs.
AWS Support will verify ownership and submit the merge or consolidation request. Do not post identity documents in public forums or chat threads.
4. Wait for the merge to complete
The timing depends on AWS and Pearson VUE. Most requests finish within a few business days after identity verification. After the merge, check your AWS Certification account to confirm exam history, active certifications, and continuing education credits all appear under one Candidate ID.
5. Reconnect downstream systems
If you use Credly, BadgeCert, an internal LMS, or a partner compliance tool, refresh the profile after the merge. Some badge acronyms and APIs may still reference the old ID for a short time.
How Sapior sees it
At Sapior, we treat AWS Candidate IDs as identity data, not just a support ticket detail. Teams should monitor for duplicate profiles before audits, not after. Standardize the login method, map candidate IDs to your identity provider, and audit certification data on a regular cadence. That prevents the quiet drift where one person becomes two records in AWS.
Preventing future duplicates
Use a single email address for AWS Training and Certification, Pearson VUE, Credly, and Partner Central. Prefer corporate SSO where available. If your email changes, update the existing AWS Certification profile instead of creating a new one. When onboarding contractors, use existing accounts instead of opening new ones.
Duplicates are fixable, but only if AWS sees a clear, verifiable path back to one canonical identity.