-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
💬 Decide how we should operate AWS QuickSight #833
Comments
This issue is being marked as stale because it has been open for 60 days with no activity. Remove stale label or comment to keep the issue open. |
This issue is being closed because it has been open for a further 7 days with no activity. If this is still a valid issue, please reopen it, Thank you! |
I am reopening this issue as we need to investigate and have an alternative BI offering and this one is part of AWS which makes securing access much easier. This also relates #1687 |
This issue is being marked as stale because it has been open for 60 days with no activity. Remove stale label or comment to keep the issue open. |
This needs to either cover the new QS or closed. |
Background and context
AWS QuickSight is currently offered on a best endeavour basis.
It looks to have been provided at some point, but is not an official Analytical Platform component.
Recently we've had a few support requests regarding IdAM, and I'm wondering if it's worth revisiting if/how we provide this service.
User types impacted
Data (consumers) and Platform (administration) Engineering teams
Requested Feature
Formalisation of the administration and support of AWS QuickSight
Your usecase
Provide clarity to the consumers and administrators on the status of the service
Reference:
Analytical Platform technical documentation: https://silver-dollop-30c6a355.pages.github.io/documentation/80-archived-operations-handbook/40-common-user-support/Quicksight.html#how-to-access-quicksight-as-an-author
Recent support issue: https://github.com/ministryofjustice/data-platform-support/issues/126
The text was updated successfully, but these errors were encountered: