Health Checks to AWS API Gateway fail when API keys enabled (x-api-key)

0

Route 53 Health Checks are impossible to fully enable to AWS API Gateway when the api on the gateway has API keys enabled. Why? Because the request to the gateway must send the "x-api-key" header with a known value.

To my knowledge, at best you can configure an HTTP (not HTTPS) health check to the path desired. This request will be responded with a 301 redirect. The 301 is accepted as "healthy" by the default rules of a Route 53 Health Check.

If you were to configure an HTTPS health check, there would be no 301 redirect. Instead you would immediately receive a 403 Forbidden. This would fail the health check.

질문됨 8년 전1.5천회 조회
1개 답변
0

Hi DalePh,

Thanks for your feedback. Yes, unfortunately there is no way to pass in headers at this time. For now the workaround of using HTTP or TCP health check type is the only option.

thanks

답변함 8년 전
profile picture
전문가
검토됨 7달 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인