AWS access-key identifier pattern appears in public content
ShipReady found an AWS access-key ID pattern in scanned page or script content.
Why it matters
An access-key identifier in public client content deserves prompt investigation because it may identify a credential that was included in a deployment.
How ShipReady detects it
What it inspects
ShipReady scans page content and fetched scripts for supported AWS access-key ID patterns while applying its general placeholder guard.
What triggers a finding
The rule triggers when it finds a non-placeholder string that matches the supported AWS access-key ID pattern.
What the evidence shows
The scanner observed a string matching an AWS access-key ID format in public content. Reports redact the value to a short prefix.
Limits of this check
An access-key ID is not a secret access key. ShipReady does not authenticate to AWS, validate the identifier, determine its account or permissions, or prove that it is active or usable.
How to fix it
Identify the deployment source
Locate the value in the source and build pipeline, then determine whether it is an intended non-secret identifier or an accidental credential reference.
Rotate through the owner-controlled process
If the identifier belongs to an exposed or uncertain credential, follow the organization's AWS credential-rotation process and remove it from public assets.
How to verify the change
Search deployed artifacts after remediation
Inspect generated client assets and relevant source history for the pattern after the fix.
Expected: Public artifacts no longer contain unintended AWS access-key identifiers.