Skip to main content
MohamedCamara

My name is Mohamed Camara. I grew into cloud and infrastructure the long way: helping users first, then staying with the harder system problems underneath.

The work I do now grew out of that path.

Over time I moved deeper into infrastructure, then cloud, then architecture. Today that means AWS foundations, hybrid networking, identity, migrations, and research or regulated environments where mistakes are expensive. I still spend most of my time in the parts people do not glamorize, but teams depend on.

What pulled me in
AWS · Hybrid · Identity · HPC & lab systems
What I watch for
People on the other side of the screen · Long nights · Drift
How I tend to work
Stay close · Write it down · Tell the truth

In practice

Cloud, hybrid, and systems I carry

The story below is how I got here. This is what here looks like in engineering terms — the places responsibility has settled over the years.

Read the full narrative on its own page →

Chapter

Where it started, and how it kept going

I wrote this the way I would tell it to someone patient enough to listen — the uncertain stretch, one morning by the window, and later the slow build into helpdesk, Bay State IT, and the infrastructure work that became my life. Nothing below contradicts it; it all comes from the same person.

There was a time in my life when everything felt uncertain.

Not the kind of uncertainty you can easily ignore, but the kind that sits with you quietly and follows you throughout the day. The kind that makes you question where you are, where you're going, and whether you're doing enough to get there.

I remember waking up early one morning—earlier than usual. The house was silent. No movement, no noise, no distractions. It was one of those rare moments where everything felt paused, like the world hadn't fully started yet.

I sat there for a while, just thinking.

At that point in my life, I wasn't where I wanted to be. I knew I had potential, but I also knew I hadn't fully stepped into it yet. I had gone through challenges, made mistakes, and experienced moments where things didn't go the way I expected. There were times I doubted myself—times I wondered if I was on the right path or if I was moving too slowly.

It wasn't failure. It was something more subtle.

The sun doesn't rush. It doesn't force its way up. It rises, consistently, every day, whether you're paying attention or not.

And that's when it clicked.

Everything I had been through up to that point—the challenges, the setbacks, the uncertainty—it wasn't holding me back. It was shaping me. It was building something I couldn't fully see yet.

I started thinking about the work I had been putting in, the things I was learning, the experiences I was gaining. Even the difficult moments had value. They were teaching me discipline, patience, and resilience.

That morning wasn't about motivation.

It was about clarity.

I realized that I didn't need everything to be perfect before moving forward. I didn't need to have every step figured out. What I needed was consistency. Direction. And the willingness to keep going, even when things weren't clear.

So I made a decision.

But my mindset changed.

And that changed everything.

I started approaching things differently. I became more intentional with my time, more focused on growth, and more disciplined in how I moved. I stopped comparing where I was to where others were and started focusing on my own path.

I understood that real growth isn't loud.

It's built quietly, through consistent effort, through small decisions, through showing up even when you don't feel like it.

Over time, things began to shift.

Not all at once, but gradually.

The same way the sun rises—steady, consistent, inevitable.

Looking back, that morning stands out as a turning point.

Not because something dramatic happened, but because something internal changed. I saw things differently. I understood that where I started didn't define where I would end up.

It also meant growing into environments where the stakes were higher and the systems more complex.

A major part of my work began supporting healthcare, biotech, and scientific research environments. These were not simple deployments. They required careful thinking around reliability, access, storage, compliance expectations, and how technical systems support real research and lab operations. I worked on high-performance computing environments using AWS ParallelCluster, with Slurm and SlurmDBD integration, AWS Managed Microsoft AD, and scientific workload support. I helped design and support research-oriented cloud foundations, lab workflow systems, identity integrations, storage patterns, and enterprise-grade continuity for environments where failure has real consequences.

That work reinforced something I had already started to believe years earlier: technology has to work in the real world.

It has to be usable.

It has to be supportable.

It has to be secure, scalable, and built with enough care that people can rely on it.

