Hello everyone,
I have a Lambda function that serves as a resource in AWS. I've set up different aliases to represent different environments (e.g., development, production, testing, etc.). My goal is to generate a unique URL for each alias so that I can access the Lambda function in each environment.
When the "resource base policy" is generated to make it public (in an alias), the ARN of the lambda in the policy does not specify the alias. As a result, when I try to access the Lambda function using the generated URL, I receive a "Forbidden" error, I've noticed a critical detail in the policy, regardless of whether you add it to an alias, always seems to be created in the "$LATEST" version of the Lambda function
Has anyone encountered a similar problem or can provide guidance on how to resolve this issue?
Regards,
AWS OFFICIALUpdated 2 years ago
