Infisical adds honey tokens for AWS

This is a sharp move because it turns one of the most dangerous leak types, an AWS key, into a detection tripwire instead of just another secret to rotate later.

• –AWS is a sensible first target: IAM keys are valuable bait, CloudTrail gives a reliable signal, and even an unauthorized `GetCallerIdentity` attempt is enough to raise an alarm
• –Infisical’s choice to mint the bait in the customer’s own AWS account is the important bit; it makes the token harder to fingerprint than vendor-hosted canaries
• –The feature is detection, not prevention, so the value depends on fast alerting and disciplined rotation once a token is triggered
• –The positioning is good for security teams that want a higher-confidence compromise signal than passive secret scanning alone
• –The obvious limitation is scope: this starts with AWS IAM, so broader credential types will matter if Infisical wants this to become a generic breach-detection layer