79650743

Date: 2025-06-03 06:55:04
Score: 1
Natty:
Report link

For my case , I got warning about suspicious activity on one of the API key (NOT the same key that run the CodeBuild either)

The issue was raised (via email) about 8am. Then 11am. i doing the CodeBuild and notice the "0 build in queue" error. The issues on the suspicious API has been raised about 10 days earlier, and i only "inactive" them. So i guess what i got today is second warning.

So this time i "delete" the exposed API key. And just about the write to AWS support. I got email Thank you for removed the exposed API key. And CodeBuild just work fine after that.

Reasons:
  • Blacklisted phrase (0.5): Thank you
  • Long answer (-0.5):
  • No code block (0.5):
  • Low reputation (0.5):
Posted by: Kawisathorn Sangiemchit