You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is applicable or not, but it seems more than a few client conversations have been centered around "how to set up their cloud account".
Clients have been asking about a "hub and spoke" pattern to their cloud account with centralize a subset of cloud services for visibility, security, and compliance while giving enough autonomy for the workloads to provision the services they need, within the "guardrails" of a centralized authority.
Pub/Fed and banking clients seem to be gravitating toward a "hub and spoke" design to their cloud account and organization structure. For example, in large orgs with distributed IT teams, a "cooking cutter" landing zone for workloads interacts with a centralized "management plane" account for aggregate logging, brokering public traffic, centralized audit & billing access.
The text was updated successfully, but these errors were encountered:
Not sure if this is applicable or not, but it seems more than a few client conversations have been centered around "how to set up their cloud account".
Clients have been asking about a "hub and spoke" pattern to their cloud account with centralize a subset of cloud services for visibility, security, and compliance while giving enough autonomy for the workloads to provision the services they need, within the "guardrails" of a centralized authority.
Pub/Fed and banking clients seem to be gravitating toward a "hub and spoke" design to their cloud account and organization structure. For example, in large orgs with distributed IT teams, a "cooking cutter" landing zone for workloads interacts with a centralized "management plane" account for aggregate logging, brokering public traffic, centralized audit & billing access.
The text was updated successfully, but these errors were encountered: