feat: migration guides #3248
Open
feat: migration guides #3248
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
id
force-pushed
the
20251117-aws-iot-migration-guide
branch
from
2da27e5 to
83e3912
Compare
id
force-pushed
the
20251117-aws-iot-migration-guide
branch
from
acba3ad to
560f759
Compare
Meggielqk
reviewed
Nov 24, 2025
|
|
||
| Regardless of the method, the certificate hierarchy is the same: your devices are always signed by your own CA. For migration to EMQX, you must obtain this CA certificate so EMQX can verify your devices. | ||
|
|
||
| ### Identify the CA That Issued Your Device Certificates |
Collaborator
There was a problem hiding this comment.
@id, I added this section to show exactly users can locate the CA. Please help to review.
Collaborator
Author
There was a problem hiding this comment.
@Meggielqk I cannot formally approve the PR because I created it. If you think it looks good, let's merge it.
thalesmg
previously approved these changes
Nov 24, 2025
| | **Device Certificate** | `device-001.cert.pem` | `device-001.cert.pem` | No change. The device continues using its existing certificate signed by your CA. | | ||
| | **Device Private Key** | `device-001.key.pem` | `device-001.key.pem` | No change. The device continues using its existing private key. | | ||
| | **Server Verification** (Device trusts Server) | Device client uses `AmazonRootCA1.pem` | Device client must be updated to use `emqx-server-ca.pem` | The client must trust the CA that issued the EMQX server's certificate. | | ||
| | **Client Verification** (Server trusts Device) | AWS IoT Core trusts your registered CA | EMQX listener's `cacertfile` must be set to `your-ca.pem` | EMQX must be configured to trust the same CA you registered with AWS IoT Core.| |
Contributor
There was a problem hiding this comment.
I think it's worth mentioning that verify = verify_peer must be set in addition to configuring the CA cert file.
|
|
||
| | **Parameter** | **AWS IoT Core (Example)** | **EMQX (Example)** | **Notes** | | ||
| | ------------- | -------------------------- | ------------------ | --------- | | ||
| | **Endpoint Hostname** | `agwba84cbf2pn-ats.iot.eu-west-1.amazonaws.com` | `mqtt.example.com` | Update device client code/firmware | |
Contributor
There was a problem hiding this comment.
Probably they'll need to specify the port as well. IIRC, AWS IoT SDK defaults to 443 when using WSS, at least.
It does seem to default to 8883 when not using websockets, indeed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.