AWS Telco Network Builder Features

With AWS Telco Network Builder (TNB), communications service providers (CSPs) can define network requirements by using telecom industry standards. AWS TNB maps the requirements to a cloud architecture and provisions the right compute, storage, and networking resources automatically. AWS TNB simplifies network lifecycle management so that you can use a single service to deploy, update, and upgrade network functions. AWS TNB also provides a centralized dashboard so that you can monitor and manage your network functions and AWS services from one place.

AWS Infrastructure

AWS Outposts

AWS Telco Network Builder supports AWS Outposts, a family of fully managed solutions delivering AWS infrastructure and services to virtually any on-premises or edge location for a truly consistent hybrid experience. Outposts solutions allow you to extend and run native AWS services on premises, and is available in a variety of form factors, from 1U and 2U Outposts servers to 42U Outposts racks, and multiple rack deployments.

With AWS Outposts, you can run some AWS services locally and connect to a broad range of services available in the local AWS Region. Run applications and workloads on premises using familiar AWS services, tools, and APIs. Outposts supports workloads and devices requiring low latency access to on-premises systems, local data processing, data residency, and application migration with local system interdependencies.

AWS Local Zones

AWS Telco Network Builder supports AWS Local Zones, a type of infrastructure deployment that places compute, storage, database, and other select AWS services close to large population and industry centers.

Telecom industry compliance support

AWS TNB supports popular European Telecommunications Standards Institute (ETSI) SOL003 and SOL005 interfaces that make it easier for CSPs to integrate with ETSI-compliant service orchestrators.

Self-service interface using telecom industry standards

CSPs can define network services and network functions by using the AWS Telco Network Builder console, AWS Command Line Interface (CLI), or AWS Cloud Development Kit (CDK). The service and function definitions comply with industry standards by using the supported Topology and Orchestration Specification for Cloud Applications (TOSCA) format.

Automated lifecycle management

AWS TNB makes it easier for CSPs to manage network services on AWS. It helps you to deploy, upgrade, update, and terminate network services comprised of network functions by using underlying infrastructure resources such as AWS CloudFormation, Amazon Elastic Kubernetes Service (EKS), and Amazon Virtual Private Cloud (VPC).

Network service visibility

AWS TNB provides CSPs with visibility into network operations across planning, deployment, and operations for network functions. For example, you can plan by viewing network functions available but not in production and can view the status of service deployments. You can also manage operational tasks such as upgrades and terminations.

Flexible network service definitions

Create network service templates with or without a pipeline for all telecom workloads (RAN, Core, IMS, and Network and Enterprise Applications). AWS TNB gives you flexibility in defining, provisioning, deploying, updating, and upgrading your network services. To publish new definitions, developers can create a new service definition, use an existing template, or integrate with a continuous integration and continuous delivery (CI/CD) pipeline. Operations teams can use AWS TNB to help ensure that all deployments are updated.

Resource dependency management

AWS TNB automatically manages dependencies between resources during stack management actions. You don’t need to worry about specifying the order in which resources are created, updated, or deleted. AWS TNB determines the correct sequence of actions to take for each resource when performing stack operations.

Service version control

AWS TNB supports versioning of network service and network function templates, providing developers and operations engineers visibility into out-of-date deployments.