-
|
The PubSub example requires |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 30 replies
-
|
Answer: It should look something like this: xxxxxxxxxxxxxx-ats.iot.us-east-2.amazonaws.com |
Beta Was this translation helpful? Give feedback.
-
|
Hello! A team member has marked the above comment as the likely answer to this discussion thread.
|
Beta Was this translation helpful? Give feedback.
-
|
[I'm going to try something else.] |
Beta Was this translation helpful? Give feedback.
-
That's very helpful, thanks. However I still have an installation problem. I'm using a WSL2/Ubuntu20.04.6 terminal and Node 18.16.0. The following are notes I'm preparing to help others get this running.These steps result in an index.html that can be opened in a browser as a local file, and the loaded page will show that it can publish on a specific MQTT topic to AWS IoT core in your dev region, and receive its own messages back by subscribing to that topic.
|
Beta Was this translation helpful? Give feedback.
-
|
The installation errors above happen even if you follow https://github.com/aws/aws-iot-device-sdk-js-v2/blob/main/samples/README.md#installing-via-npm and change the |
Beta Was this translation helpful? Give feedback.
-
|
It looks like you are running into some problems with the dependencies for this sdk. Are you making sure to install this sdk before you install the sample? You can do this in a few ways but it looks like you are trying to install from the source: We want to make sure we have clear and detailed instructions for how to install this sdk. You can find the quick connect guide here, this downloads a script and does all of the setup for you (creates the certs, sets up IoT thing, creates a policy, attaches them all together for you, installs the sdk, and even runs the pubsub sample for you). We also have a section in our FAQ that explains which certificates that you need. Is there anything that you think is missing or that could be explained better/more clearly? |
Beta Was this translation helpful? Give feedback.
-
|
I tried to install the SDK, but the required version of puppeteer is no longer supported... |
Beta Was this translation helpful? Give feedback.
-
|
What OS are you trying to run this on? |
Beta Was this translation helpful? Give feedback.
-
|
Also, it's not clear where to attach the sample policy given at https://github.com/aws/aws-iot-device-sdk-js-v2/tree/main/samples/browser/pub_sub My new Identity Pool's policy does not seem editable, and at IoT Home there are no obvious controls for attaching a policy to my pool. Maybe one is supposed to edit the policy of the IAM role associated with the identity pool? |
Beta Was this translation helpful? Give feedback.
-
|
That is the policy that you should attached to the certificate assigned to your |
Beta Was this translation helpful? Give feedback.
-
|
I have been searching AWS IoT docs for an explanation of whether there is any |
Beta Was this translation helpful? Give feedback.
-
|
Maybe the policy is supposed to be attached by calling |
Beta Was this translation helpful? Give feedback.
-
|
I'm using a Windows Subsystem for Linux v2 (WSL2) terminal that uses Ubuntu
20. My NodeJs version is 18.16.0.
…On Fri, Aug 4, 2023, 12:39 AM Joseph Klix ***@***.***> wrote:
What OS are you trying to run this on?
—
Reply to this email directly, view it on GitHub
<#412 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKJXV3BIS3CKRTJRTDDR7RLXTQK75ANCNFSM6AAAAAA3BH7A5Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I tried on macOS 13.4.1 by cloning https://github.com/aws/aws-iot-device-sdk-js-v2.git and then doing That worked much better, which led me to wonder if I unwittingly cloned the old version of the JS SDK on WSL2, so I deleted that working copy, recloned, and did the steps above. That worked just as well as on macOS. However, Then I edited It would be good to echo a line at the start of installation saying one should wait until seeing something specifc, then open the local index.html in a browser. When I open index.html in recent Chrome, the page displays only Am I not getting any further because I haven't yet attached a policy? If so, how do I attach it? |
Beta Was this translation helpful? Give feedback.
-
|
I think this topic should not be marked resolved because there still is not enough documentation about how to run the sample. In particular, I'm still stuck as described above, and there are no details about how to attach a policy when using Cognito instead of a certificate. |
Beta Was this translation helpful? Give feedback.
-
|
I'm sorry that this was closed without a solution. The bot didn't have any comment's so it selected my first reply as an answer. I have reopened this discussion and will keep it open until you get this sample working. Here are the steps that I follow to get the sample working. Please let me know if you have questions about any part.
git clone https://github.com/aws/aws-iot-device-sdk-js-v2.git
cd aws-iot-device-sdk-js-v2
npm install
# edit the `settings.js` now if you haven't already
cd samples/browser/pub_sub
npm installopen index.html in browser Connecting websocket...
start publish
Message received: topic=/test/me/senpai message=NOTICE ME {0}
Message received: topic=/test/me/senpai message=NOTICE ME {1}
... |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for clarifying where the policy must be specified. Note that when I paste-in the policy, there is a security warning: Wouldn't it be better to use a more-limited policy such as the following? However, after setting this policy (and replacing the placeholders), my index.html doesn't get any further than "Connecting websocket..." |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it is better to use a more-limited policy. I was suggesting to use * to get it working and then you can change the policy to limit what resources/actions are allowed. When you use the * policy does it work? or do you still get stuck at the "Connecting websocket..."? |
Beta Was this translation helpful? Give feedback.
-
|
When I use my more-restricted policy, the page is stuck at "Connecting websocket..." and the console doesn't show any errors or any content at all (btw, this isn't a user error; I use DevTools everyday.) I haven't tried the |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the PR. It's an improvement but after I incorporate and rebuild, I have the same problem:
|
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure what exactly is causing you to get connection closed as when I use the sample policy in the readme I am able to connect: (see sample policy){
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"iot:Publish",
"iot:Receive"
],
"Resource": [
"arn:aws:iot:region:account:topic/test/topic"
]
},
{
"Effect": "Allow",
"Action": [
"iot:Subscribe"
],
"Resource": [
"arn:aws:iot:region:account:topicfilter/test/topic"
]
},
{
"Effect": "Allow",
"Action": [
"iot:Connect"
],
"Resource": [
"arn:aws:iot:region:account:client/test-*"
]
}
]
}
|
Beta Was this translation helpful? Give feedback.
-
|
Btw, the updated browser pub_sub sample shows the following when I use a new client ID that is And the tab's Console shows only: When I leave it running and then:
|
Beta Was this translation helpful? Give feedback.
-
|
While in a Chime call just now with an SA, we double-checked my policy and found it was still using the outdated policy of this sample. Once we saved the updated policy, the index.html of this sample was able to subscribe, self-publish, and receive publishes from the MQTT test page (while it was configured to use MQTT v3...we didn't try v5). |
Beta Was this translation helpful? Give feedback.
-
|
Please reopen.
…On Fri, Aug 25, 2023, 7:05 AM github-actions[bot] ***@***.***> wrote:
Closed #412
<#412> as
resolved.
—
Reply to this email directly, view it on GitHub
<#412>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKJXV3CF2W2JWODYNJRTG4DXXAQBRANCNFSM6AAAAAA3BH7A5Q>
.
You are receiving this because you authored the thread.Message ID:
<aws/aws-iot-device-sdk-js-v2/repo-discussions/412/discussion_event/826037
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I reopened this issue. Can you provide details on what you still need help with? |
Beta Was this translation helpful? Give feedback.
-
|
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
While in a Chime call just now with an SA, we double-checked my policy and found it was still using the outdated policy of this sample. Once we saved the updated policy, the index.html of this sample was able to subscribe, self-publish, and receive publishes from the MQTT test page (while it was configured to use MQTT v3...we didn't try v5).