The case was told this month on r/FinOps, and it matches what I have seen in more than one account: a migration moved an environment from one account to another, half of the new resources came out without the owner tag because the pipeline that created them did not set it, and the budget with the alert was on the old account. No single leak went over US$ 100 a day, so no alert fired; the sum showed up on the monthly bill. When the question "whose volume is this?" came, nobody knew, and the tag that would have answered did not exist. What follows is where each cloud keeps the identity that created a resource, with the command, the field and how long it is kept. Everything comes from the official documentation; the sources are at the end.
AWS: CloudTrail Event history, 90 days
CloudTrail is enabled by default on every account and the Event history keeps the last 90 days of management events per region, with no trail and no event data store. lookup-events accepts ResourceName as a lookup attribute, so the resource ID is enough:
# in the resource's region; EventName: RunInstances, CreateVolume, AllocateAddress, CreateNetworkInterface aws cloudtrail lookup-events --region us-east-1 \ --lookup-attributes AttributeKey=ResourceName,AttributeValue=vol-0123456789abcdef0 \ --query "Events[].[EventTime,EventName,Username]" --output table # the full principal (ARN, type, session) is inside CloudTrailEvent, which is a JSON string aws cloudtrail lookup-events --region us-east-1 \ --lookup-attributes AttributeKey=ResourceName,AttributeValue=vol-0123456789abcdef0 \ --query "Events[?EventName=='CreateVolume'].CloudTrailEvent" --output text | jq .userIdentity Username is the session or user name; userIdentity carries type (IAMUser, AssumedRole, Root), arn and principalId. If the resource is older than 90 days, the Event history does not have it: you need a trail that was already writing to S3 before, or a CloudTrail Lake event data store.
Azure: Activity Log, 90 days
The Activity Log page says it plainly: "The activity log is the only place that stores the creator of a resource", and Azure retains it for 90 days and then deletes it. The field is caller:
az monitor activity-log list \ --resource-id "/subscriptions/<sub>/resourceGroups/<rg>/providers/Microsoft.Compute/disks/<disk>" \ --offset 90d --select eventTimestamp caller operationName status \ --query "[?status.value=='Succeeded'].{when:eventTimestamp,who:caller,op:operationName.value}" -o table --offset takes ##d##h and defaults to 6 h: without --offset 90d the query looks only at the last afternoon. To keep it beyond 90 days, a diagnostic setting that sends the Activity Log to a Log Analytics workspace; there you look the creator up in the AzureActivity table with whatever retention you set on that table.
GCP: Admin Activity audit logs, 400 days
Admin Activity audit logs are always written, cannot be excluded or disabled, and go to each project's _Required bucket, which retains 400 days and is not configurable. The principal is in protoPayload.authenticationInfo.principalEmail and the resource in protoPayload.resourceName:
# --freshness defaults to 1d: without this you only see the last day gcloud logging read \ 'logName:"cloudaudit.googleapis.com" AND protoPayload.resourceName:"disks/ownerless-disk" AND protoPayload.methodName:"insert"' \ --project=<project> --freshness=400d \ --format="table(timestamp,protoPayload.authenticationInfo.principalEmail,protoPayload.methodName)" To read the bucket directly: --bucket=_Required --location=global --view=_Default. Reading audit logs needs the Logs Viewer or the Private Logs Viewer role depending on the log type; Admin Activity ones are covered by the first.
OCI: Audit, 365 days
The Audit service records calls to every public OCI API, from the Console, the CLI, the SDKs or other services, and keeps them for 365 days. It is a tenancy-level value, applies to all regions and compartments, and cannot be changed. The principal is data.identity.principalName in the v2 schema:
oci audit event list --compartment-id <compartment-ocid> \ --start-time 2026-08-18T00:00:00Z --end-time 2026-11-18T00:00:00Z --all \ --query 'data[?data."resource-id"==`<volume-ocid>`].[data."event-name", "event-time", data.identity."principal-name"]' \ --output table --compartment-id is required: you search compartment by compartment. And before going to Audit, look at the resource's tags, because in OCI the creator is usually there, as explained below.
What to do with anything older than the retention
A volume from 2024 is in neither CloudTrail nor the Activity Log, and in GCP and OCI it depends on the date. What is left:
- Tag it today with whoever claims it and the date: claimed-by=team-x and claimed-on=2026-11-18. It is not the creator, it is the person responsible from now on, and next time the question has an answer.
- Terraform state as a second source: terraform state list and terraform state show on each workspace. What is in a state has an owner (the repo); what is in none was created by hand or by another pipeline.
- For what came from a pipeline: the identity that ran the apply is in the audit log (the assumed role, the service principal, the service account), and that date's deploy log leads to the PR and its author. Slower than a tag, but it closes the chain.
- In OCI, the automatic tags: tenancies created after December 17, 2019 have the Oracle-Tags namespace with two tag defaults, CreatedBy (principal name) and CreatedOn (date and time), which OCI applies to every new resource. If the namespace is missing, they are not applied. They show up in the resource's defined-tags: oci bv volume get --volume-id --query 'data."defined-tags"."Oracle-Tags"'.
- In AWS, the generated tag aws:createdBy: the management account activates it in Billing, it applies only to resources created after activation and only in some regions, and it lives in Billing and Cost Management reports, not in the console or Tag Editor. The value is account-type:account-ID:user-name or the role session name.
So it does not happen again
- Tag at creation, not afterwards. In Terraform AWS, default_tags in the provider "aws" block adds Owner and whatever else to every resource with tags in the provider (since 3.38.0; aws_autoscaling_group is the exception), and tags_all shows the result.
- In Azure, a policy with the modify effect adds or replaces a tag on create or update; the built-in "Add a tag to resources" sets a fixed value and, with a remediation task, reaches what already existed. It does not set the creator: for that it is still the exported Activity Log.
- In OCI, do not delete the Oracle-Tags tag defaults: they are ordinary tag defaults and the administrator can remove them, and without them the creator lives only in Audit again.
- A budget per new account or project the same day the account is created; an US$ 80-a-day leak does not trip the old account's alert.
FAQ
Why does CloudTrail not show my resource? Three causes: the wrong region (the Event history is per region), more than 90 days, or a name that is not what CloudTrail indexes as ResourceName. Try AttributeKey=EventName,AttributeValue=CreateVolume with a --start-time window and filter by hand.
Does the Activity Log show who created a resource six months ago? No, unless a diagnostic setting was already exporting it to a workspace. Microsoft writes it in its own documentation: to keep it beyond 90 days you have to export it.
Can I extend Audit retention in OCI? No: 365 days, tenancy-wide, not modifiable. For more, the audit logs are available as a Logging source, and a Connector Hub connector with Logging as source and Object Storage as target copies them to a bucket.
Is gcloud logging read useful without --freshness? Only for yesterday: the default is 1d.
What Control Cloud does with this
I build Control Cloud. The map lists what bills while attached to nothing: volumes with no instance, public IPs with no target, loose network interfaces, with the provider and the compartment or group they live in. It does not read CloudTrail, the Activity Log, GCP audit logs or OCI Audit: today the "who created it" question is answered with the commands in this note, and the map gives you the list of what to ask about. The notes on public IPs that bill, what survives when you delete a VM and log groups that never expire are the inventory of where those orphans usually are. If you want to see it on your account, request access: 7-day trial, no card.
Sources
- AWS CloudTrail User Guide, "Working with CloudTrail Event history" (enabled by default, 90 days of management events per region, separate from trails and event data stores); CLI reference cloudtrail lookup-events (AttributeKey ResourceName, Username, CloudTrailEvent with userIdentity).
- AWS Billing User Guide, "Using AWS-generated tags" (aws:createdBy: activated by the management account, only resources created afterwards, region list, Billing and Cost Management only, value format).
- Microsoft Learn, "Azure Monitor activity log" (90-day retention, "the only place that stores the creator of a resource", export to Log Analytics and query AzureActivity); reference az monitor activity-log list (--resource-id, --offset in ##d##h with 6 h default, --select caller).
- Microsoft Learn, "Azure Policy definitions modify effect" and "Assign policy definitions for tag compliance" (built-in "Add a tag to resources", remediation task).
- Google Cloud, "Cloud Audit Logs overview" (Admin Activity always written, _Required bucket, roles to read them, gcloud logging read "logName : projects/PROJECT_ID/logs/cloudaudit.googleapis.com"); "Logging quotas and limits" (_Required 400 days, not configurable); gcloud logging read reference (--freshness 1d default, --bucket --location --view); AuditLog type reference (authenticationInfo.principalEmail, resourceName, methodName).
- Oracle Cloud, "Overview of Audit", "Audit Log Retention Period" (365 days, tenancy-level, not modifiable), "Audit Log Contents" (data.identity.principalName) and oci audit event list reference (--compartment-id required, --start-time, --end-time).
- Oracle Cloud, "Understanding Automatic Tag Defaults" (Oracle-Tags, CreatedBy, CreatedOn, tenancies created after 2019-12-17, not applied if the namespace is missing); "Logging Overview" (audit logs as a Logging source) and "Connector Hub Overview" (Logging source, Object Storage target).
- Terraform AWS Provider, "Resource Tagging" guide (default_tags since 3.38.0, aws_autoscaling_group exception, tags_all).

