# Wildcard subdomains

**URL:** <https://forum.serverless.com/t/wildcard-subdomains/12327>\
**Category:** Serverless Framework\
**Tags:** lambda, api-gateway\
**Created:** [August 19, 2020, 9:41am UTC](https://forum.serverless.com/t/wildcard-subdomains/12327 "2020-08-19T09:41:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gear2000](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/gear2000/32/4496_2.png) [@gear2000](https://forum.serverless.com/u/gear2000)\
**Post date:** [August 19, 2020, 9:41am UTC](https://forum.serverless.com/t/wildcard-subdomains/12327/1 "2020-08-19T09:41:53Z")

</div>

Hi, is it possible to implement wildcard custom domains for api gateway? In other words, \*.users.example.com. Amazon made an announcement about a year ago about this feature. I’m trying to create custom endpoints for each user.

[https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html#wildcard-custom-domain-names](https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html#wildcard-custom-domain-names)

I’m using the serverless-domain-manager, but this requires a redefinition of each subdomain though it is serviced by the the same lambda function.

Gary

---

<div class="post-metadata">

**Author:** ![bbarrington42](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/bbarrington42/32/7431_2.png) [@bbarrington42](https://forum.serverless.com/u/bbarrington42)\
**Post date:** [April 18, 2023, 10:29am UTC](https://forum.serverless.com/t/wildcard-subdomains/12327/2 "2023-04-18T10:29:32Z")

</div>

Wow. This is pretty old. Any plans to support this?

---

<div class="post-metadata">

**Author:** ![bbarrington42](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/bbarrington42/32/7431_2.png) [@bbarrington42](https://forum.serverless.com/u/bbarrington42)\
**Post date:** [April 18, 2023, 9:08pm UTC](https://forum.serverless.com/t/wildcard-subdomains/12327/3 "2023-04-18T21:08:06Z")

</div>

Well, actually, I see it IS supported. It just dumps the result of the stack deployment several times and spits out this error during all but the first: Error: Impossible to parse the output of “serverless info”:

I tried upgrading to the latest version of the plugin (7.0.2), but no change in the behavior.