Submissions
Write for us
AWS Fullstack takes submissions from engineers writing about systems they have built and run on AWS. Here is what we look for and how to send yours.
How it works
Send us a sample
A finished article, a draft, or a link to something you have already published. We would rather read your actual writing than a description of it.
We read it
An editor reads it against what we publish and replies either way, usually within a week. Most articles that run here land between 1,200 and 2,500 words: long enough for real configuration, short enough to finish.
We check it, we do not rewrite it
If it fits, we check the facts, links and formatting before it goes live. The words and the conclusions stay yours. Anything that needs changing comes back to you rather than being changed for you.
It publishes under your name
Every article carries your byline and a profile page collecting your work. Already published it elsewhere? We will republish with a canonical link back to AWS Fullstack and a credit to the original.
What makes a submission land
- It describes something you built or operated, not something you read about.
- It has a number in it somewhere: latency, cost, throughput, error rate.
- It says what you would do differently, which is usually the most useful paragraph in the article.
- It is not a product walkthrough. We are happy to cover a tool that solved your problem; we will not run a piece where the tool is the point.
Send your sample
It goes straight to the editors. We reply either way, usually within a week.