Home
BuildOn.AWS is a community-first site that brings builders together to begin and continue their personal cloud journey. BuildOn.AWS tackles the issues that matter to you most by providing a safe space for builders of all skill levels to share experiences, best practices, lessons learned, eureka moments, and the occasional tale of woe — all with the goal of helping each other get the most from the cloud, whether you use AWS or not.
All content posts are reviewed — first as a proposal, then as content to be published — to ensure they fit the vision of BuildOn.AWS. Before submitting content proposals to BuildOn.AWS, please familiarize yourself with these Community Content Guidelines.
We look for content that fits the BuildOn.AWS vision, both in terms of topic and style.
Post topics must:
- Address a broad cloud concept, question, or challenge. Specific AWS services can be used to give technical examples, but does not have to be the focus of the content. Rather, prioritize topics that are timely, useful, and interesting.
- Help builders make decisions, answer questions, and solve problems. Advice should be actionable and well-supported.
Writing style must:
- Use your personal voice, stories, and experiences to complement your technical expertise. Posts should read like you’re explaining something to a friend, not like you’re running PR for a company or trying to sell a product.
- Have an opinion. Sharing well-reasoned and evidence-based perspectives helps readers make decisions. Equivocation helps no one.
- Stay clear, educational, and concise. Complex ideas should be made accessible using images, illustrations, and examples as needed — and the reader should always understand the “why” of any direction. But posts should be no longer than they need to be. Always be asking, “Does this line truly add value for the reader?” If the answer is no, delete it.
- Feel free to be fun. Remember: passion is contagious. If you find something interesting or funny, don’t be afraid to share it with your reader — especially if it helps crystalize the topic you’re writing about.
- What are JavaScript engines?
- Instrumenting Java applications with OpenTelemetry
- Four reasons why GraphQL is the future
- How to deploy a Kubernetes cluster using Terraform
- How I Scaled a Mastodon Instance Over the Weekend (Want to write this? Grab it from the wish list here.)
- Showdown: Emacs vs Vim (Want to write this? Grab it from the wish list here.)
- Linux commands every developer should know (Want to write this? Grab it from the wish list here.)
For more ideas, see the content wishlist.
Some content doesn’t fit on BuildOn.AWS, for example because it violates the Terms of Use, Site Terms, and Code of Conduct, or because its topic or style don’t align with the above guidelines. Content proposals may be rejected or sent back with a request for resubmission if:
- Content does not follow the BuildOn.AWS topic and style guidelines (above).
- Content contains affiliate links.
- Content is plagiarized (posts, images, comments, code snippets) or you don’t have permission to use it.
- Content violates the Terms of Use, Site Terms, and Code of Conduct.
- We aim to create a positive and welcoming community, and content that is disrespectful or otherwise damages that positive atmosphere will be rejected.