Custom domain configuration & LoRa gateway LNS

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개 답변

최신
최다 투표
가장 많은 댓글

이 답변이 도움이 되었나요?커뮤니티가 여러분의 지식을 활용할 수 있도록 정답을 찬성하세요.

수락된 답변

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.

Custom domain configuration & LoRa gateway LNS

관련 콘텐츠