> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Remove Duplicate CloudTrail Trail

> Stop paying for a second copy of the same CloudTrail management events.

CloudTrail delivers the first copy of management events in each region at no charge. Every additional trail that records the same management events is billed per event. nOps finds accounts and regions paying for these extra copies and shows the whole charge as the saving.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Management and governance |
| **Service** | AWS CloudTrail |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 30 days |
| **Source** | nOps |

## Why it matters

Duplicate trails are common after an organization trail is added on top of trails each account already had, or when a security tool creates its own trail.

## How nOps finds it

nOps reads the last 30 days of CloudTrail billing for each account and region. An account and region is flagged when paid management-event charges (the copies after the free one) cost at least \$5 over the period and were billed on at least 25 of the last 30 days. The saving is that charge.

## Before you start

Know which trail your security and compliance tools rely on. Permission to change trails (`cloudtrail:PutEventSelectors`, `cloudtrail:StopLogging`).

## How to implement

1. List the trails recording in the region, including organization trails (`aws cloudtrail describe-trails --include-shadow-trails`).
2. Check each trail's event selectors (`aws cloudtrail get-event-selectors --trail-name TRAIL`) and pick the one to keep, usually the organization trail.
3. Make sure the kept trail is logging and records all management events.
4. On the duplicate trail, remove management events and keep any data events (CloudTrail console: **Trails → your trail → Management events → Edit**). If it records nothing else, stop logging or delete it.
5. Update Terraform or CloudFormation if the trail is managed there.

## Risks and considerations

* Security tools, SIEMs and log archives may read from the duplicate trail's bucket. Point them at the kept trail first.
* Keep the duplicate's data events if you need them; only the management events are duplicated.
* To roll back, restore the trail's previous event selectors or start logging again. The kept trail recorded everything in between.

## FAQs

> [accordion] Will I lose any events?
>
> No. The kept trail still records every management event. Only the paid second copy stops.

## Related

* [Disable CloudTrail Data Events in Non-Production Accounts](https://help.nops.io/inform/supported-recommendations/disable-cloudtrail-data-events-in-non-production-accounts)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.