- Newest
- Most votes
- Most comments
Hello.
I tried accessing it from my terminal, and name resolution was done without any problems.
Also, although I am getting a 403 error, the function URL also appears to be working.
I think it's probably a temporary issue or a problem with your PC.
curl https://ay424xgkkzwoyyzxt2kzpsah240mfgsy.lambda-url.us-west-1.on.aws/ -i
HTTP/1.1 403 Forbidden
Date: Sat, 02 Nov 2024 13:40:22 GMT
Content-Type: application/json
Content-Length: 16
Connection: keep-alive
x-amzn-RequestId: cd27bab5-a7c1-4eb3-8366-3d40f3b82d36
x-amzn-ErrorType: AccessDeniedException
{"Message":null}
dig ay424xgkkzwoyyzxt2kzpsah240mfgsy.lambda-url.us-west-1.on.aws
; <<>> DiG 9.16.1-Ubuntu <<>> ay424xgkkzwoyyzxt2kzpsah240mfgsy.lambda-url.us-west-1.on.aws
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52887
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;ay424xgkkzwoyyzxt2kzpsah240mfgsy.lambda-url.us-west-1.on.aws. IN A
;; ANSWER SECTION:
ay424xgkkzwoyyzxt2kzpsah240mfgsy.lambda-url.us-west-1.on.aws. 60 IN A 54.241.184.132
ay424xgkkzwoyyzxt2kzpsah240mfgsy.lambda-url.us-west-1.on.aws. 60 IN A 54.183.246.3
;; Query time: 50 msec
;; SERVER: 192.168.11.1#53(192.168.11.1)
;; WHEN: 土 11月 02 22:39:33 JST 2024
;; MSG SIZE rcvd: 121
Based on the information provided, it appears that you are experiencing an issue with your Lambda function URL in the us-west-1 region. The error "DNS_PROBE_FINISHED_NXDOMAIN" typically indicates that the domain name cannot be resolved, which suggests there might be a problem with the DNS resolution for your function URL.
Given that the same function URL is working properly in other regions and that the function itself is working when tested from the AWS console, this issue is likely not related to your specific implementation or configuration. The fact that this problem started about 6 hours ago and is affecting only the us-west-1 region points towards a potential intermittent or regional issue with AWS Lambda function URLs.
However, it's important to note that Lambda function URLs are generally available and supported in the us-west-1 region. There are no known widespread outages or issues reported for Lambda function URLs in this region at the time of this response.
To troubleshoot this issue, you could try the following steps:
- Verify that the function URL is correctly configured and hasn't been accidentally modified or deleted.
- Try creating a new function URL for the same Lambda function to see if the issue persists.
- Check if there are any AWS service health notifications for Lambda or related services in the us-west-1 region.
- Contact AWS support if the issue continues, as they would have more detailed information about any potential regional problems or ongoing incidents.
If the problem persists and you need immediate resolution, you might consider temporarily redirecting traffic to your function URLs in other regions where they are working correctly.
Remember that while intermittent issues can occur with cloud services, persistent region-specific problems with core functionality like function URLs are uncommon. If the issue continues for an extended period, it's advisable to engage with AWS support for a more in-depth investigation.
Sources
Understanding Lambda function invocation methods - AWS Lambda
Invoking Lambda function URLs - AWS Lambda
Creating and managing Lambda function URLs - AWS Lambda
answered 2 years ago
Hi team, i am also facing the same issue all of a sudden. My function is live for 1.5 years. It was working till yesterday but now I can't able to connect my URL.
Can you please help to resolve the issue?
Thanks
answered 2 years ago
Relevant content
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 months ago
