site-logo

JAWS PANKRATION 2024

site-logo
HomeNewsTimetableCfPCommitteePromotionFollow UpPrivacy Policy

Private Edge 5G: Are Multicloud or Multivendor Solutions the Key? Is eBPF the Ultimate tool to add?

Lv300

Lv300

8/24/2024 06:00 (UTC)
Session Info

This session will explore the power of applying eBPF to 5G Core deployments over Kubernetes, AWS Cloud, and RedHat OpenShift.

We'll discuss how eBPF enhances network performance, security, and the evolution of 5G technologies.

Starting with an overview of eBPF’s dynamic kernel tracing for improved routing, load balancing, and security, we'll address current private edge 5G deployment challenges and eBPF’s practical solutions.

We'll then delve into deploying a CNI with eBPF in a 5G Core solution over Kubernetes, concluding with a demonstration of LTERAN deployment and end-to-end communication.

Marco Antonio Gonzalez

Marco Antonio Gonzalez

- AWS Community Builders -

Session Category
End user computing
Networking and content distribution
Security
Identity and compliance
AWS Services
EKS
AWS services related to ROSA (Red Hat Openshift on AWS)
ECR
Session Materials
Session Archive
Session Summary (by Amazon Bedrock)
    The presentation is about implementing self-service for engineers in AWS Identity Center. The speaker, Yusuke from Yokohama, works as a software engineer at mixi and is involved in community activities. The session covers: 1. Overview of AWS Identity Center 2. Issues with centralized permission management 3. Proposed solution: delegating permission management AWS Identity Center simplifies single sign-on and user provisioning by connecting employee IDs to existing identity services. It allows users to access multiple AWS accounts with one set of credentials. The speaker discusses the challenges of centralized permission management in large organizations, where the central identity team may struggle to handle the increasing number of developer teams efficiently. To address this issue, the speaker proposes delegating AWS Identity Center management to unit-level identity teams. This approach allows for more efficient review and implementation of permission changes within each unit. The presentation outlines a technical stack for implementing delegated permission management, including: 1. Infrastructure as Code (e.g., AWS CloudFormation) 2. Version control systems (e.g., GitHub) 3. CI/CD services The speaker explains an architecture using Terraform, GitHub, and GitHub Actions to realize delegated permission management. This setup includes directory-based management, pull request reviews, and automated permission application. The roles of central and unit-level identity teams are defined, with the central team focusing on overall governance and the unit-level teams handling day-to-day permission management. The main benefit of this approach is enabling self-service permission setting without central IT team intervention, potentially improving development productivity.

Back

©JAWS-UG (AWS User Group - Japan). All rights reserved.