<h2><strong>Cloud Networking and its Impact on Streaming Services</strong></h2>
<h2><img loading="lazy" decoding="async" class="alignnone size-medium wp-image-13110" src="https://apiblog.cloudastra.co/wp-content/uploads/2025/02/DISH-Technologies-Transforming-Network-Infrastructure-with-AWS-CloudWAN-300x300.png" alt="" width="300" height="300" srcset="https://apiblog.cloudastra.co/wp-content/uploads/2025/02/DISH-Technologies-Transforming-Network-Infrastructure-with-AWS-CloudWAN-300x300.png 300w, https://apiblog.cloudastra.co/wp-content/uploads/2025/02/DISH-Technologies-Transforming-Network-Infrastructure-with-AWS-CloudWAN-150x150.png 150w, https://apiblog.cloudastra.co/wp-content/uploads/2025/02/DISH-Technologies-Transforming-Network-Infrastructure-with-AWS-CloudWAN-768x768.png 768w, https://apiblog.cloudastra.co/wp-content/uploads/2025/02/DISH-Technologies-Transforming-Network-Infrastructure-with-AWS-CloudWAN-96x96.png 96w, https://apiblog.cloudastra.co/wp-content/uploads/2025/02/DISH-Technologies-Transforming-Network-Infrastructure-with-AWS-CloudWAN.png 1024w" sizes="auto, (max-width: 300px) 100vw, 300px" /></h2>
<p>&nbsp;</p>
<h3 data-start="482" data-end="503"><strong data-start="485" data-end="501">Introduction</strong></h3>
<p data-start="505" data-end="884">DISH Technologies (DISH Tech) is a pioneer in satellite television and broadband services and a wholly-owned subsidiary of EchoStar. Since its establishment in 1980, DISH Tech has continually innovated in digital entertainment and cloud networking solutions. The company provides satellite TV, high-speed internet, and on-demand content to residential and commercial customers.</p>
<p data-start="886" data-end="1164">In 2015, DISH launched SLING TV, the world’s first live TV streaming service. As a leading over-the-top (OTT) platform, SLING TV integrates cloud DVR and extensive content packages. When combined with AirTV, it offers a seamless blend of live, recorded, and local programming</p>
<p data-start="1166" data-end="1551">To keep up with increasing demand and scalability challenges, DISH Tech needed to modernize its cloud networking infrastructure. Their previous setup relied on a complex mesh of IPSec tunnels connecting multiple data centers and AWS regions. However, this approach led to inefficiencies, including limited scalability, high management overhead, and frequent connectivity disruptions.</p>
<p data-start="1553" data-end="1850">To overcome these challenges, DISH Tech adopted AWS CloudWAN, a fully automated, centrally managed, and highly segmented WAN solution. This blog explores why AWS CloudWAN was selected, provides a technical overview of its deployment, discusses key benefits, and outlines future enhancements.</p>
<h3 data-start="1852" data-end="1878"><strong data-start="1855" data-end="1876">Why AWS CloudWAN?</strong></h3>
<p data-start="1880" data-end="2073">DISH Tech sought an advanced cloud networking solution to simplify network management, improve automation, and enhance security. AWS CloudWAN addressed their challenges in the following ways:</p>
<h4 data-start="2075" data-end="2151"><strong data-start="2079" data-end="2149">1. Transitioning from a Partial Mesh to Hub-and-Spoke Architecture</strong></h4>
<p data-start="2152" data-end="2438">Previously, DISH Tech used a partial mesh network, which was difficult to manage. The transition to a hub-and-spoke model streamlined connectivity by using AWS CloudWAN as the central hub, allowing seamless communication between data centers and AWS virtual private clouds (VPCs).</p>
<h4 data-start="2440" data-end="2490"><strong data-start="2444" data-end="2488">2. Automation and Centralized Management</strong></h4>
<p data-start="2491" data-end="2820">The legacy network lacked automation, requiring manual configuration. AWS CloudWAN’s centralized policy framework enabled full automation via CI/CD pipelines, eliminating human errors and improving efficiency. All network policies are now stored in a machine-readable JSON format, ensuring controlled and automated updates.</p>
<h4 data-start="2822" data-end="2862"><strong data-start="2826" data-end="2860">3. Scalability and Flexibility</strong></h4>
<p data-start="2863" data-end="3044">Manually managing network expansions was time-consuming. AWS CloudWAN provided dynamic attachments and segmentation, allowing DISH Tech to scale its infrastructure seamlessly.</p>
<h4 data-start="3046" data-end="3100"><strong data-start="3050" data-end="3098">4. Improved Routing and Network Segmentation</strong></h4>
<p data-start="3101" data-end="3307">DISH Tech needed a structured segmentation strategy to isolate traffic between business units and environments. AWS CloudWAN introduced dynamic routing, optimizing traffic flow and improving security.</p>
<h4 data-start="3309" data-end="3361"><strong data-start="3313" data-end="3359">5. Reliable and Self-Healing IPSec Tunnels</strong></h4>
<p data-start="3362" data-end="3618">The previous network suffered from frequent tunnel failures and relied on expensive firewall hardware. AWS CloudWAN improved network resilience by offering backup tunnels and automated failover mechanisms, reducing downtime and maintenance costs.</p>
<h3><strong>Technical Overview of DISH Tech’s Cloud Networking Setup</strong></h3>
<p>DISH Tech’s AWS CloudWAN deployment is structured into two primary connectivity paths:</p>
<h4><strong>Connectivity Path 1: Hybrid Connectivity Between DISH Tech On-Premises Physical Data Centers and DISH Tech AWS Cloud Network</strong></h4>
<p>As a security requirement, the Sling Legacy environment needed to be kept separate from the new Control Tower environment. To achieve this, DISH Tech defined distinct segments for each environment. A core design principle was to separate production and non-production traffic in both environments, while allowing a shared segment only for applications that required access to common services.</p>
<p>The first connectivity path aimed to link between all of DISH Tech’s on-premises physical data centers and from the on-premises physical data centers to their AWS cloud network. The first part for interconnection of the data centers was achieved by creating a hub and spoke model, with the data centers connecting to each other through the CloudWAN network. The second part, of connecting the on-premises data centers to the AWS cloud network was done by creating a separate on-premises segment for the Sling Legacy environment and another for the Control Tower environment. The on-prem segment provides both functionalities, namely the data center to data center connectivity and the data centers to AWS connectivity. Traffic on these different on-premises segments was isolated from each other by using the Cloud WAN policy configuration.</p>
<div><img decoding="async" style="width: 80%; height: auto;" src="https://d2908q01vomqb2.cloudfront.net/c5b76da3e608d34edb07244cd9b875ee86906328/2025/01/24/Fig-1-Dish-Tech-Global-Network-architecture-with-Hybrid-Connectivity-Path.jpg" alt="Dish Tech Global Network architecture with Hybrid Connectivity Path" /></div>
<h4><strong>Connectivity Path 2: AWS CloudWAN for Inter-Connectivity Across AWS Regions</strong></h4>
<p>As discussed in the first connectivity path, one of the core designing principles of the network was to have no communication between production and non-production segments. There was also a nuanced difference between the two environments in terms of connectivity to the Cloud WAN network. The Sling legacy environment was making use of AWS Transit Gateways attachments to CloudWAN, while the Control Tower environment would have inter-VPC communication through VPC Attachments to CloudWAN. Having this nuanced difference in terms of connectivity to the AWS CloudWAN network, the Sling legacy business unit was able to make continuous use of its existing AWS Transit Gateways and the VPCs attached to them. Sling achieved this by peering their existing Transit Gateways with Cloud WAN. This provided Sling with the route segmentation across multiple regions that they initially lacked in their previous design.</p>
<div><img decoding="async" style="width: 80%; height: auto;" src="https://d2908q01vomqb2.cloudfront.net/c5b76da3e608d34edb07244cd9b875ee86906328/2025/01/24/Fig-2-Dish-Tech-AWS-inter-connectivity-architecture-through-AWS-CloudWAN.jpg" alt="Dish Tech AWS inter-connectivity architecture through AWS CloudWAN" /></div>
<p>In the figure, there are four segments of the DISH Tech CloudWAN network shown. The VPCs are attached to the Control Tower segments (Prod and Non-Prod segments, respectively) through the VPC core network attachment types. The VPCs in the Control Tower environment leverage a distributed inspection model, having AWS Gateway Load Balancer endpoints route traffic to distributed third-party firewalls behind Gateway Load Balancers. The Gateway Load Balancers have not been shown in the diagram for simplicity.</p>
<p>The VPCs in the Sling Legacy environment were initially connected to Transit Gateways specific to their environment. By separating the DISH Tech Cloud WAN into distinct segments for Sling Legacy and Control Tower, DISH Tech was able to utilize the existing Transit Gateways. They did this by using Transit Gateway route table attachments for the respective Sling Legacy segments. This approach also allowed the Sling Legacy environment to benefit from a centralized inspection model, with one centralized inspection VPC for each region, tailored to the needs of their business units.</p>
<h3><strong>Results and Future Plans</strong></h3>
<p>With the first set of the AWS CloudWAN deployment, DISH Tech built a highly segmented, secure, and hub-and-spoke network topology, providing connectivity between their different business units and their physical data centers. With this approach, DISH Tech reduced the complexity of mesh topology and established a transparent, centralized network connectivity model. The management of the various network segments between different business units and deployment environments is now more controlled. Centralized networking via CloudWAN enables DISH Tech’s infrastructure teams to maintain the hybrid connectivity and addition of new network workloads in an automated fashion.</p>
<p>By using the power of tagging and automation through DISH Tech’s CI/CD Pipelines and AWS Cloud WAN&#8217;s core network policy, DISH Tech deployed a fully automated infrastructure-as-code network. This expedited DISH Tech’s vision of automation and centralized management of the key constructs of their network. Tagging changes on the Cloud WAN attachment level would trigger the CI/CD Pipelines to automatically add the new attachments to the specific segments. Any new VPC or any new environment now gets attached to the respective Cloud WAN segment through tagging and inherits the correct routing domains through dynamic routing. Given the flexibility of API-driven Cloud WAN functionality, changes are now seamless and managed through Infrastructure-as-Code.</p>
<p>DISH Tech now monitors and manages their network connectivity statuses and health through a centralized Amazon CloudWatch dashboard, which shows them the state of the IPSec tunnels and the amount of traffic in and out of the entire network through Amazon CloudWatch metrics. They have also implemented alert mechanisms to notify them when traffic exceeds certain thresholds or when any tunnels encounter connectivity issues. This has reduced the time spent on operations and has led to faster deployments and quicker development of other business-critical functions.</p>
<p>Next step in the evolution of the DISH Tech network journey, as the traffic bandwidth requirements grow, the IPSec tunnels could be replaced with AWS Direct Connect Connections. AWS Direct Connect links the customer’s on-premises network to an AWS Direct Connect location. With this, DISH Tech will have dedicated physical connectivity from their data centers to their AWS regions by terminating the Direct Connect connections on the transit gateways attached to their CloudWAN network segments. Since Direct Connect provides a direct connection to AWS and does not go over the internet, any latency or jitter issues experienced by IPSec tunnels over the internet can be mitigated, and performance improvements will be observed.</p>
<h3 data-start="5335" data-end="5396"><strong data-start="5339" data-end="5394">Future Enhancements: AWS Direct Connect Integration</strong></h3>
<p data-start="5397" data-end="5738">To further improve performance, DISH Tech plans to integrate AWS Direct Connect. This will replace IPSec tunnels with dedicated low-latency private connections between their data centers and AWS. Direct Connect will enhance reliability and reduce network congestion, ensuring a high-performance cloud networking infrastructure.</p>
<h3><strong>Conclusion</strong></h3>
<p data-start="5761" data-end="6210">DISH Tech’s cloud networking transformation with AWS CloudWAN has provided a robust, scalable, and automated network infrastructure. By adopting a hub-and-spoke architecture, leveraging CI/CD automation, and implementing network segmentation, DISH Tech has significantly improved operational efficiency. The centralized management model allows for faster deployments, stronger security, and seamless network expansions.</p>
<p data-start="6212" data-end="6535">Looking ahead, integrating AWS Direct Connect will further optimize network performance by reducing latency and enhancing reliability. This strategic evolution underscores<a href="https://cloudastra.co/blogs/the-crucial-role-of-solution-delivery-in-the-tech-industry"> the crucial role of solution delivery in the tech industry</a>, ensuring DISH Tech remains at the forefront of cloud networking advancements.</p>
<p data-start="6212" data-end="6535">Do you like to read more educational content? Read our blogs at<a href="https://www.cloudastra.co/blogs"> Cloudastra Technologies</a> or contact us for business enquiry at <a href="https://www.cloudastra.co/contact">Cloudastra Contact Us</a>.</p>


DISH Tech's AWS CloudWAN network architecture overview

Blog Details

DISH Technologies Transforming Network Infrastructure with AWS CloudWAN

DISH Technologies Transforming Network Infrastructure with AWS CloudWAN

Share This Article

Follow Us