What should a solutions architect do to meet these requirements?
Use AWS WAF to protect both APIs. Configure Amazon Inspector to analyze the legacy API. Configure Amazon GuardDuty to monitor for malicious attempts to access the APIs.
Use AWS WAF to protect the API Gateway API. Configure Amazon Inspector to analyze both APIs. Configure Amazon GuardDuty to block malicious attempts to access the APIs.
Use AWS WAF to protect the API Gateway API. Configure Amazon Inspector to analyze the legacy API. Configure Amazon GuardDuty to monitor for malicious attempts to access the APIs.
Use AWS WAF to protect the API Gateway API. Configure Amazon Inspector to protect the legacy API. Configure Amazon GuardDuty to block malicious attempts to access the APIs.
Explanations:
AWS WAF can protect the API Gateway, but Amazon Inspector does not provide real-time protection or analysis for APIs; it only assesses vulnerabilities for applications. GuardDuty is a threat detection service that monitors for malicious activity, but does not directly prevent access to APIs.
While AWS WAF can effectively protect the API Gateway API, Amazon Inspector is not suitable for real-time analysis of both APIs as it primarily focuses on vulnerability assessments. GuardDuty monitors for threats but does not block access directly.
AWS WAF provides protection for the API Gateway API against common exploits and DoS attacks. Amazon Inspector can be used to analyze the legacy API for vulnerabilities. GuardDuty can monitor for malicious attempts to access both APIs, allowing for timely response and enhanced security without blocking access.
AWS WAF protects the API Gateway, but using Amazon Inspector to “protect” the legacy API is incorrect, as it is meant for vulnerability assessment, not active protection. GuardDuty does not block access but rather monitors for malicious activities, so this option incorrectly states its functionality.