# Unicast

Unicast is a network delivery method in which a sender addresses each packet to one destination rather than to a group of receivers.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/unicast

> Unicast underpins most cloud application traffic, including API requests, database connections, and web downloads. It provides straightforward per-client communication, but delivering identical content separately to many receivers can multiply bandwidth consumption, making multicast or edge caching useful alternatives for suitable workloads.

Practice exams covering Unicast: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty).

## 6 key aspects of Unicast

Unicast provides flexible one-to-one delivery, but repeated distribution of identical data requires careful bandwidth planning and workload-appropriate optimization.

1. **Single-destination delivery**: Each packet targets one destination rather than a receiver group. An application serving many clients typically maintains multiple unicast exchanges.
2. **Bandwidth scales with repeated delivery**: Sending identical data separately to more receivers increases source traffic and load on shared network paths. Estimate aggregate throughput as per-receiver bitrate multiplied by receiver count, then account for overhead and retransmissions.
3. **Broad application compatibility**: Unicast supports common request-response applications over private or public networks. It works with both TCP and UDP and does not require multicast group membership.
4. **Independent client behavior**: Separate exchanges support individualized responses, authentication, and client-specific pacing. This flexibility is valuable when receivers need different data or consume it at different times.
5. **Optimization through caching or group delivery**: Caching reduces repeated origin transfers while preserving unicast delivery to clients. Multicast instead reduces duplicate transmission on shared paths when identical data, compatible applications, and network support make group delivery appropriate.
6. **No inherent reliability or security guarantee**: Unicast specifies delivery addressing, not guaranteed arrival, ordering, or confidentiality. Select transport protocols, retry behavior, and encryption separately.

## Cloud services for Unicast

EC2 applications use VPC networking for ordinary unicast communication, with Transit Gateway providing routed connectivity between attached networks where needed. For repeated delivery of cacheable objects, CloudFront can serve cached copies closer to users and reduce traffic reaching the EC2 or other configured origin. Viewer delivery remains unicast. For compatible applications distributing identical feeds simultaneously, Transit Gateway multicast provides a separate group-delivery option within its supported scope. Select between these patterns by measuring duplicate payload volume, origin capacity, cacheability, receiver requirements, and transfer charges rather than assuming one method always minimizes cost.

- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: CloudFront delivers content to viewers using unicast connections and can cache reusable responses at edge locations. Cache hits reduce origin traffic rather than converting delivery into multicast or eliminating viewer-side transfer.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon VPC provides the networking environment for private unicast communication among cloud resources. Route tables, security groups, and network ACLs affect reachability; ordinary VPC networking does not natively forward IP multicast.
- **[AWS Transit Gateway](https://blowstack.com/tools/cloud-services-hub/aws-transit-gateway)**: Transit Gateway connects networks for routed unicast communication and also supports multicast through explicitly configured multicast domains in supported configurations. Its multicast capability can reduce source-side duplication for compatible group-delivery workloads, but it does not extend multicast across every attachment type.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: EC2 instances commonly originate and receive unicast application traffic. Instance network bandwidth and packet-processing limits matter when a server sends separate copies of the same data to many clients.

## Unicast exam questions

Real practice exam questions on Unicast, with the correct answer and its explanation.

### Question 1 (ANS-C01)

**Question:**

A company distributes a live 10-Mbps UDP telemetry feed from a Nitro-based EC2 publisher in one AWS Region to 60 EC2 consumers in that Region and 60 consumers in a second Region. Each Region has several VPCs attached to its own multicast-enabled AWS Transit Gateway. The transit gateways have an inter-Region peering attachment. Currently, the publisher sends a separate unicast stream to every consumer.

The applications support IPv4 multicast and IGMPv2. The company can deploy a Nitro-based EC2 relay that receives one unicast stream and republishes it. It must reduce inter-Region payload traffic to approximately 10 Mbps and publisher outbound payload traffic to no more than 20 Mbps. Any relay must transmit no more than 10 Mbps of payload, regardless of the number of consumers. The UDP feed cannot be converted to HTTP, and all required security rules can be configured.

Which architecture meets these requirements?

**Correct answer:** Configure multicast domains and participant subnet associations separately in each Region. Have the publisher send one multicast stream to local consumers and one unicast stream over the peering attachment to a relay in the second Region. Have the relay originate a multicast stream for that Region's consumers.

**Explanation:** Transit Gateway performs multicast replication within each Region's configured multicast domain. The publisher sends 10 Mbps locally and 10 Mbps to the remote relay, meeting its 20-Mbps limit. Only one 10-Mbps stream crosses Regions, and the relay transmits one 10-Mbps multicast stream regardless of receiver count. Receiver group membership and the relevant attachment subnet associations must be configured in each Region.

## Practice Unicast in a full exam

Questions on Unicast in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 1 question

## What is Unicast

Unicast describes one-to-one packet delivery: a sender transmits a packet addressed to an individual destination. A server can communicate with thousands of clients simultaneously, but each client receives its own unicast traffic. The defining property is the destination of each transmission, not the number of clients the application serves overall. Unicast works with IPv4 and IPv6 and does not require a particular transport protocol; both TCP and UDP can carry unicast traffic.

Most cloud workloads use unicast by default. Examples include an application calling an HTTPS API, a virtual machine querying a database, and a browser downloading an object. Routing selects a path toward the destination, while security controls determine whether the traffic is permitted. Private addressing does not change the delivery method: communication between two private IP addresses is still unicast. A load balancer also does not turn application traffic into multicast; client-to-load-balancer and load-balancer-to-backend communication remain separate delivery paths.

The main bandwidth trade-off appears when many receivers need identical data. If a source sends a 5 Mbps live stream separately to 200 receivers, its outbound payload rate is approximately 1 Gbps, before protocol overhead and retransmissions. Each copy consumes capacity wherever its path overlaps with other copies. This can exhaust instance network capacity or shared links and can increase transfer or processing charges, depending on the services, Regions, Availability Zones, and network components involved.

Multicast addresses this duplication differently. A sender transmits to a multicast group, and a multicast-capable network replicates packets where paths diverge toward interested receivers. For synchronized, identical UDP feeds within a supported network, multicast can substantially reduce traffic on shared links. However, it requires compatible applications, group membership management, and explicit network support. It is not a general replacement for personalized HTTPS responses, and multicast itself does not guarantee delivery or retransmit lost packets. Ordinary Amazon VPC networking does not provide native IP multicast forwarding; AWS Transit Gateway offers multicast within supported configurations.

A content delivery network provides another approach while retaining unicast delivery to clients. For example, Amazon CloudFront can cache a versioned software package near users rather than repeatedly retrieving it from an origin. Users still receive separate unicast responses, but cache hits reduce origin requests and origin-side bandwidth. This does not eliminate the bytes delivered to viewers. Savings depend on cacheability, cache keys, expiration settings, geographic demand, and pricing; personalized or uncacheable responses may gain little origin-bandwidth reduction.

Choose the optimization according to the traffic pattern. Unicast suits database transactions, individualized API responses, and small receiver populations. Edge caching suits repeatedly requested static objects and cacheable media segments. Multicast can suit simultaneous distribution of identical feeds to receivers on a supported network. Compression, conditional requests, and avoiding unnecessary polling can also reduce unicast traffic without changing the delivery model.

Operationally, measure source throughput, receiver count, cache hit ratio, packet loss, and the links or billing boundaries crossed by each copy. Use flow records, interface metrics, and application telemetry together; traffic volume alone does not reveal whether responses contain duplicate content. Finally, do not confuse unicast with reliability or encryption. TCP can provide ordered, reliable transport, UDP does not provide those guarantees, and encryption requires an additional mechanism such as TLS. These properties are independent of one-to-one addressing.
