TalksAWS re:Invent 2025 - A leader's guide to navigating multicloud strategies and decisions (SNR204)

AWS re:Invent 2025 - A leader's guide to navigating multicloud strategies and decisions (SNR204)

Navigating Multicloud Strategies and Decisions

Understanding Multicloud Considerations

  • Multicloud represents a pivotal decision that can shape an organization's entire technology strategy
  • There is often confusion, contradictions, and uncertainty around multicloud strategies
  • AWS is committed to interoperability and providing tools to help customers build, migrate, and manage workloads across clouds

When is Multicloud the Right Strategy?

  • Multicloud should not be a solution looking for a problem - it adds complexity and requires a legitimate business need
  • Common scenarios where multicloud may be appropriate:
    • Mergers and acquisitions where the acquired company is on a different cloud
    • Desire to leverage unique capabilities across different cloud providers
    • Operating independent business units on different clouds
  • Key considerations:
    • Let business objectives drive the cloud strategy, not just the latest technology trends
    • Workload placement impacts teams across the organization, not just IT
    • Ensure everyone understands the "why" behind the multicloud strategy

Debunking Multicloud Myths

  1. Myth: Everyone is doing multicloud:

    • While many organizations claim to have a multicloud strategy, the majority still standardize on a single primary cloud provider
    • Don't get caught up in industry hype - focus on your organization's unique needs
  2. Myth: Multicloud helps avoid vendor lock-in:

    • Every technology choice creates some form of lock-in - the key is understanding and managing the trade-offs
    • Abstraction layers often fail to fully abstract away cloud-specific features and capabilities
    • Focus on defining a pragmatic strategy to reduce lock-in, not just avoiding it
  3. Myth: Multicloud improves availability:

    • Attempting to build complex multicloud failover mechanisms often creates more operational risk than it solves
    • A multi-region strategy within a single cloud provider is generally more reliable and cost-effective
  4. Myth: Multicloud provides better pricing leverage:

    • Procurement tactics of pitting cloud providers against each other often backfire, as the real savings come from mastering a single cloud platform
    • Studies show 20% lower infrastructure costs when using a single cloud provider versus multicloud

Establishing Multicloud Governance

  • Lack of clear strategy and governance quickly leads to multicloud sprawl and loss of control
  • Recommendations:
    • Centralize multicloud management through a unified cloud Center of Excellence
    • Standardize change management and implement a cohesive tagging strategy
    • Avoid spreading connected workloads across multiple clouds to reduce complexity and latency

Addressing Data Gravity and Workload Placement

  • Applications and data are naturally "pulled" together due to data gravity
    • Avoid separating applications from their data sources
    • Minimize data movement and keep workloads physically close to their data
  • Use purpose-built data lakes tied to specific applications or domains, rather than a single monolithic data lake

Organizational Considerations for Multicloud

  • Structure the organization with a unified cloud Center of Excellence and specialized teams for each cloud provider
  • Hire deep expertise in each cloud platform, rather than trying to find "full-stack" multicloud experts

Navigating Multicloud Security Challenges

  • Multicloud inherently increases security complexity due to different tools and approaches across providers
  • Implement automated security controls, create a single pane of visibility, and establish consistent security policies

Practical Multicloud Recommendations

  • If pursuing multicloud, allocate 80% of workloads to a primary cloud provider and 20% to secondary clouds
  • Carefully evaluate workload placement based on clear, documented criteria - don't let engineers make ad-hoc decisions
  • Consider multicloud for M&A, holding company structures, or unique cloud capabilities, but avoid it for cost leverage or failover expectations

Additional Resources

  • Visit AWS's multicloud website for additional features, tools, and a detailed white paper on this topic
  • Reach out to the author, Tom Goden, or the AWS team for further assistance in navigating multicloud strategies

Your Digital Journey deserves a great story.

Build one with us.

Cookies Icon

These cookies are used to collect information about how you interact with this website and allow us to remember you. We use this information to improve and customize your browsing experience, as well as for analytics.

If you decline, your information won’t be tracked when you visit this website. A single cookie will be used in your browser to remember your preference.