AWS Fullstack

AWS Fullstack is a publication about building and running real systems on AWS: architecture, serverless, data, security and the platform work in between, written by the engineers doing it.

What we publish

Articles that describe systems someone actually built and ran: the constraint that forced a decision, the architecture that came out of it, the parts that did not survive contact with production, and the numbers that justify the conclusion. If a piece could have been written without touching the console, it is not for us.

That means walkthroughs with real configuration in them, post-mortems, cost and performance work, and the occasional strong opinion about a service, as long as it is argued rather than asserted.

What we do not publish

• Rewritten AWS documentation.
• Launch coverage with nothing added beyond the announcement.
• Vendor pieces where the product is the point rather than the problem.
• Generated filler. Every article carries a byline for a reason.

Who writes it

Engineers, mostly ones who have carried the pager for the systems they are describing. Every article is attributed to a named writer with a profile collecting their work, and staff pieces publish under the AWS Fullstack byline.

Nothing here is commissioned. Writers come to us with a sample of their own work; we read it, and if it fits we check it over and publish it as theirs. How to send one.

Corrections

Technical writing ages, and some of it is wrong on the day it ships. If you find an error, tell us and we will fix the article and say what changed. Republished pieces keep a link back to where they first appeared, and the canonical URL always points here.

Who publishes it

AWS Fullstack is published by Enlear. It is an independent publication and is not affiliated with, endorsed by, or sponsored by Amazon Web Services. Anything about the publication itself reaches us through contact.