1 Answer
2
Accepted Answer
Lambda function URLs are intended to be very lightweight way if invoking Lambda functions. They have limited capabilities, custom domain names is not one of them. Creating an alias in Route53 will not help as the Lambda service will not know which function it needs to invoke.
If you need custom domain names, use API Gateway instead.
Relevant questions
Can we send email notifications from SNS using our own domain?
Accepted Answerasked 6 months agoRoute53 custom domain not updating content
asked 7 months agocan we attach the custom domain to lambda function urls ?
Accepted Answerasked 5 months agoCan we add .earth as a valid top level domain in Route 53?
asked 11 days agoHTTP API Custom Domain not working
Accepted Answerasked 6 months agoAmplify Console - custom domain shows different content than default url
asked 3 months agoApiGatewayV2 - HttpApi - Cannot use a custom domain
asked 2 years agoAttaching custom image to user (not domain) in SageMaker Studio
Accepted Answerasked 2 years agoHow to configure a custom domain name for api gateway in a multi region scenario?
asked 2 days agoAWS IoT custom domain ECDSA support
Accepted Answerasked 9 months ago
You can also consider putting your custom domain name on CloudFront or a public ALB.