You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1017304
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/cloudtrail.mdx
+37-5Lines changed: 37 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,9 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
11
11
/>
12
12
13
13
{/* MANUAL-CONTENT-START:intro */}
14
-
[AWS CloudTrail](https://aws.amazon.com/cloudtrail/) records who did what in your AWS accounts. Every API call — from the console, the CLI, an SDK, or another AWS service — is captured as an event with the calling identity, source IP, parameters, and result. It is the system of record for security investigation, compliance evidence, and answering "what changed?"
14
+
[AWS CloudTrail](https://aws.amazon.com/cloudtrail/) records who did what in your AWS accounts. An API call — from the console, the CLI, an SDK, or another AWS service — is captured as an event with the calling identity, source IP, parameters, and result. It is the system of record for security investigation, compliance evidence, and answering "what changed?"
15
+
16
+
What lands in that record is set by configuration, not assumed. Trails and event data stores log management events by default; data events, network activity events, and Insights events are captured only where you configure selectors for them. Read a trail's selectors before you treat its history as complete.
15
17
16
18
With AWS CloudTrail, you can:
17
19
@@ -22,9 +24,39 @@ With AWS CloudTrail, you can:
22
24
23
25
In Sim, CloudTrail is the audit half of the AWS story. Where IAM and Identity Center answer *who has access*, CloudTrail answers *what they actually did with it* — so an agent can take a suspicious permission change and trace it back to the principal, the source IP, and the moment it happened, then hand a written timeline to whoever needs to act on it.
24
26
25
-
This block is read-only with one narrow exception: `Cancel Query` stops a running CloudTrail Lake query. It never enables or disables logging, alters trail configuration, or deletes a trail, so it can be granted a `cloudtrail:Describe*/Get*/List*/LookupEvents/StartQuery` policy with no residual write risk. Note that `Start Query` is billed per GB scanned and consumes your account's concurrent-query quota.
26
-
27
-
`Lookup Events` is limited by AWS to two requests per second per account per Region. The block paces itself against that limit automatically, so broad searches take longer rather than failing.
27
+
This block is read-only with one narrow exception: `Cancel Query` stops a running CloudTrail Lake query. It never enables or disables logging, alters trail configuration, or deletes a trail. Every operation it ships is covered by this policy, with no residual write risk:
28
+
29
+
```json
30
+
{
31
+
"Version": "2012-10-17",
32
+
"Statement": [
33
+
{
34
+
"Effect": "Allow",
35
+
"Action": [
36
+
"cloudtrail:DescribeTrails",
37
+
"cloudtrail:GetTrail",
38
+
"cloudtrail:GetTrailStatus",
39
+
"cloudtrail:GetEventSelectors",
40
+
"cloudtrail:GetInsightSelectors",
41
+
"cloudtrail:GetEventDataStore",
42
+
"cloudtrail:ListTrails",
43
+
"cloudtrail:ListEventDataStores",
44
+
"cloudtrail:ListTags",
45
+
"cloudtrail:LookupEvents",
46
+
"cloudtrail:StartQuery",
47
+
"cloudtrail:DescribeQuery",
48
+
"cloudtrail:GetQueryResults",
49
+
"cloudtrail:CancelQuery"
50
+
],
51
+
"Resource": "*"
52
+
}
53
+
]
54
+
}
55
+
```
56
+
57
+
`cloudtrail:CancelQuery` is the action `Cancel Query` needs, and it is not implied by `Describe*`, `Get*`, or `List*` — omit it and that one operation fails with an access-denied error. Note that `Start Query` is billed per GB scanned and consumes your account's concurrent-query quota of 10.
58
+
59
+
`Lookup Events` is limited by AWS to two requests per second per account per Region. Each call uses AWS adaptive retry mode and allows up to six attempts, so a throttled request backs off exponentially with jitter and usually succeeds instead of surfacing an error. That is a retry budget, not a guarantee: sustained throttling past six attempts fails the call with a `ThrottlingException`, and because a fresh SDK client is built per invocation, adaptive mode's client-side rate limiter carries no pacing state between calls. `Lookup Events` also returns one page per call — feed `nextToken` back in to walk a broad search, and expect to handle a throttling error on a long paging loop.
28
60
{/* MANUAL-CONTENT-END */}
29
61
30
62
@@ -192,7 +224,7 @@ List the ARN, name, and home Region of every CloudTrail trail visible to the acc
192
224
| ↳ `trailArn`| string | ARN of the trail |
193
225
| ↳ `name`| string | Trail name |
194
226
| ↳ `homeRegion`| string | Region in which the trail was created |
195
-
|`nextToken`| string | Pagination token for the next page of trails |
227
+
|`nextToken`| string | Pagination token for the next page of trails, or null on the last page|
0 commit comments