Working notes from Formiga, an independent AWS consultancy in Cascais, Portugal. There is nothing to buy on these pages and no product behind them.
Every page here follows the same three rules, because they are the rules that make a page worth checking rather than worth skimming: anything attributed to a vendor is quoted from that vendor's own documentation with the date we read it; everything else is labelled as our opinion; and each page ends with what it does not claim. Where a source does not answer a question, we say so and leave the hole visible instead of filling it.
Tagging a resource and being able to report on its cost are two different acts, and only one of them happens in the account where the resource lives. What AWS states about activation and its 48-hour delay, what its documentation does not state, and six ways a tagging scheme looks finished and reports nothing.
NAT Gateway processing, cross-AZ transfer, S3 requests and CloudWatch Logs ingestion are the lines teams cut first. Each one is usually paying for something — and the question worth asking before you cut it.
Numbers written during a compliance exercise are targets, not measurements. AWS's four DR strategies named at source, the divergences that make a written RTO false without an outage, and why the engineer who built the recovery path is the worst person to validate it.
Code 0224 is mandatory for French routing identifiers and absent from EU EAS code list v16. DGFiP's own change log explains why. Written in French, for the people who hit this in production.
Architecture reviews, cost audits, intelligent document processing, disaster recovery and regulatory readiness. Scope and prices on the page, not behind a call.
If one of these describes a problem you have, the front page says what an engagement looks like and what it costs, and there is a form on it that a person reads. We would rather you read the relevant guide first and decide you do not need us.