QuestionQ22

VerifiedSecurity and Compliance

A company organizes its AWS accounts into OUs within an AWS Organizations organization. It has deployed a collection of Amazon API Gateway APIs in one Organizations account. The APIs are associated with that account’s VPC and currently have no authentication mechanism. Only principals in one specific OU must be permitted to invoke the APIs.

The company applies the following policy to the API Gateway interface VPC endpoint:

Question Image

The company also modifies the API Gateway resource policies to deny invocations that do not pass through the interface VPC endpoint. After these updates, attempts to invoke an API by using the interface VPC endpoint URL produce this error: "User: anonymous is not authorized."

Which combination of steps will resolve this issue?

Choose two
Explanation

A VPC endpoint policy evaluates the invoker from the request’s Authorization header. A request with no authorization header, or with a non-SigV4 bearer token, is treated as anonymous; a valid SigV4 signature identifies the authenticated IAM principal. Configuring API methods with AWS_IAM authorization and signing client requests with SigV4 AWS credentials provides that IAM identity, allowing the aws:PrincipalOrgPaths condition to restrict invocation to principals in the required OU.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!