Urgent.News

What's breaking now, across thousands of outlets.

Tech

The bill jumped and the resource has no owner: where the creator lives in AWS, Azure, GCP and OCI

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…

A recent discussion on the FinOps subreddit highlighted an issue with cloud resource ownership. In several accounts, a migration process resulted in half of the newly created resources lacking an owner tag. This absence posed a problem as the budget alert, which was set up for the old account, failed to trigger because the new resources did not have the required owner designation.

The duration for which each cloud provider retains information about the creator of a resource varies. AWS retains this data for 90 days in its CloudTrail Event history, Azure retains it for 90 days in its Activity Log, Google Cloud retains it for 400 days in its Admin Activity audit logs, and Oracle Cloud Infrastructure (OCI) keeps it for 365 days in its Audit service.

For AWS, the username of the user who created the resource can be found using the CloudTrail lookup-events command. In Azure, the caller who initiated the resource creation can be retrieved using the az monitor activity-log list command. For GCP, the principal email associated with the resource creation can be obtained via the gcloud logging read command. OCI provides the principal name of the user who initiated the API call through the audit service.

When dealing with resources older than the provider's retention period, tagging becomes a solution. Adding a tag such as "claimed-by=team-x" and "claimed-on=2026-11-18" can help assign responsibility. This method, while slower than tagging at creation, still helps in identifying the accountable party for future reference.

Additionally, infrastructure as code tools like Terraform can provide a second source of information. The Terraform state list and state show commands can reveal the original owner of resources, while the creator's identity can be found in the audit log. For resources created manually or through other pipelines, the creator can be identified in the audit log, which leads to the corresponding pull request and its author.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Request IDs vs Correlation IDs: Never Get Lost in Distributed Logs Again

A Request ID is a unique string assigned to a single incoming HTTP request—a digital message sent over the internet—as soon as it arrives at a server.

  • Request IDs uniquely identify each HTTP request at the server level
  • Correlation IDs link operations across multiple services in a transaction
  • They help engineers trace data flow and resolve production incidents

More from Wednesday 18 November →