AWS Certified Advanced Networking Specialty Boot Camp in Singapore

Unlock the potential of advanced networking on AWS with the DreamsPlus AWS Certified Advanced Networking Specialty Boot Camp in Singapore. This immersive training program is tailored to equip you with the essential skills and in-depth knowledge required to master AWS networking services and architecture. Combining theoretical insights with hands-on practical experience, our boot camp ensures you’re fully prepared to earn your AWS Certified Advanced Networking Specialty certification.

Course Overview

At DreamsPlus, we are committed to offering more than just a certification. Our AWS Certified Advanced Networking Specialty Boot Camp provides a comprehensive pathway to mastering advanced networking on AWS. This course delves into advanced networking concepts and practices, critical for managing today’s cloud-based infrastructure in Singapore. Here’s a closer look at what you’ll learn:

• Advanced Networking Concepts: Explore advanced networking protocols, routing techniques, and hybrid networking architectures necessary for AWS environments.
• AWS Networking Services and Architecture: Gain expert-level knowledge of AWS networking services such as VPC, Direct Connect, Route 53, and more. Learn best practices for designing resilient, scalable, and highly available network architectures.
• Designing and Implementing Scalable and Secure Networks: Understand how to design, implement, and manage scalable, secure networks on AWS. Learn strategies for network security, optimization, and monitoring to ensure efficiency.
• Interactive Workshops: Participate in hands-on workshops designed to simulate real-world networking scenarios, providing you with practical experience and skills that can be directly applied to your role.

Join the growing tech community in Singapore and take your AWS networking expertise to the next level with DreamsPlus.

Syllabus 

• Domain 1: Network Design (30% of scored content)
• Domain 2: Network Implementation (26% of scored content)
• Domain 3: Network Management and Operation (20% of scored content)
• Domain 4: Network Security, Compliance, and Governance (24% of scored content)

Domain 1: Network Design

Task Statement 1.1: Design a solution that incorporates edge network services to optimize user performance and traffic management for global architectures.

• Patterns for using content distribution networks (like Amazon CloudFront) in design
• Global traffic management design patterns, such as those seen in AWS Global Accelerator
• Patterns of integration for global traffic management and content distribution networks with other services (such Amazon API Gateway and Elastic Load Balancing [ELB]).

Task Statement 1.2: Design DNS solutions that meet public, private, and hybrid Requirements.

• DNS protocol (for example, DNS records, TTL, DNSSEC, DNS delegation,zones)

• DNS logging and monitoring
• Amazon Route 53 features (for example, alias records, traffic policies, resolvers, health checks)

• Integration of Route 53 with other AWS networking services (for example, Amazon VPC)

• Integration of Route 53 with hybrid, multi-account, and multi-Region options

• Domain registration

Task Statement 1.3: Design solutions that integrate load balancing to meet high availability, scalability, and security requirements.

• How load balancing works at layer 3, layer 4, and layer 7 of the OSI model
• Different types of load balancers and how they meet requirements for network design, high availability, and security

• Connectivity patterns that apply to load balancing based on the use case (for example, internal load balancers, external load balancers)

• Scaling factors for load balancers
• Integrations of load balancers and other AWS services (for example, Global Accelerator, CloudFront, AWS WAF, Route 53, Amazon Elastic Kubernetes Service [Amazon EKS], AWS Certificate Manager [ACM])

• Configuration options for load balancers (for example, proxy protocol, cross-zone load balancing, session affinity [sticky sessions], routing algorithms)

• Configuration options for load balancer target groups (for example, TCP, GENEVE, IP compared with instance)

• AWS Load Balancer Controller for Kubernetes clusters
• Considerations for encryption and authentication with load balancers (for xample, TLS termination, TLS passthrough)

Task Statement 1.4: Define logging and monitoring requirements across AWS and hybrid networks.

• Metrics, agents, logs, alerts, dashboards, and insights from Amazon CloudWatch in AWS designs to offer transparency
• AWS Transit Gateway Network Manager for visibility in architectures
  • VPC Reachability Analyzer for visibility in architectures
• Traffic mirroring and flow logs in architectures to offer visibility
• Access logging (using CloudFront and load balancers, for instance)

Task Statement 1.5: Design a routing strategy and connectivity architecture between on-premises networks and the AWS Cloud.

• The principles of routing (dynamic versus static, BGP, etc.)
• Concepts for physical interconnects at Layers 1 and 2 (such as VLAN, link aggregation group [LAG], optics, and jumbo frames)
• Technologies for encapsulation and encryption, such as Generic Routing IPsec encapsulation [GRE]
• Sharing resources throughout AWS accounts
• Network overlays

Task Statement 1.6: Design a routing strategy and connectivity architecture that include multiple AWS accounts, AWS Regions, and VPCs to support different connectivity patterns.

• Different connectivity patterns and use cases (for example, VPC peering, Transit Gateway, AWS PrivateLink)

• Capabilities and advantages of VPC sharing
• IP subnets and solutions accounting for IP address overlaps

Domain 2: Network Implementation

• Routing protocols (for example, static, dynamic)
• VPNs (for example, security, accelerated VPN)
• Layer 1 and types of hardware to use (for example, Letter of Authorization [LOA] documents, colocation facilities, Direct Connect)

