# How we write and check our AWS guides

The guides on cloudconsole.dev cover AWS errors, CLI commands, CloudWatch alarms, Logs Insights queries, regions and how-tos. This page explains how they are written, how they are checked and how to get one corrected.

## How a guide is made

1. **One real question per page**

   Each guide answers one thing engineers actually search for: an error message, a CLI command, a CloudWatch alarm, a Logs Insights query, a region or a how-to. The questions come from real search suggestions, not from a keyword list padded with variations. The short answer comes first, then the detail.

2. **AWS documentation as the source**

   Every guide links the AWS documentation it relies on in its Sources section. Limits and defaults that AWS can change are written as “by default” or “at the time of writing”, or left out.

3. **Every CLI command is checked automatically**

   Before a guide is published, our build checks every `aws …` command against the AWS CLI’s own service definitions (botocore). A flag the API doesn’t have fails the build. Last full check: 17 November 2026, all 509 guides passing.

4. **Alarm settings exactly as AWS recommends**

   CloudWatch alarm guides restate the metric, statistic, period, threshold and evaluation settings from AWS’s published “Recommended alarms” and link that page. The explanation of when to tune them is our own.

5. **Written for someone fixing something now**

   Most common cause first, a short diagnostic sequence, commands you can copy, and the mistake people make next. Commands that delete or change things are flagged. Examples use placeholder accounts and resources.

6. **Drafted with AI, checked against the sources**

   Guides are drafted with the help of AI writing tools, then checked against the AWS documentation they cite and by the automated checks above, including rules that reject unsupported links, invented flags and repeated boilerplate.

## Policy

| | |
|---|---|
| Who writes them | Cloudconcur Ltd, the UK company that makes CloudConsole, an app for AWS on iPhone and Android. |
| Independence | We are not affiliated with Amazon Web Services. Guides recommend AWS’s own tools and other products when they are the right answer. CloudConsole is mentioned only in the box about handling the problem away from your desk; comparison pages say that we make CloudConsole and list their sources. |
| Free, no ads, no cookies | The guides are free to read, carry no ads and set no cookies; page views are counted with cookie-free Cloudflare Web Analytics, and taps on the store buttons are counted the same way (see the [privacy policy](https://cloudconsole.dev/privacy)). |
| Dates | Each guide shows when it was last updated. When we correct a guide, we change that date. |
| Corrections | Found something wrong or out of date? Email [support@cloudconsole.dev](mailto:support@cloudconsole.dev) with the page address. We fix confirmed errors and update the page. |
| Quoting | You are welcome to quote the guides, including in AI assistants. Please link back to the page you use. |

Start with the [guides](https://cloudconsole.dev/guides/), or read [about CloudConsole](https://cloudconsole.dev/about).

---

Source: https://cloudconsole.dev/editorial

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
