Professional background
M.Neboke began working hands-on with AWS after creating an account in 2009. In 2015, M.Neboke designed and implemented the production release of an enterprise system on AWS, then continued serving as a system architect across enterprise cloud programs. Recent work focuses on translating 3-2-1-1-0 into affordable, testable controls and evaluating Backup as a Service options for large organizations. M.Neboke also serves as a part-time lecturer in a university business administration program, connecting technology architecture with governance, risk, operations and management decisions.
Experience at a glance
- 2009: Created an AWS account and began hands-on work with the platform.
- 2015: Designed and implemented the production release of an enterprise system on AWS.
- Current: Works as an enterprise system architect, including 3-2-1-1-0 implementation and BaaS evaluation.
- Academic: Serves as a part-time university lecturer in business administration.
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. Identifying employment, client and project details are not published. Articles draw on experience without disclosing confidential information.
Firsthand field notes are published only in anonymized form. They retain the technical sequence and measured outcome when useful, state what was not tested, and avoid presenting historical AWS experience as validation of current service behavior.
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.