• Layer 2 and layer 3 (for example, VLANs, IP addressing, gateways, routing, switching)

• Traffic management and SD-WAN (for example, Transit Gateway Connect)
• DNS (for example, conditional forwarding, hosted zones, resolvers)
• Security appliances (for example, firewalls)
• Load balancing (for example, layer 4 compared with layer 7, reverse proxies, layer 3)

• Infrastructure automation
• AWS Organizations and AWS Resource Access Manager (AWS RAM) (for example, multi-account Transit Gateway, Direct Connect, Amazon VPC, Route 53)

• Test connectivity (for example, Route Analyzer, Reachability Analyzer)
• Networking services of VPCs

Task Statement 2.2: Implement routing and connectivity across multiple AWS accounts, Regions, and VPCs to support different connectivity patterns.

• Connectivity between many accounts and VPCs (such as multi-protocol label switching [MPLS], third-party suppliers, Transit Gateway, VPN, and VPC peering).
  • Connectivity for private applications (like PrivateLink, for instance)
  • Techniques for increasing AWS networking connectivity (like AWS RAM for organizations)
  • Application and client host and service name resolution (DNS, for instance)
  • automation of infrastructure;
  • Authorization and authentication (SAML, Active Directory, etc.)
  • Security (such as AWS Network Firewall, network ACLs, and security groups)
  • Check connectivity using tools such as reachability and route analyzers.

Task Statement 2.3: Implement complex hybrid and multi-account DNS architectures.

• When to utilize public and private hosted zones
• Techniques for changing traffic control (depending on weighting, region, or latency, for instance).
• DNS forwarding and delegation (conditional forwarding, for instance)
• Various types of DNS records (such as pointer records, alias records, TXT, A, AAAA, and TXT records).
• DNS Security
• How several accounts (like AWS RAM) can share DNS services
• Outbound and inbound requirements and implementation alternative Final Destinations.

Task Statement 2.4: Automate and configure network infrastructure.

• Infrastructure as Code (IaC): This includes AWS CloudFormation, AWS Cloud Development Kit (AWS CDK), AWS CLI, AWS SDK, and APIs.
• Frequently occurring issues with hard coded instructions in IaC templates for cloud networking resource provisioning;
• Event-driven network automation.

Domain 3: Network Management and Operation

Task Statement 3.1: Maintain routing and connectivity on AWS and hybrid networks.

• Industry-standard routing technologies (such BGP over Direct Connect) that are utilized in AWS hybrid networks
• AWS and hybrid network connectivity techniques (like Direct Transit gateways, VIFs, and connect gateways

• The impact of quotas and limitations on AWS networking services (for instance, limitations on routes and bandwidth

• The ways that the public and private sectors can acquire customized services (for for instance, VPC peering and PrivateLink)

• Available inter-Regional and intra-Regional communication patterns

Task Statement 3.2: Monitor and analyze network traffic to troubleshoot and optimize connectivity patterns.

• Metrics measuring network performance and reachability limitations (such as packet size and routing)
• The right logs and measurements, such as packet loss, to evaluate network performance and reachability problems
• Logging and metrics collection and analysis tools (e.g., CloudWatch, VPC Flow Logs, VPC Traffic Mirroring)
• Tools (such as Reachability Analyzer and Transit Gateway Network Manager) to examine routing patterns and problems

Task Statement 3.3: Optimize AWS networks for performance, reliability, and cost- effectiveness.

• circumstances where a transit gateway or a VPC peer is suitable;
  • Diverse approaches to lower bandwidth consumption (e.g., CloudFront, unicast as opposed to multicast).
• Reasonably priced connectivity choices for data transfer between on-premises settings and a virtual private cloud
• AWS network interface types;
  • High-availability features in Route 53 (e.g., DNS load balancing utilizing weighted record sets and health checks with latency)
  • Dependability of Route 53’s options;
  • Traffic distribution patterns and load balancing;
  • VPC subnet optimization;
  • Frame size optimization for capacity across various connection types

Domain 4: Network Security, Compliance, and Governance

• Distinct threat models according to the architecture of the application
• Typical security risks
• Techniques for safeguarding various application flows
• An Amazon network architecture that complies with security and legal specifications

Task Statement 4.2: Validate and audit security by using network monitoring and logging services.

Knowledge of:

• Network monitoring and logging services that are available in AWS (for example, CloudWatch, AWS CloudTrail, VPC Traffic Mirroring, VPC Flow Logs, Transit Gateway Network Manager)

• Alert mechanisms (for example, CloudWatch alarms)
• Log creation in different AWS services (for example, VPC flow logs, load alancer access logs, CloudFront access logs)

• Log delivery mechanisms (for example, Amazon Kinesis, Route 53, CloudWatch)

• Mechanisms to audit network security configurations (for example, security groups, AWS Firewall Manager, AWS Trusted Advisor)

Task Statement 4.3: Implement and maintain confidentiality of data and communications of the network.

• Network encryption options that are available on AWS
• VPN connectivity over Direct Connect
• Encryption methods for data in transit (for example, IPsec)
• Network encryption under the AWS shared responsibility model
• Security methods for DNS communications (for example, DNSSEC)