--- title: Day 15/30: “Who created this server?” | daily.dev description: A short, humorous take on the importance of AWS resource tagging. Without proper tags for project, environment, owner, and cost centre, cloud resources become... canonical: https://daily.dev/posts/day-15-30-who-created-this-server--0ybdcdkzr twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Day 15/30: “Who created this server?” | daily.dev og:description: A short, humorous take on the importance of AWS resource tagging. Without proper tags for project, environment, owner, and cost centre, cloud resources become... og:url: https://daily.dev/posts/day-15-30-who-created-this-server--0ybdcdkzr og:image: https://api.daily.dev/og/posts/0ybdCdkzR.png og:image:alt: Day 15/30: “Who created this server?” og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Day 15/30: “Who created this server?” **[Ezile Mdodana](https://daily.dev/sources/7vb9selrkhohgnzepmfvq)** · [@ezilemdodana](https://daily.dev/ezilemdodana) · 1 min read · 13 upvotes · 1 comments ## Summary A short, humorous take on the importance of AWS resource tagging. Without proper tags for project, environment, owner, and cost centre, cloud resources become unidentifiable and undeletable — creating governance, security, and cost management headaches. A consistent tagging standard prevents the classic 'mystery server' problem that plagues teams relying on memory instead of documentation. ## Content Nobody knows. “What does it do?” Also nobody knows. “Can we delete it?” Suddenly, everybody is nervous. AWS tags help label resources by project, environment, owner, department or cost centre. A simple tagging standard makes reporting, automation, security and cost management easier. Useful tags might include: `Project` `Environment` `Owner` `CostCentre` If your naming strategy is “we will remember,” I have unfortunate news about human memory. #AWSWithoutTheFluff #AWSTagging #CloudGovernance ## Community discussion Top comments from developers on daily.dev. **@agustinbarrientos** · 0 upvotes > An ownerless server should be checked against load balancer targets, DNS, recent connections, and scheduled jobs, then stopped before termination. "Nobody owns it" isn't proof that nobody depends on it. ## Similar posts on daily.dev - [Amazon SageMaker launches custom tags for project resources](https://daily.dev/posts/amazon-sagemaker-launches-custom-tags-for-project-resources-j4ythn8wo) · AWS · 0 upvotes · 0 comments - [Your AI agent just provisioned a resource. Who owns it?](https://daily.dev/posts/your-ai-agent-just-provisioned-a-resource-who-owns-it--cx9pu5e45) · The New Stack · 0 upvotes · 0 comments - [How to reassign resource ownership before someone’s last day](https://daily.dev/posts/how-to-reassign-resource-ownership-before-someone-s-last-day-umubjjbi6) · The New Stack · 0 upvotes · 0 comments --- Tags: [#aws](https://daily.dev/tags/aws) [View this post on daily.dev](https://daily.dev/posts/day-15-30-who-created-this-server--0ybdcdkzr) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/day-15-30-who-created-this-server--0ybdcdkzr","headline":"Day 15/30: “Who created this server?”","text":"A short, humorous take on the importance of AWS resource tagging. Without proper tags for project, environment, owner, and cost centre, cloud resources become unidentifiable and undeletable — creating governance, security, and cost management headaches. A consistent tagging standard prevents the classic 'mystery server' problem that plagues teams relying on memory instead of documentation.","url":"https://daily.dev/posts/day-15-30-who-created-this-server--0ybdcdkzr","datePublished":"2026-08-10T09:04:09.446Z","dateModified":"2026-09-13T20:47:27.300Z","author":{"@type":"Person","name":"Ezile Mdodana","url":"https://daily.dev/ezilemdodana","image":"https://media.daily.dev/image/upload/s--1OI8gwnO--/f_auto/v1771923757/avatars/avatar_7vB9SeLRKhOHGnzEpmFvQ?_a=BAMAMiiu0","description":"Software Project Lead sharing practical insights on NestJS, Angular, AWS and scalable systems.","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":8430}},"image":"https://media.daily.dev/image/upload/s--VgB6W7zc--/f_auto/v1786352650/posts/0ybdCdkzR?_a=BAMAMicg0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":13},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"comment":[{"@type":"Comment","text":"An ownerless server should be checked against load balancer targets, DNS, recent connections, and scheduled jobs, then stopped before termination. “Nobody owns it” isn’t proof that nobody depends on it.","datePublished":"2026-08-14T19:34:01.216Z","url":"https://daily.dev/posts/0ybdCdkzR#c-ayc0WQv1e","author":{"@type":"Person","name":"Agustin Barrientos","url":"https://daily.dev/agustinbarrientos","image":"https://media.daily.dev/image/upload/s--5ayxQnqn--/f_auto/v1788281802/avatars/avatar_wQYYVe5Tbj0NJ7C7qPoa8?_a=BAMAMicg0"}}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/sources/7vb9selrkhohgnzepmfvq","name":"Ezile Mdodana"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Ezile Mdodana","item":"https://daily.dev/sources/7vb9selrkhohgnzepmfvq"},{"@type":"ListItem","position":3,"name":"Day 15/30: “Who created this server?”"}]} ```