The same was true in other parts of my work. Whether it was designing hybrid storage with AWS Storage Gateway, integrating access through Active Directory, Okta, or Azure AD, supporting Linux environments, troubleshooting Windows Server and RDS infrastructure, helping lead Google Workspace to Microsoft 365 migrations, implementing CI/CD pipelines, improving monitoring and alerting, conducting AWS audits, or guiding clients through better architecture decisions—the pattern stayed the same.

Keep moving deeper.

Understand the system.

Take ownership.

That is probably the part that matters most to me.

I have learned a lot. I have taken on more than I once imagined. I have grown from solving immediate issues in front of me to designing, supporting, and improving larger systems that businesses and teams depend on. But I still see my path the same way I did in that quiet early morning light: not as something finished, but as something unfolding.

Still rising.

Still becoming.

Still moving forward.

The sun doesn't rush. It doesn't force its way up. It rises, consistently, every day, whether you're paying attention or not.

Something I still believe

The scenes above are the same narrative, staged for pacing. If you want the full chapter in one continuous scroll — print-friendly, no duplication on this page — it lives here:

Open full narrative

Turn

Where story becomes systems

The same mindset in the story shows up here in practical form: account design, networks, identity, migration sequencing, and the quieter operational work that keeps systems reliable.

After the story

The domains my work expanded into

None of this came from a checklist. Each area below is somewhere responsibility pulled me and I kept showing up.

  • AWS & multi-account governance

    I work with Control Tower and Landing Zone Accelerator when teams need a clean multi-account foundation that can scale. The goal is simple: guardrails people actually use, and an estate someone new can understand quickly.

  • Hybrid & cloud networking

    Most environments are hybrid in practice. I focus on VPN, routing, and Transit Gateway patterns that are easy to reason about when incidents happen.

  • Research & HPC on AWS

    I support research stacks where reliability matters as much as speed: ParallelCluster, Slurm, and directory-integrated workloads. I treat these environments like production, not temporary projects.

  • Storage, backup & continuity

    Storage and DR only count when restore paths are tested. I help teams tighten gateway/NAS patterns, backup scope, and recovery ownership before a bad day proves the gaps.

  • Identity & access

    I work across IAM Identity Center, Okta, Azure AD, and AD integrations so access models stay understandable for both users and auditors.

  • Microsoft 365 & collaboration migrations

    I have led Workspace-to-M365 migrations including tooling, DNS, identity, and stabilization. The cutover is only half the job; the week after is where trust is won.

  • Linux & Windows operations

    I still work hands-on across Linux and Windows operations. The pattern is consistent: stabilize quickly, find root cause, and fix the class of failure.

  • Monitoring, automation & CI/CD

    I build monitoring and automation that operators will actually use. Good dashboards and pipelines should reduce toil without hiding risk.

  • Security, SSL & compliance support

    I support reviews, hardening, and certificate hygiene with an operational lens. Recommendations are written for the team that has to execute them, not just present them.

  • Client advisory & cross-functional leadership

    I help clients make practical decisions across architecture, cost, and delivery. I am direct about trade-offs when a shortcut will create downstream pain for operators or customers.

Systems

Kinds of environments I have lived inside

