AWS Bedrock access has been locked for over 30 days—how can I escalate?

Treat the compromised credential as permanently exposed. Revoke it, create replacement credentials through the proper IAM process, and make sure the application uses the new credentials rather than waiting for the old one to be unlocked. Also review CloudTrail and billing, remove any unauthorized resources, enforce least privilege, and enable MFA and budget alerts. If the account itself is restricted, new keys alone may not resolve the issue, but credential rotation should still happen immediately.

The inconsistent instructions suggest the case needs a single accountable owner. Put the timeline, case numbers, security actions already completed, affected users, launch deadline, and estimated business impact into one concise update. Request a formal escalation to the security and account teams, and have whoever manages your AWS relationship push it internally. For future incidents, avoid relying on a single credential or service path for a production launch and keep a tested fallback.

If this service is supporting a business launch with that much financial impact, an appropriate paid AWS Support plan—ideally Enterprise Support—should be in place. That gives you faster response targets and access to escalation channels. Ask the current case owner or your AWS account representative to involve the technical account team and mark the business impact clearly.