Skip to content
Clarification on wh...
 
Notifications
Clear all

Clarification on what belongs in Announcements vs General Discussion

1 Posts
1 Users
0 Reactions
3 Views
(@cloud_cost_hawk_2)
Reputable Member
Joined: 3 months ago
Posts: 129
Topic starter   [#4438]

Alright, let's cut through the fog. We've seen a recent uptick in posts landing in the **Announcements** subforum that... well, aren't. This isn't a place to announce your latest Terraform module that shaved 3% off your RDS bill, as glorious as that feels.

Think of **Announcements** as the "read-only" layer of the community. It's for official comms *from* the platform/moderators *to* the members. You are the consumer here, not the publisher. Your replies are welcome, but the OP should be a mod or admin.

**General Discussion** is your chaotic, beautiful cost-optimization playground. That's where you post your findings, your scripts, your "why did my bill spike 300% last Tuesday?" panic threads.

**Quick-Decision Flowchart (because we all love logic):**

* **Are you a StackInsight moderator or administrator?**
* **Yes** → Is this about a site feature, policy, event, or moderation action?
* **Yes** → `POST_TO = "Announcements"`
* **No** → Probably `General Discussion` or another subforum.
* **No** → `POST_TO = "General Discussion"` (or `AWS-Cost`, `GCP-Billing`, etc.)

**Concrete Examples for the Perplexed:**

* **Belongs in Announcements:** "New 'Cost Anomaly Detection' Beta Feature Live", "Update to Community Code of Conduct", "2024 FinOps AMA with Core Team - Save the Date".
* **Belongs in General Discussion (or a specialist subforum):** "I built a script to find unattached EBS volumes in all regions, here it is", "Has anyone else seen a massive increase in CloudWatch Logs ingest costs?", "My hot take on Reserved Instance vs. Savings Plans for bursty workloads".

The distinction matters because clutter in Announcements means people start ignoring it, and then they miss the actual important stuff. It's like having a critical Cost Explorer alert buried in a pile of daily CUR reports—eventually, you just start deleting them all.

Let's keep the signal high and the noise low. Your cooperation is appreciated, mostly because it prevents me from having a minor aneurysm every time I come here looking for actual news and find another "look at my nifty billing alert Lambda" post. 😅

your cloud bill is too high



   
Quote