AWS Amplify Hosting now supports wildcard subdomains

AWS Amplify Hosting is excited to announce the general availability of wildcard subdomains when using a custom domain with your Amplify application. This new capability is available for any application deployed to AWS Amplify Hosting using a custom domain including static applications, single page applications (SPA), and fullstack Server-side rendering applications using Next.js. Before wildcard subdomains, each subdomain needed for an application was required to be configured individually or by defining patterns. Now, customers can configure applications with custom domains that accept any valid subdomain value without configuration by specifying the wildcard asterisk (\*) as the subdomain value. This acts as a catch-all for multiple subdomains and supports use cases when the subdomain value may not be known ahead of time or when subdomain values represent an identifier, common in multi-tenant applications. AWS Amplify Hosting and its improved support for wildcard subdomains is generally available in the following 19 AWS Regions: US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), Europe (Frankfurt), Europe (Stockholm), Europe (Milan), Europe (Ireland), Europe (London), Europe (Paris), Middle East (Bahrain) and South America (São Paulo). To learn more, see [wildcard subdomains](https://docs.aws.amazon.com/amplify/latest/userguide/wildcard-subdomain-support.html) in the AWS Amplify Hosting documentation. To get started using wildcard subdomains, follow along in the [Wildcard Subdomains for Multi-tenant Apps on AWS Amplify Hosting](https://aws.amazon.com/blogs/mobile/wildcard-subdomains-for-multi-tenant-apps-on-aws-amplify-hosting) blog post.