使用AWS re:Post即您表示您同意 AWS re:Post 使用条款
AWS re:Postre:Post

Custom domain configuration & LoRa gateway LNS

0

I have some running gateways that I'd rather not experiment with until I've asked this question. Current the gateways are connected to the standard pre-provisioned CUPS and LNS address (e.g. https://ABCD12345678.cups.lorawan.us-east-1.amazonaws.com:443

I've configured a custom domain:

core.mydomain.com core.mydomain.com Enabled DATA August 29, 2021, 13:38:46 (UTC-0400)

Will pointing to the custom domain work for LoRa gateways? I've used the custom domain for connect MQTT clients to IoT Core, but I'm unsure if this would also work for the CUPS and LNS addresses.

And if so, what is the correct URI structure for a custom domain? wss://core.mydomain.com:443 and https://core.mydomain.com:443?

主题
物联网 (IoT)
标签
AWS IoT Core物联网 (IoT)
语言
English
AWS-User-9404308
已提问 2 年前260 查看次数
1 回答
0
已接受的回答

Hi and good to see your progress ;) Custom domains are supported for AWS IoT Core MQTT/HTTPS protocols: https://docs.aws.amazon.com/iot/latest/developerguide/iot-custom-endpoints-configurable-custom.html.

There is currently not support for the Custom Domains for AWS IoT Core for LoRaWAN. Could you talk more about the motivaton why you would want to use a custom domain here? Thanks!

Andrei S
已回答 2 年前
  • AWS-User-9404308
    2 年前

    Thanks Andrei. Two reasons, 1) Custom domains are nice for branding (even if only used internally), and 2) I think the same use case as MQTT/HTTPS, custom domains for LoRa gateways makes migration easier. ie. you have a bunch of gateways pre-deployed and pointing to Chirpstack or TTS The things stack with the same custom domain. Migration would be changing a DNS setting and some certs, not changing each gateway's LNS url one by one.

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈，并能促进提问者的职业发展。

回答问题的准则

相关内容