-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(aws-lambda): FunctionUrl incorrectly uses Alias ARNs #21353
Conversation
When configuring a FunctionUrl for a Lambda function Alias, the underlying lambda function's ARN must be configured as TargetFunctionArn, and the alias name as Qualifier. This was previously not the case, as the Alias' ARN was used with no qualifier, which accidentally succeeded provisionning but did not necessarily produce the intended result.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
I just now tried out the new
My CDK project is here: https://github.com/LiveData-Inc/hyphen-bug Here's a copy of the CDK output |
A hyphen in the Alias Name seems to cause the problem. If I change the hyphen to an underscore, the stack deploys. |
@jrobbins-LiveData the contents of your template is correct, and I believe this is a bug in the CloudFormation resource handler for |
@RomainMuller is there any way for us to know when the CloudFormation issue will be fixed? |
When configuring a FunctionUrl for a Lambda function Alias, the underlying lambda function's ARN must be configured as TargetFunctionArn, and the alias name as Qualifier. This was previously not the case, as the Alias' ARN was used with no qualifier, which accidentally succeeded provisionning but did not necessarily produce the intended result. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
When configuring a FunctionUrl for a Lambda function Alias,
the underlying lambda function's ARN must be configured
as TargetFunctionArn, and the alias name as Qualifier. This
was previously not the case, as the Alias' ARN was used
with no qualifier, which accidentally succeeded provisionning
but did not necessarily produce the intended result.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license