使用 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.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋，同時有助於提問者的專業成長。

回答問題指南

相關內容