AWS App Runner Custom Domains

[jvisker]

Name of the resource

Other

Resource name

AWS::AppRunner::CustomDomain

Description

There is no CloudFormation support for creating custom domains for AWS App Runner. There should be a new resource created called something like AWS::AppRunner::CustomDomain. The related links included have the fields that need to be included.

Other Details

https://docs.aws.amazon.com/apprunner/latest/api/API_AssociateCustomDomain.html https://docs.aws.amazon.com/apprunner/latest/api/API_DescribeCustomDomains.html https://docs.aws.amazon.com/apprunner/latest/api/API_DisassociateCustomDomain.html

[jvisker]

I do not see a change in the documentation. Am I missing something?

[Negan1911]

@prerna-p The issue is still in the "Shipped" column but as this shows, it wasn't shipped

[mvanholsteijn]

For inspiration -> https://github.com/OblivionCloudControl/xebia-email-signature/blob/main/src/app_runner_custom_domain_resource_provider/__init__.py

[ggallotti]

It would be nice to have this.

[tcldr]

Is there an update on this? There's lots of demand not only on this issue, but on the App Runner specific issue (that is dependent on this one), too.

[wired00]

Hi All, so what's the options at this point. Are there any IaC options when using CDK v2 to automagically update/upsert route53 alias to point at new execution point (say https://123xyz.ap-southeast-2.awsapprunner.com)? That is, on occasion when there is a requirement for a complete new new App runner deployment. Is it a one off case of clickops/aws console?

[mvanholsteijn]

@wired00 Best thing is to wrap the custom resource provider in CDK for yourself.

https://github.com/OblivionCloudControl/xebia-email-signature/blob/main/src/app_runner_custom_domain_resource_provider/__init__.py