As part of your organization's monitoring plan, you have been tasked with obtaining and analyzing detailed information about the traffic sourced at one of your FortiGate EC2 instances.
I don't recall much about network access analyzer scopes, but it seems like a more advanced option that might not be necessary for basic traffic monitoring.
I practiced a similar question, and I feel like adding the EC2 instance to CloudWatch could help, but I'm not confident if it captures all traffic details.
This is a good one. I think option B is the way to go - creating a VPC flow log will give you the detailed traffic information you need for the FortiGate instance. Seems like the most straightforward solution.
Okay, let's see. I know CloudTrail is for capturing API calls, so that's not the right choice here. I'm leaning towards option B or D, but I'll need to double-check the details on those.
This looks like a straightforward question about monitoring traffic on a FortiGate EC2 instance. I think option B, creating a VPC flow log, is the best approach here.
I see both points, but I think option C could also be useful. Adding the EC2 instance as a target in CloudWatch can help collect traffic logs for analysis.
CloudTrail is for AWS API calls, not network traffic. And CloudWatch is more for aggregated metrics, not raw logs. I'd go with option B to create a VPC flow log.
Option B seems the most straightforward way to get detailed traffic info on the FortiGate EC2 instance. Flow logs at the network interface level should give you the insights you need.
Ellen
2 months agoBerry
2 months agoBonita
2 months agoFrancoise
3 months agoYun
3 months agoLauryn
3 months agoBette
4 months agoSherron
4 months agoFelix
4 months agoCarri
4 months agoTammara
4 months agoCatalina
4 months agoLera
5 months agoStevie
5 months agoJoanna
5 months agoKanisha
5 months agoMarleen
2 months agoVallie
2 months agoTonette
2 months agoRoosevelt
3 months agoJacklyn
6 months agoGenevieve
5 months agoEura
5 months agoRoxanne
7 months agoLouis
7 months ago