A company is developing an application in the AWS Cloud. The application's HTTP API contains critical information that is published in Amazon API Gateway. The critical information must be accessible f

Question

Options

• ASet up an API Gateway private integration to restrict access to a predefined set ot IP addresses.
• BCreate a resource policy for the API that denies access to any IP address that is not specifically
• CDirectly deploy the API in a private subnet. Create a network ACL. Set up rules to allow the traffic
• DModify the security group that is attached to API Gateway to allow inbound traffic from only the

• A
  7% (2)
• B
  74% (20)
• C
  4% (1)
• D
  15% (4)

Explanation

Amazon API Gateway supportsresource policies, which allow you to control access to your API by specifying the IP addresses or ranges that can access the API. By creating a resource policythat explicitly denies access to any IP address outside the allowed set, you can ensure that only trusted IP addresses (such as those from your internal network) can access the critical information in your API. This approach provides fine-grained access control without the need for additional infrastructure or complex configurations. Option A (Private integration): API Gateway private integrations are for creating private APIs that are only accessible within a VPC, but this solution is about restricting access to certain IP Option C (Private subnet and ACLs): Deploying the API in a private subnet and using network ACLs adds unnecessary complexity and isn't the best fit for HTTP APIs. Option D (Security group): API Gateway doesn't have a security group because it isn't a resource inside a VPC. Instead, resource policies are the correct mechanism for controlling IP-based

No community discussion yet for this question.