Week 08 - Solutions Architect Track - Network Observability Why network observability? - Troubleshoot network connectivity and performance - Understand and Optimize costs - Govern network security - Identify anamalous traffic pattern - Architect for availability and scale Overview of network observability: - Collect metrics and logs - Monitor alarms and flow logs using Cloud watch dashboard and metric filters - Analyse traffic mirroring , reachability analyzer , amazon cloud watch contributor insights, cloud watch log insights, Network access analyser, third party solutions VPC Flow logs: - Concerned about IP traffic going to and from network interface of VPC , concerned about capturing Header information. - Flow logs needs to be enabled explicitly as it is NOT enabled by default , which is an optional feature - Source could be VPC, Subnet, ENI - Destination can be Cloud Watch, Kinesis Data Firehose, S3 and later these can be analysed - It can capture logs from any service that have ENI, like EC2 service. - It DOES NOT capture some internal traffic like connecting Microsoft licence server. - VPC collects logs near real time - Doesn’t affect performance as flow log data is collected outside path of your network traffic. - Allows to customise the data format for flow logs - 5 Tuple - Source IP / Destination IP / Source Port / Dest Port / Protocol Virtual Mirroring: - Mirroring is encapsulated with VXLAN header, which is Virtual Extensible LAN is a network virtualisation technology - VPC Flow Logs Vs VPC Traffic Mirroring
@@be-SA Done. I think, This is the first time for me posting UA-cam content in Linkedin :) I will share BeSA video as a reference to my blogs to linked posts going forward. Thanks
Excellent session, learned alot from the live demo of services in AWS console, wish to see more demos like this. Great effort 👍
Thank you, Ashish, Parna, and Kapil for a wonderful presentation.
Thank you, Ashish sir, for giving us such a clear and comprehensive understanding of this.
Good one, learned many new services and concepts in network observability in AWS context.
Thanks for the sample questions
Week 08 - Solutions Architect Track - Network Observability
Why network observability?
- Troubleshoot network connectivity and performance
- Understand and Optimize costs
- Govern network security
- Identify anamalous traffic pattern
- Architect for availability and scale
Overview of network observability:
- Collect metrics and logs
- Monitor alarms and flow logs using Cloud watch dashboard and metric filters
- Analyse traffic mirroring , reachability analyzer , amazon cloud watch contributor insights, cloud watch log insights,
Network access analyser, third party solutions
VPC Flow logs:
- Concerned about IP traffic going to and from network interface of VPC , concerned about capturing Header information.
- Flow logs needs to be enabled explicitly as it is NOT enabled by default , which is an optional feature
- Source could be VPC, Subnet, ENI
- Destination can be Cloud Watch, Kinesis Data Firehose, S3 and later these can be analysed
- It can capture logs from any service that have ENI, like EC2 service.
- It DOES NOT capture some internal traffic like connecting Microsoft licence server.
- VPC collects logs near real time
- Doesn’t affect performance as flow log data is collected outside path of your network traffic.
- Allows to customise the data format for flow logs
- 5 Tuple - Source IP / Destination IP / Source Port / Dest Port / Protocol
Virtual Mirroring:
- Mirroring is encapsulated with VXLAN header, which is Virtual Extensible LAN is a network virtualisation technology
- VPC Flow Logs Vs VPC Traffic Mirroring
Really nice summary. Worth putting in a LinkedIn post
@@be-SA Done. I think, This is the first time for me posting UA-cam content in Linkedin :) I will share BeSA video as a reference to my blogs to linked posts going forward. Thanks