SD-WAN Multicloud
Apply consistent policies to applications spread across clouds.
Software-defined WAN (SD-WAN) applies policies over compatible IP access. It suits application-based paths; distinguish networking, cloud routing and recovery.
Orchestration alone does not correct poor access, identity or security architecture.
Let’s talk
How it works
Apply shared policies to applications spread across clouds.
Sites and users
SD-WAN policies
Cloud applicationsApplications do not all use the same entry
Distinguish private tenant workloads from public SaaS. The edge applies policies over compatible access; cloud integrations define how each network is reached.
Define site-to-cloud routing and cloud-to-cloud routing where supported. Tunnels or a private connection do not amount to a complete security policy.
Sites and users
SD-WAN policies
Cloud applicationsObserve the application and both directions
A path change can improve degraded access, but also check return routes, gateway limits and cloud-service load.
Test voice, long sessions and critical flows with the real policy. Choosing another circuit does not solve every SaaS problem.
Sites and users
SD-WAN policies
Cloud applicationsRecover the path, not recreate the application
Policy can use an operational alternative when access, routes and capacity are prepared. A cloud-region outage additionally requires an application and data plan.
Separate a circuit-failure test from recovery in another region. The latter includes dependencies outside WAN control.
Illustrative case: from situation to decision
- Situation
- Voice uses a public service while a critical application runs in a private cloud network.
- Option
- Define application policies; consider DCA Router when the need is inter-domain routing.
- Check
- Test each flow, its return path and the response to a circuit or region outage.
SD-WAN policy does not replace CSP configuration, security or data recovery.
Decisions for your project
- Destinations
- SaaS or private networks, regions and cloud-to-cloud requirements.
- Policy
- Application classes, access, segmentation and return routes.
- Recovery
- Network fallback separated from the data and application plan.
From design to operation
Pilot one application and an alternative path before extending policies across sites and clouds.
Complements, alternatives and variants
Product sources
What challenge would you like to solve?
Tell us what is happening and what needs to change. You do not need to know the catalogue.
What happens next?
- Understand the context
What’s changing, where your teams work and what cannot fail. Still defining the brief? We can help structure it.
- Design the options
Bring needs, Colt capabilities and technical criteria together. Compare alternatives and explain dependencies and limits.
- Validate before committing
Coverage, feasibility, responsibilities and terms. A commercial proposal is developed with the relevant specialists.
ColtPlatinum guides the project and coordinates commercial discussions and follow-up. Colt validates feasibility, enters into the service contract, and provisions, installs and delivers the services.
Availability, coverage, capabilities, SLAs and timelines are subject to technical validation and contract. No diagram is a service guarantee.