How do we pick a starting point for our cloud infrastructure rollout?

[Jacob.T]

So we’re finally trying to move our main application to the cloud, and I’ve hit this weird snag. Our team can’t even agree on the most basic starting point for our infrastructure setup, and honestly, I’m starting to feel a bit lost about which approach would actually match how we build and deploy things day-to-day.

[Mark.D]

I hear you the cloud move feels like a storm and the first step should not pretend to be a final blueprint we need a simple anchor like infrastructure as code to move together.

[Riley4]

An IaC first approach maps what you deploy to the steps you actually do in day to day work and that may reveal where the friction sits.

[PaisleyJT]

I am frustrated by the clash in the room and I want to feel that we can test one tiny end to end story with infrastructure as code and learn from it.

[Samuel24]

Chasing the perfect starting point can slow us down and I doubt a single universal plan will fit our messy realities.

[Scarlett_C]

Maybe success is not a tool choice but a measured rhythm of deploys tests and feedback and the cloud becomes a means not a cage.

[Jerry_D]

Wait are we thinking cloud as a place or as a catalog of services we already know how to use in our current style?

[GeorgeDL]

From a writerly angle I watch how the plan evolves like a character arc with constraints and drift shaping what readers expect from the system.