What happens in a session
- Your findings, not a slide deck. The session starts from what your own accounts show: the security findings, the cost movements and the gaps against the month's topic.
- A senior AWS architect. Each session is run by a Solution Architect with 15 or more years of AWS and cloud experience, the same people who deploy your landing zone.
- A short list to act on. You leave with the findings put in order, in plain English, and what to do about each one.
How often
Essentials includes one session a month and Pro includes two. Office Hours are not part of the Free plan. See Pricing.
The year's topics
Each month has a topic, so over a year the sessions cover the whole of a well-run AWS environment. The calendar below is the starting point. The topics are chosen to fit your business and tied to your own security and cost findings, so the order changes when something in your environment needs attention sooner.
| Month | Topic |
|---|---|
| January | Reliability |
| February | Security |
| March | Cost optimization |
| April | Performance |
| May | Automation |
| June | Data and backup |
| July | Networking |
| August | Compliance |
| September | Sustainability |
| October | Incident readiness |
| November | Governance |
| December | Year-end review |