Beginner's Guide to Securing Cloud Workloads
Context
Cloud security is a foundational concern for any organization deploying applications and workloads in cloud environments. Companies need documentation that simplifies compliance requirements, provides actionable guidance, and equips junior developers with the knowledge to build securely by default. This guide was created to serve as a reusable internal resource that could onboard new developers or accompany security reviews during early-stage development.
Solution
Structured a five-section guide covering the following critical areas:
- Identity and Access Management (IAM)
- Network Security
- Data Encryption (At Rest & In Transit)
- Vulnerability Scanning & Monitoring
- Final Checklist & Compliance Validation
Each section includes:
- Step-by-step instructions
- Checklists for implementation
- Common mistakes to avoid
- Mini test scenarios to validate security posture
The project was authored and published using MadCap Flare, an industry-standard tool for professional documentation, to demonstrate proficiency with real-world tech writing environments.
Impact
- Delivered a fully functional portfolio piece demonstrating both technical knowledge and documentation skills
- Successfully configured a Windows environment on Mac to run MadCap Flare using VMware Fusion
- Created compliant, testable, and easy-to-follow documentation tailored to junior cloud engineers — a highly relevant audience in today’s cloud-first landscape
Key Takeaways
- Writing for clarity means thinking like your audience — junior developers need just enough detail to learn without overwhelm.
- Technical writing is most effective when it’s actionable, testable, and includes guidance on avoiding common pitfalls.
- Tools like MadCap Flare may require cross platform setup, which built my confidence in configuring complex environments.
Reflection
This project enabled me to combine my cloud training with real-world writing and compliance scenarios. I overcame technical obstacles (including setting up a Windows VM, installing dependencies, and resolving XHTML validation errors in Flare), and I now have a polished, professional artifact.
I also ran into a frustrating but common Windows issue during the build process. Flare was repeatedly denied access to the output directory due to locked files. Despite restarting, running as admin, and cleaning the project, the build kept failing. Eventually, I manually explored the output folder, deleted its contents, and that resolved the error. This experience reinforced the value of persistence, curiosity, and hands-on troubleshooting — all essential skills for technical writers working across platforms.
Project Links
Right-click a link and choose “Open in new tab” if you don’t want to leave this page.
This workflow is based on a standard GitHub Actions template I studied at the AWS Cloud Institute. While I didn’t write it entirely from scratch, I modified it to suit the project’s test structure and repository setup.