As you might expect, there is no one single entry point or path that companies embark on to begin cloud adoption. More times than not, It starts small and organically. It could be a single team or part of the organization that starts to Dapple and using the cloud for a specific project or application.
A handful of users with a handful of accounts.
These are the pioneers of an organization tasked to evaluate the feasibility of cloud adoption.
And when the team ultimately find success in their endeavor, adoption starts to catch on like wildfire,
the benefits of the cloud speed, agility, efficiency and overall value attract other teams, groups or parts of the organization. Before long, what was once just a single application or pilot program? It's now a major component of the organizations I T infrastructure
do. The limited number of users and accounts and descriptions. Governance is often manual at this stage if considered it all
from here. As cloud infrastructure grows, we've seen organizations enter the next phase of adoption in some unique ways. If the organization entered this phase prior to about 2018 we saw them move to a model of a single account or subscription.
This model, which is now considered a legacy approach, was evangelized at the time by the major cloud service providers. The idea was that a single cloud account or subscription could support all of your workloads across your organization. While this made simple sense in theory, it starts to break down when applied at scale.
When you start to mix multiple workloads in a multi tenancy model inside a single a counter subscription like this,
user access and permissions become increasingly entangled.
And as you would expect, this complexity grows exponentially as the organization's infrastructure scales.
So about 2018 the major cloud service providers shifted and started to heavily promote the idea off a multi account or multi subscription approach.
In this model, the account or subscription is no longer a singular approach. Instead, the account or subscription is treated more like a container or blast radius for security and financial barriers and boundaries, layers of protection around your different workloads. In fact,
if you have an application deployed across multiple accounts for subscriptions, one for each life cycle environment,
this approach establishes much more granular control of security boundaries and user access, but still becomes increasingly complex at scale. A rat's nest of accounts and resource is
even contemporary cloud. Native organisations find complexity in governance its scale organizations that skipped over the cloud adoption journey often subscribed to a version of cloud lifecycle management
not unlike natural systems and constructs. Balance must be established before organizations can truly embrace the promise of improved agility and realized the extraordinary return on investment with the cloud.
The cloud management lifecycle, by and large, doesn't dramatically change between various market segments or between major cloud service providers where changes identified. A cloud lifecycle management platform allows us to quickly identify and accommodate those changes to ensure balance is not lost but
as you would expect finding this balance of scales complex,
how can an organization ensure the proper compliance and security boundaries? That skill, while still empowering their teams to innovate with newly released services and resource, is
ultimately, regardless of the approach for adoption strategy, three unique challenges and governance hinder speed, scale and progress at any organization until they're defined in salt.
The first challenge that arises its scale is around account management in accents. How do you determine who has access to what resource is across your enterprise.
The second challenge of scale is around controlling your cloud costs
with the inherent elasticity and power of the cloud.
How can you still adhere to budgets?
And finally, the third challenge that arises at scale is around compliance itself, making sure that all operations and deployments fall within any relevant regulatory policy. Boundaries and drift from this compliance is mitigated.
These challenges that scaled directly define our cloud governance principles, count management,
and continuous compliance.
Let's spend some time and packing each of these principles to better understand the methodologies that help solve our governance, complexity at scale as well as some of the best practices. We've learned that cloud tamer and helping our customers solve their unique cloud governance needs.