This whitepaper is for historical reference only. Some content might be outdated and some links might not be available.
Example architecture #2
An example architecture of a 5GC workload with AWS Outposts. The 5G control plane and user plane are running on-premises.

Architecture of 5G core on AWS Outposts
Security description of the example architecture of 5G core network function on AWS Outposts:
-
VPC routing tables. As an example, customers can direct the user plane or internet traffic to on-premises network using the AWS Outposts local gateway.
-
Traffic going in and out of the instances are filtered using security groups. In addition, there are network ACL rules that can filter traffic on a subnet level. Network ACLs are stateless firewall rules.
-
Nitro hardware-based instances.
-
Persistent data at rest stored in EBS volumes.
-
Access to AWS services that do not reside inside the VPC is through VPC endpoints.
-
Snapshots, AMIs, manifest files, or backup data can be stored in Amazon S3 storage. Data at rest is encrypted using AWS KMS, and access to data can be restricted with IAM policies.
-
AWS Direct Connect instances.
-
AWS KMS for management of encryption keys.
-
AWS Certificate Manager to manage imported SSL/TLS certificates.
-
Amazon ECR is used to store container images.
-
Amazon EKS service is used for Kubernetes-based container orchestration.
-
AWS CloudTrail helps enable governance, and supports operational and risk auditing of an AWS account.
-
Amazon CloudWatch monitors AWS resources and applications that run on AWS in near real-time.
-
AWS Config provides a detailed view of the configuration of AWS resources in an AWS account.
-
AWS CloudFormation helps set up AWS resources automatically.
-
AWS WAF helps protect application endpoints or APIs against common web exploits and bots.
-
AWS IAM helps to securely control access to AWS resources.
-
AWS Control Tower provides a simple way to set up and govern a secure, multi-account AWS environment.
-
VRF devices, virtual router, and forwarding devices are used to segregate the VPN.
-
Customer SEGs are entities on the borders of the IP security domains used for securing native IP based protocols.
-
Customer owned on-premises HSM to generate cryptographic keys for importing to AWS KMS or use with AWS KMS XKS.