These are patterns of work I have lived in: landing zones, hybrid paths, research stacks, migrations. Client names stay private; the work itself does not.

  1. 01

    When the AWS footprint outgrew one account

    I have helped teams move from ad-hoc AWS sprawl to clear multi-account foundations. The real goal is an estate a new engineer or auditor can map without guesswork.

    • Control Tower
    • LZ Accelerator
    • Multi-account
    • Healthcare / life sciences
  2. 02

    Lab and research stacks that had to behave like production

    ParallelCluster and Slurm environments where failed jobs mean lost science, not just lost time. I treat these stacks as long-term platforms, not temporary grant artifacts.

    • ParallelCluster
    • Slurm
    • Managed AD
    • Research computing
  3. 03

    The stretch between cloud and everything that could not move

    Hybrid connectivity across VPN, Transit Gateway, and routing paths that stay legible under pressure. I prefer explicit maps over hidden assumptions.

    • VPN
    • Transit Gateway
    • Hybrid
    • Routing
  4. 04

    Access, data, and what survives a bad day

    Identity, storage, and DR work that aligns access and recovery with reality. A plan is only credible if someone has practiced it.

    • Okta
    • Azure AD
    • Storage Gateway
    • Backup & DR
  5. 05

    When mail and files and habits had to move

    Workspace-to-M365 migrations including tooling, DNS, and identity cutovers. I stay through stabilization, because that is where trust is earned.

    • Microsoft 365
    • MigrationWiz
    • Mail & DNS
    • Change management
  6. 06

    Honest reads on what the estate is really doing

    Architecture and risk reviews aimed at better sequencing, cleaner spend, and fewer operational surprises. I call out delivery gaps early when promises outrun platform reality.

    • Advisory
    • Optimization
    • Security reviews
    • Roadmaps

Path

Compressed, if you prefer it that way

If you want the compressed version, here is the same path in four beats.

Foundations

Helpdesk and IT services — Bay State IT

I started where users feel pain first: the ticket, the call, the screen that will not cooperate. That season taught me to look past symptoms and fix system causes.

01

Systems & infrastructure

Widening into infrastructure, cloud, production

From there the work widened into servers, networks, storage, identity, and cloud. I cared less about closing fast and more about whether the environment would still make sense next month for someone new.

02

AWS & hybrid ownership

When AWS became mine to carry

AWS became where design and operations met: accounts, hybrid links, identity, and data across real workloads. I became the person people called when design, deploy, or incident response needed one owner.

03

Today

Where the path sits now

Today the work crosses engineering, clients, and delivery commitments: reviews, roadmaps, migrations, and documentation that lasts. The thread is still the same: understand the system, reduce risk, leave it clearer than I found it.

04

Swipe or scroll horizontally →

What I notice

How I try to hold responsibility

These are the rules I reach for when design choices, deadlines, and incidents get real.

  • Ownership

    If I put my name on a design, I own what happens in operations too: certificates, integrations, drift, and handoff quality.

  • Clarity for every audience

    Engineers need specifics, and non-engineers still need clear trade-offs. I aim for language both groups can act on.

  • Security and scale as engineering

    Security and scale are design decisions, not late-stage add-ons. It is always cheaper to argue in design than in incident review.

  • Operational truth

    I trust evidence: logs, metrics, runbooks, and clear change history. Process should match how failures actually happen.

  • Promises you can keep

    What is sold and what the platform can sustain should describe the same reality. I push back when that gap grows.

  • Writing for the next person

    Documentation is part of delivery. Good notes and diagrams are how you respect the next operator and your future self.

If we talk

Ways I have been useful to people

Not a product menu. Just situations where I have been useful and where a conversation might help.

Walking an AWS estate together

A practical review of accounts, networking, identity, spend, and risk. I focus on what to fix now, what can wait, and what the team can realistically sustain.

Hybrid moves without pretending the old world vanished

Landing zones, connectivity, and sequencing that respect production calendars and team capacity.

When identity is the knot

IAM Identity Center, Okta, Azure AD, and AD alignment so sign-in, authorization, and audit trails match real usage.

Storage, backup, and what “recovery” really means

Gateway and NAS patterns, backup scope, and DR plans that the operating team can actually execute.

Standing with research teams on AWS

Research stacks on AWS that stay supportable over time, not brittle after initial setup.

Migrations that include the week after

Workspace-to-M365 style moves with careful DNS/identity cutovers and a real stabilization phase after go-live.

Closing chapter

Reach

If something here spoke to you

If you want to talk architecture, migration risk, or the gap between promises and platform reality, send a note. I read them.

Still rising. Still becoming.

If something here resonated — the pace of the work, the way systems are held, or the story behind it — I would rather hear it in your words than leave it at a scroll.

End of page — thank you for reading