2 Answers
- Newest
- Most votes
- Most comments
0
Thanks for the response. I tried in the vpc under private and public subnet but still same issue. I tried outside vpc but the same. The original url means the url i got in the Visual Studio after deployment is working every where. Thanks
answered a year ago
0
When using NONE auth type, does the Lambda function have the resource-based policy to make the function public? Should look like this:
{
"Version": "2012-10-17",
"Statement": [
{
"StatementId": "FunctionURLAllowPublicAccess",
"Effect": "Allow",
"Principal": "*",
"Action": "lambda:InvokeFunctionUrl",
"Resource": "arn:aws:lambda:us-east-1:12345678910:function:<Function Name>",
"Condition": {
"StringEquals": {
"lambda:FunctionUrlAuthType": "NONE"
}
}
}
]
}
Here is text from the documentation on this: If you choose the NONE auth type, Lambda doesn't use IAM to authenticate requests to your function URL. However, users must still have lambda:InvokeFunctionUrl permissions in order to successfully invoke your function URL.
answered a year ago
Relevant content
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Can you share a code snippet? Is your lambda in vpc?