Audit logs are how an organization reconstructs what happened during an incident, satisfies regulators and decides what to tell customers. An attacker with enough privilege will try to switch them off, narrow what they record, or delete what has already been collected — leaving the company unable to answer basic questions later. The good news is that AWS offers strong ways to make logging tamper-resistant: an organization-wide trail managed centrally, logs stored in a separate account, and organization policies that stop even account administrators from disabling them. If an ordinary administrator in a production account can turn off logging, that is a governance gap worth closing quickly.