title: AWS API Gateway - error 403 on resource not found
body: <p>It seems an <code>HTTP</code> response of <code>403</code> is accepted as the norm and correct handling of any calls made to a resource or endpoint that does not exist on an API Gateway setup (<a href="https://forums.aws.amazon.com/thread.jspa?threadID=192977" rel="nofollow noreferrer">this post</a>). </p>
  
  <p>Example: a call to a non-existing endpoint on my Gateway would be;</p>
  
  <ul>
  <li>GET -- https://{{MyGatewayDomain}}/api/v1/blah </li>
  </ul>
  
  <p>This would return a <code>403 forbidden</code>. Which can be rather confusing and misleading.</p>
  
  <p>I'd like to know if anyone has managed to configure their API Gateway so that any call to a non-existing endpoint / resource, returns what I would have thought is a correct response of a 404? </p>
  
  <p>Thanks in advance.</p>
  
  <p><strong>EDIT</strong></p>
  
  <p>As per <code>bejos-aws</code>'s suggestion, I am able to override the default behaviour of the <code>403 Missing Authentication Token</code> however, this will not solve my issue as then all the valid <code>403</code> errors would return a <code>404</code> response which is incorrect. </p>
  
  <p>Also, my issue is regarding a <code>403 forbidden</code> which doesn't exist in the default responses in the AWS <code>Gateway Response</code>'s list (and even if it did, that wouldn't help). </p>
  
  <p>Seems this is just not possible?</p>