We are using generate_embed_url_for_registered_user from boto3 to embedd a quicksight dashboard via iframe to our platform. It works well, but we noticed very often on the console the error “Websocket onclose failed with code: 1006 reason”. So far it seems like the dashboard loads anyway without issues, but we are not yet sure if we should be concerned by it or not.
I’ve seen other posts that mention that error but have other errors too and their dashboards do not load, but I believe they were using an SDK directly, not loading the embedd url onto an iframe like we are doing.
Has anyone else had this and found a solution or found it irrelevant?
thank you for your quick answer. I saw that post, but it doesn’t seem to be quite the same issue. We are not using amazon-quicksight-embedding-sdk, but simply an iFrame with the url we get with boto3 on a lambda to embedd a dashboard, not several visuals in different iframes as on the other post. We also don’t get any 429 errors, and I think this is the error mostly addressed in the answer given on that post.
The dashboard does load without problems that we can tell so far, but we still wonder if this error 1006 websocket error could cause us problems in the future.
When embedding Quick Sight dashboards in an iframe using URLs generated through boto3, it is common to see a browser console error stating Websocket onclose failed with code: 1006 reason. This error indicates that the WebSocket connection closed abnormally, but it is a low-level protocol message that does not necessarily indicate a problem with dashboard functionality.
If you need more information, I would suggest you to file a case with AWS Support where we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!