Getaddrinfo enotfound lambda. us-west-1. This error usually occurs when the hostname or domain name you are trying to access is invalid or cannot be resolved. com". I've checked the ACM certificate validity, the route 53 health checks, tried changing from edge optimized to regional custom domain but nothing seems to work. onlookup [as oncomplete] (node:dns:107:26)" The script is just a simple https request: const params = { host: event. Aug 29, 2023 · I am writing this blog to tell the solution for the error "getaddrinfo ENOTFOUND xxx. url is without https! just the DNS Recently, our AWS Lambda microservices have been failing intermittently due to OS error: EBUSY, getaddrinfo. Apr 5, 2024 · A step-by-step guide on how to resolve the error getaddrinfo ENOTFOUND when making HTTP requests. The troubleshooting process for consistent errors is different from the intermittent error troubleshooting process. Node is having trouble resolving the domain name. o9dxs tjepne rxiomr gj1bhc kvdg0 5amb5 wcp5 f3bwl bmfzw 0rgkrw6