Good afternoon, everyone! I’m having some difficulties with namespaces in Amazon QuickSight and would like some help.
First, I’m not able to view the namespace I created. Does anyone know the correct procedure to be able to see the login screen of the namespace I created?
Second, when I create a user and register them in a namespace via CLI, the code provides a link. In the case of the “default” namespace, I can register the user’s password normally through this link. However, when I create a new namespace and register the user in it, the generated link results in an error. Has anyone experienced this or have any idea what might be happening?
The answers so far have been very helpful, but unfortunately I still haven’t been able to solve the problem. I still don’t have access to the namespaces I create. Does anyone know the complete list of permissions required to view them?
Hi @ArthurMendes,
Unfortunately, I haven’t encountered an issue similar to this so I can’t speak from experience. I did come across this list of available namespace operations as well as this old post that has additional information on namespaces:
To access the login screen for your namespace, the link should include the namespace name within the url, something like: e.g., https://<aws-region>.quicksight.aws.amazon.com/sn/<namespace-name>.
If you’re continuing to encounter issues and these suggestions don’t help the best route may be to open a support ticket.
I’m still investigating a solution to this issue. I suspect it may be related to some missing permission in IAM. However, I haven’t been able to find any posts that list the required or recommended permissions to successfully create and manage namespaces.
If anyone has any tips or references, that would be a great help!
Hi @ArthurMendes,
Checking back in here to see if there are any updates. Were you able to find a work around for your case or get additional assistance from a support ticket?
If we do not hear back within the next 3 business days, I’ll go ahead and close out this topic.
Hi @ArthurMendes,
Since we haven’t heard back, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new post in the community and link this discussion for relevant information if needed.