<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Siva Nagi Reddy on Medium]]></title>
        <description><![CDATA[Stories by Siva Nagi Reddy on Medium]]></description>
        <link>https://medium.com/@sivanagi317?source=rss-234d38e91f55------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_I8CfhuYvLcgZ0Ll</url>
            <title>Stories by Siva Nagi Reddy on Medium</title>
            <link>https://medium.com/@sivanagi317?source=rss-234d38e91f55------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:40:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sivanagi317/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Title: Unleashing the Power of AWS QuickSight: Overcoming Data Source Deletion Challenges for…]]></title>
            <link>https://medium.com/@sivanagi317/title-unleashing-the-power-of-aws-quicksight-overcoming-data-source-deletion-challenges-for-e5f5d67eef18?source=rss-234d38e91f55------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5f5d67eef18</guid>
            <category><![CDATA[aws-quicksight]]></category>
            <dc:creator><![CDATA[Siva Nagi Reddy]]></dc:creator>
            <pubDate>Tue, 19 Mar 2024 17:43:20 GMT</pubDate>
            <atom:updated>2024-07-10T12:48:36.708Z</atom:updated>
            <content:encoded><![CDATA[<h3>Unleashing the Power of AWS QuickSight: Overcoming Data Source Deletion Challenges for Seamless Dashboard Operation</h3><h3>Introduction:</h3><p>In this blog post, we will delve into a prevalent issue encountered by AWS QuickSight users — The unexpected deletion of data sources has affected the visual information on the dashboard. AWS QuickSight offers a robust and intuitive platform for data visualisation, yet deleting data sources can pose challenges. We will analyze the causes of this problem and offer effective solutions to address it.</p><p><strong>What is Amazon Quicksight?<br></strong>Amazon Quicksight is fast cloud-powered BI service that makes it easy to build visualisation, perform ad-hoc analysis and quickly get business insights from your data.</p><p>It allows you to easily create and publish interactive dashboards that include machine learning insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*SNNfx1XEVZQ2Z-pQ4pg3xw.png" /><figcaption><strong>AWS Quicksight</strong></figcaption></figure><p><strong><em>Exploring Data Sources, Datasets, Analysis and Dashboard in AWS QuickSight</em></strong></p><p><strong>Datasource</strong> is the source of the data that you want to analyze, such as databases, files, or AWS services. You connect QuickSight to these data sources to pull in the data for visualization.</p><p>A <strong>Dataset</strong> is a subset of the data pulled from the datasource, which has been prepared and transformed for analysis. It involves selecting specific tables, columns, or performing data cleaning and transformation tasks.</p><p>The <strong>Analysis</strong> is the process where you create visual representations (charts, graphs, etc.) of your data. This is where you build your data visualizations and explore your data in detail.</p><p>A <strong>Dashboard</strong> is a collection of analyses and visualizations that provide an at-a-glance overview of the metrics and key performance indicators (KPIs) important to your business. It is a comprehensive, interactive interface where users can monitor and analyze their data in a consolidated view.</p><h3>Reasons for Deletion of Data Sources in AWS QuickSight:</h3><blockquote>User Error:</blockquote><p>One of the main causes of data source deletion in AWS QuickSight is user error. Users may accidentally remove critical data sources without realising the impact of their actions. This can lead to the breakdown of all dashboards that depend on the data source<strong>.</strong></p><blockquote>Multiple Datasources with the Same Name:</blockquote><p>Another reason why data sources may be accidentally deleted is the ability to create multiple datasources with the same name in AWS QuickSight. This can cause confusion and increase the likelihood of deleting the wrong datasource if not managed carefully.</p><h4>Preventive Measures:</h4><ul><li><em>Understand underlying reasons for unintentional data source deletion to establish preventative measures.</em></li><li><em>Limit delete permissions for Quicksight users.</em></li><li><em>Implement clear and unique naming conventions for data sources to prevent confusion and accidental deletions.</em></li><li><em>Ensure users undergo thorough training on data management.</em></li><li><em>Educate users on the possible repercussions of deleting data sources.</em></li></ul><h4>Challenges Encountered:</h4><p>The deletion of data sources in AWS QuickSight can lead to loss of crucial information, and disruptions in data visualisation processes. Users may experience difficulties in reconstructing deleted data sources, affecting the overall efficiency and accuracy of their analytics. It is essential to address these challenges promptly to maintain the integrity of data visualization projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A-LLzBzvNcBLnINIXtoceQ.jpeg" /><figcaption>Sample of Broken Dataset and Dashboard</figcaption></figure><h3>Prerequisites:</h3><p>You must have the following prerequisites:</p><ul><li>An AWS account</li><li>A Enterprise QuickSight account</li><li>AWS Identity and Access Management (IAM)</li><li>AWS Lambda</li></ul><h4>Solution Overview:</h4><blockquote>Detecting Deleted Data Sources</blockquote><blockquote>Identifying Associated Datasets</blockquote><blockquote>Restoring Deleted Data Sources</blockquote><blockquote>Updating Associated Datasets</blockquote><h3>IAM Policy for Recovering Deleted Datasources</h3><p>When working with Amazon QuickSight, it’s essential to have the appropriate permissions to manage and recover datasets effectively. Below is an IAM policy that grants comprehensive permissions for creating, listing, getting, updating, describing, searching, and setting dashboards, analyses, datasets, and data sources in Amazon QuickSight.</p><pre>{<br>    &quot;Version&quot;: &quot;2012-10-17&quot;,<br>    &quot;Statement&quot;: [<br>        {<br>            &quot;Effect&quot;: &quot;Allow&quot;,<br>            &quot;Action&quot;: [<br>                &quot;quicksight:CreateDataSource&quot;,<br>                &quot;quicksight:ListDataSets&quot;,<br>                &quot;quicksight:ListDataSources&quot;,<br>                &quot;quicksight:ListAnalysis&quot; ,<br>                &quot;quicksight:UpdateDashboard&quot;,<br>                &quot;quicksight:UpdateAnalysis&quot;,<br>                &quot;quicksight:UpdateDataSet&quot;,<br>                &quot;quicksight:UpdateDataSource&quot;,<br>                &quot;quicksight:DescribeDashboard&quot;,<br>                &quot;quicksight:DescribeAnalysis&quot;,<br>                &quot;quicksight:DescribeDataSet&quot;,<br>                &quot;quicksight:DescribeDataSource&quot;<br>            ],<br>            &quot;Resource&quot;: [<br>                &quot;arn:aws:quicksight:&lt;region&gt;:&lt;account-id&gt;:dashboard/*&quot;,<br>                &quot;arn:aws:quicksight:&lt;region&gt;:&lt;account-id&gt;:analysis/*&quot;,<br>                &quot;arn:aws:quicksight:&lt;region&gt;:&lt;account-id&gt;:dataset/*&quot;,<br>                &quot;arn:aws:quicksight:&lt;region&gt;:&lt;account-id&gt;:datasource/*&quot;<br>            ]<br>        }<br>    ]<br>}</pre><h4>Detecting Deleted Data Sources :</h4><p>There are two ways we can obtain those details.</p><ul><li>we can navigate to CloudWatch Logs and retrieve the respective logs. From there, we can extract the data source ID that was deleted.</li><li>If CloudWatch Logs are not enabled, you can use the following code to obtain the list of data sources and their respective IDs.</li></ul><p>Python script that retrieves a list of all data sources and their IDs:</p><pre>import boto3<br>aws_acct_region=&#39;your_region_name&#39;<br>def lambda_handler(event, context):<br>    sts = boto3.client(&#39;sts&#39;,region_name=aws_acct_region)<br>    aws_account_id = sts.get_caller_identity()[&#39;Account&#39;]<br>    client = boto3.client(&#39;quicksight&#39;,region_name=aws_acct_region)<br>    # List data sources<br>    response = client.list_data_sources(AwsAccountId=aws_account_id)<br>    data_sources = response[&#39;DataSources&#39;]<br>    # Prepare output data<br>    data_source_details = [[&#39;Name&#39;, &#39;DataSourceId&#39;]]<br>    for data_source in data_sources:<br>        data_source_name = data_source[&#39;Name&#39;]<br>        data_source_id = data_source[&#39;DataSourceId&#39;]<br>        data_source_details.append([data_source_name, data_source_id])<br>    # Create CSV data<br>    csv_data = &#39;\n&#39;.join([&#39;,&#39;.join(map(str, row)) for row in data_source_details])<br>    # Optional: Upload to S3 (replace bucket and key with your details)<br>    # bucket_name = &#39;your_bucket_name&#39;<br>    # s3_key = &#39;file_name.csv&#39;<br>    # s3_client = boto3.client(&#39;s3&#39;)<br>    # s3_client.put_object(Body=csv_data, Bucket=bucket_name, Key=s3_key)<br>    return {<br>        &#39;statusCode&#39;: 200,<br>        &#39;body&#39;: &#39;Data sources list retrieved successfully&#39;<br>    }</pre><p><strong>Explanation:</strong></p><ul><li>The script retrieves the AWS account ID using the sts client.</li><li>It connects to the QuickSight service using the boto3 client.</li><li>The list_data_sources function retrieves a list of all data sources for the specified account.</li><li>The script iterates through each data source and extracts its name and ID.</li><li>It creates a list of lists containing headers (Name, DataSourceId) and data rows for each source.</li><li>The script converts the data into CSV format using list comprehension.</li></ul><h4>Identifying Associated Datasets<strong> :</strong></h4><p>Based on the data source ID we retrieved earlier, we can now identify all datasets created using that specific data source. This process involves querying the AWS QuickSight API to gather information about datasets associated with the given data source. By iterating through the list of datasets, we can determine which ones are linked to the specified data source.</p><p>Python script that retrieves a list of all associated data sets and their IDs :</p><pre>import boto3<br>aws_acct_region=&#39;your_region_name&#39;<br><br>def lambda_handler(event, context):<br>    sts = boto3.client(&#39;sts&#39;,region_name=aws_acct_region)<br>    aws_account_id = str(sts.get_caller_identity()[&#39;Account&#39;])<br>    data_source_id=&#39;your_data_source_id&#39;<br>    data_source_arn = &quot;arn:aws:quicksight:{}:{}:datasource/{}&quot;.format(aws_acct_region,aws_account_id, data_source_id)<br>    client = boto3.client(&#39;quicksight&#39;,region_name=aws_acct_region)<br><br>    # Get the list of datasets<br>    datasets = []<br>    next_token = None<br>    while True:<br>        if next_token:<br>            response = client.list_data_sets(AwsAccountId=aws_account_id, NextToken=next_token)<br>        else:<br>            response = client.list_data_sets(AwsAccountId=aws_account_id)<br>        datasets.extend(response[&#39;DataSetSummaries&#39;])<br>        next_token = response.get(&#39;NextToken&#39;)<br>        if not next_token:<br>            break<br><br>    # Extract dataset names and IDs<br>    data_source_details = []<br>    for dataset in datasets:<br>        try:<br>            dataset_response = client.describe_data_set(AwsAccountId=aws_account_id, DataSetId=dataset[&#39;DataSetId&#39;])<br>        except client.exceptions.InvalidParameterValueException as e:<br>            print(f&quot;Error describing dataset {dataset[&#39;DataSetId&#39;]}: {e}&quot;)<br>            continue<br><br>        data_source_arn_ = None<br>        for physical_table_id, physical_table_details in dataset_response[&#39;DataSet&#39;][&#39;PhysicalTableMap&#39;].items():<br>            if physical_table_details.get(&#39;CustomSql&#39;, {}).get(&#39;DataSourceArn&#39;):<br>                data_source_arn_ = physical_table_details[&#39;CustomSql&#39;][&#39;DataSourceArn&#39;]<br>                break<br><br>        if data_source_arn_ == data_source_arn:<br>            data_source_details.append([dataset[&#39;Name&#39;], dataset[&#39;DataSetId&#39;]])<br><br>    # Write dataset names and IDs to a CSV string<br>    csv_data = &#39;\n&#39;.join([&#39;,&#39;.join(map(str, row)) for row in data_source_details])<br><br>    # Upload the CSV data to S3<br>    bucket_name = &#39;your_bucket_name&#39;<br>    s3_key = &#39;file_name.csv&#39;<br>    s3_client = boto3.client(&#39;s3&#39;,region_name=aws_acct_region)<br>    s3_client.put_object(Body=csv_data, Bucket=bucket_name, Key=s3_key)<br><br>    return {<br>        &#39;statusCode&#39;: 200,<br>        &#39;body&#39;: &#39;Dataset list uploaded to S3 successfully&#39;<br>    }</pre><p><strong>Explanation:</strong></p><ul><li>The script retrieves the AWS account ID using the sts client.</li><li>It connects to the QuickSight service using the boto3 client.</li><li>The list_data_sets function retrieves a list of all data sets for the specified account.</li><li>List Datasets: The code uses the list_data_sets API of the QuickSight client to retrieve a list of datasets in the AWS account. It paginates through the results if there are more datasets than the API can return in a single call.</li><li>Check Dataset Dependencies: For each dataset, the code uses the describe_data_set API to get detailed information about the dataset, including its physical table map. It then checks if any of the physical tables in the dataset are linked to the data source you&#39;re interested in. If a dataset is found to be dependent on the data source, its name and ID are added to the data_source_details list.</li></ul><h4>Restoring Deleted Data Sources:</h4><p>In this guide, we’ll delve into the essential steps required to recreate a data source in AWS QuickSight. This comprehensive process will help you restore connectivity and functionality to your datasets and analyses, ensuring minimal disruption to your operations.</p><p>Here’s a step-by-step approach to recreating a deleted data source:</p><ul><li><strong>Gather Information:</strong> Before diving in, collect some key details about the deleted data source:</li><li><strong>Data Source ID:</strong> This unique identifier helps reference the specific data source.</li><li><strong>Data Source Type:</strong> Identify the type of data source (e.g., MySQL, PostgreSQL).</li><li><strong>Connection Details:</strong> This includes information like database name, username, and password (secure these!).</li><li><strong>Security Configuration:</strong> Note down any VPC connection details or SSL settings used by the original data source.</li></ul><p>Python script that restore the deleted data source:</p><pre>import boto3<br>aws_acct_region=&#39;your_region_name&#39;<br>def lambda_handler(event, context):<br>    sts = boto3.client(&#39;sts&#39;,region_name=aws_acct_region)<br>    client = boto3.client(&#39;quicksight&#39;,region_name=aws_acct_region)<br>    aws_account_id = sts.get_caller_identity()[&#39;Account&#39;]<br>    # Specify the desired data source ID<br>    data_source_id = &#39;deleted_datasource_id&#39;<br>    # Define the data source parameters<br>    data_source_parameters = {<br>        &#39;RdsParameters&#39;: {<br>            &#39;InstanceId&#39;: &#39;your_rds_instance_id&#39;,<br>            &#39;Database&#39;: &#39;your_database_name&#39;<br>        }<br>    }<br>    data_source_name = &#39;data_source_name&#39;<br>    data_source_type = &#39;MYSQL&#39;<br>    vpc_connection_name =&#39;your_vpc_connection_name&#39;<br>    vpc_connection_arn = &#39;arn:aws:quicksight:{}:{}:vpcConnection/{}&#39;.format(aws_acct_region,aws_account_id, vpc_connection_name)<br>    disable_ssl = False<br>    # Define the data source credentials<br>    data_source_credentials = {<br>        &#39;CredentialPair&#39;: {<br>            &#39;Username&#39;: &#39;give_your_username&#39;,<br>            &#39;Password&#39;: &#39;password&#39;<br>        }<br>    }<br>    # Create the data source<br>    response = client.create_data_source(<br>        AwsAccountId=aws_account_id,<br>        DataSourceId=data_source_id,<br>        Name=data_source_name,<br>        Type=data_source_type,<br>        DataSourceParameters=data_source_parameters,<br>        Credentials=data_source_credentials,<br>        SslProperties={<br>            &#39;DisableSsl&#39;: disable_ssl<br>        },<br>        VpcConnectionProperties={<br>            &#39;VpcConnectionArn&#39;: vpc_connection_arn<br>        }<br>    )<br>    return response</pre><p><strong>Explanation:</strong></p><p>The provided Python code snippet utilizing the boto3 library demonstrates how to programmatically recreate a data source using the AWS SDK. This approach is helpful for automating the recreation process, especially if you&#39;re dealing with multiple data sources.</p><p><strong>Key Points in the Code:</strong></p><ul><li>It retrieves your AWS account ID and ARN using the sts client.</li><li>It defines the data source parameters specific to your database type (MySQL in this example).</li><li>It specifies credentials and security configurations like VPC connection and SSL settings.</li><li>The create_data_source function creates a new data source with the provided details.</li></ul><h4>Updating Associated Datasets :</h4><p>Once the data source is recreated, you’ll need to update all datasets that relied on the original source. Point them to the recreated data source to establish connectivity and ensure your Analysis and dashboards continue to function properly.</p><h4>Backup the Dataset Configuration:</h4><p>It’s critical to back up your datasets before making any updates. AWS QuickSight provides an option to export dataset settings, such as field mappings, data types, and customizations, into a JSON file. This file serves as a backup that allows you to recreate the dataset in its previous state if needed. Having this backup ensures that you can easily revert to a previous state if any issues occur during the deletion process.</p><p>Python script that backup the Dataset Configuration:</p><pre>import json<br>import boto3<br>import csv<br>aws_acct_region=&#39;your_region_name&#39;<br>client = boto3.client(&#39;quicksight&#39;,region_name=aws_acct_region)<br>s3_client = boto3.client(&#39;s3&#39;,region_name=aws_acct_region)<br>s3_bucket_name = &#39;your_bucket_name&#39;<br>def dump_dataset(account_id):<br>    datasets = []<br>    dataset_id = []<br>    response = client.list_data_sets(AwsAccountId=account_id)<br>    next_token: str = response.get(&quot;NextToken&quot;, None)<br>    datasets += response[&quot;DataSetSummaries&quot;]<br>    while next_token is not None:<br>        response = client.list_data_sets(AwsAccountId=account_id, NextToken=next_token)<br>        next_token = response.get(&quot;NextToken&quot;, None)<br>        datasets += response[&quot;DataSetSummaries&quot;]<br>    for i in datasets:<br>        dataset_id.append(i[&quot;DataSetId&quot;])<br><br>    <br>    # Create a list of dictionary keys (column names)<br>    column_names = [&#39;id&#39;, &#39;name&#39;, &#39;physical_table&#39;, &#39;logical_table&#39;, &#39;mode&#39;]<br>    <br>    # Write the dictionary data to a CSV file<br>    with open(&#39;/tmp/dataset.csv&#39;, &#39;w&#39;, newline=&#39;&#39;) as csv_file:<br>        writer = csv.DictWriter(csv_file, fieldnames=column_names)<br>        writer.writeheader()  # Write column names as the header<br>    <br>        for i in dataset_id:<br>            try:<br>                res = client.describe_data_set(<br>                    AwsAccountId=account_id,<br>                    DataSetId=i<br>                )<br>                dataset_dict = {<br>                    &#39;id&#39;: res[&#39;DataSet&#39;][&#39;DataSetId&#39;],<br>                    &#39;name&#39;: res[&#39;DataSet&#39;][&#39;Name&#39;],<br>                    &#39;physical_table&#39;: res[&#39;DataSet&#39;][&#39;PhysicalTableMap&#39;],<br>                    &#39;logical_table&#39;: res[&#39;DataSet&#39;][&#39;LogicalTableMap&#39;],<br>                    &#39;mode&#39;: res[&#39;DataSet&#39;][&#39;ImportMode&#39;]<br>                }<br>                writer.writerow(dataset_dict)<br>            except Exception as e:<br>                print(e)<br>                continue<br>            <br>    <br>    file_name = &#39;your_file_name.csv&#39;        <br>    <br>    # Upload the CSV file to S3<br>    s3_client.upload_file(&#39;/tmp/dataset.csv&#39;, s3_bucket_name, file_name)<br>            <br>    return dataset_dict<br>    <br>    <br>def lambda_handler(event, context):<br>    sts = boto3.client(&#39;sts&#39;,region_name=aws_acct_region)<br>    aws_account_id = str(sts.get_caller_identity()[&#39;Account&#39;])<br>    response = dump_dataset(aws_account_id)<br> <br>    return {<br>        &#39;statusCode&#39;: 200,<br>        &#39;body&#39;: json.dumps(&#39;Successfully taken the backup of our datasets&#39;)<br>    }</pre><h4>Explanation:</h4><p>The above code snippet provides a way to backup of dataset configurations from AWS QuickSight to an S3 bucket, ensuring that you have a copy of your datasets in case they need to be restored in the future.</p><h4>Modify the dataset configuration :</h4><blockquote>Retrieve Dataset Information:</blockquote><p>Use the describe_data_set API to retrieve detailed information about each dataset, including its ID, name, and current configuration.</p><blockquote>Modify Dataset Configuration:</blockquote><p>Edit the retrieved dataset information to update the configuration as needed. This may include changing field mappings, data types, or any other dataset settings.</p><p>Edit response to remove unnecessary information:</p><ul><li>Remove lines 2, 3, 4, 7, 8 starting with “Status”, “Dataset”, “Arn”, “CreatedTime”, and “LastUpdatedTime”.</li><li>Remove lines containing “ConsumedSpiceCapacityInBytes” and “RequestId”.</li><li>Remove the JSON block for “OutputColumns”.</li></ul><blockquote>Update Dataset Configuration:</blockquote><p>Use the update_data_set API to apply the modified configuration to the dataset.</p><p>Python script that demonstrates how to modify the dataset configuration:</p><pre>import boto3<br>aws_acct_region=&#39;your_region_name&#39;<br>def update_dataset(dataset_id):<br>    # Define the account ID<br>    account_id = &quot;your_account_id&quot;<br>    client = boto3.client(&quot;quicksight&quot;,region_name=aws_acct_region)<br>    try:<br>        response = client.describe_data_set(<br>            AwsAccountId=account_id,<br>            DataSetId=dataset_id<br>        )<br>        # Edit the dataset description<br>        dataset_description = response[&quot;DataSet&quot;]<br>        # Remove unnecessary keys from the dataset description<br>        dataset_description.pop(&quot;Arn&quot;, None)<br>        dataset_description.pop(&quot;CreatedTime&quot;, None)<br>        dataset_description.pop(&quot;LastUpdatedTime&quot;, None)<br>        dataset_description.pop(&quot;ConsumedSpiceCapacityInBytes&quot;, None)<br>        dataset_description.pop(&quot;RequestId&quot;, None)<br>        dataset_description.pop(&quot;OutputColumns&quot;, None)<br>        dataset_description.pop(&quot;RowLevelPermissionDataSet&quot;, None)<br>        # Update the dataset with the modified description<br>        update_params = {<br>            &quot;AwsAccountId&quot;: account_id,<br>            &quot;DataSetId&quot;: dataset_id,<br>            **dataset_description  # Include all remaining keys from the dataset description<br>        }<br>        response = client.update_data_set(**update_params)<br>        print(f&quot;Dataset {dataset_id} updated successfully!&quot;)<br>    except Exception as e:<br>        print(f&quot;Error updating dataset {dataset_id}: {str(e)}&quot;)<br>def lambda_handler(event, context):<br>    # Define the list of dataset IDs<br>    dataset_ids = [&#39;your dataset ids&#39; ]<br>    for dataset_id in dataset_ids:<br>        update_dataset(dataset_id)</pre><h3>Conclusion:</h3><p>Ensuring data integrity and resilience in AWS QuickSight requires a proactive approach that combines preventive measures, systematic identification of deleted data sources, and automated processes for recreating and updating datasets. By implementing stringent permissions, clear naming conventions, and comprehensive user training, organizations can reduce the risk of accidental data source deletions.Regularly backing up dataset configurations to S3 and using scripts to update configurations post-recreation ensures data continuity, enhancing data governance and minimising disruptions in data visualisation and analytics workflows within AWS QuickSight.</p><h3>References:</h3><ul><li><a href="https://community.amazonquicksight.com/t/changing-data-source-for-a-dataset/2716">AWS Quicksight Community Post</a></li><li><a href="https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/quicksight.html">Boto3 AWS Quicksight Documentation</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5f5d67eef18" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>