Professional background
M.Neboke has worked with AWS since 2009 and implemented an enterprise production release on AWS in 2015. Since then, M.Neboke has continued to work on enterprise architecture, with a recent focus on how large organizations can implement the 3-2-1-1-0 backup model in practice and how Backup as a Service platforms should be evaluated.
Why I publish this work
I believe that sharing practical recovery knowledge can improve security beyond any single organization. Backup guidance is most useful when it explains trust boundaries, failure paths, operating constraints and the evidence needed to prove a restore—not only the features a product advertises.
My current research centers on translating 3-2-1-1-0 from a memorable rule into controls that can be governed and tested across an enterprise. That includes identity separation, immutable and offline copies, clean recovery, measurable RPO and RTO, and the selection of Backup as a Service platforms.
Identity and confidentiality
M.Neboke is a professional pseudonym. Because the subject overlaps with my professional work, I do not publish my legal name, employer, client names or identifying project details. Articles draw on experience without disclosing confidential information.
Editorial boundaries
I participate professionally in architecture and BaaS evaluation. Vendor-specific claims on this site are therefore separated from design judgment and must be supported by dated documentation, contractual language or reproducible testing. Commercial relationships, if introduced, will be disclosed.