Lab complete!
Now that you have completed this lab, make sure to update your Well-Architected review if you have implemented these changes in your workload.
Click here to access the Well-Architected Tool
With optimization completed in the previous lab, let’s follow below steps on the consumer cluster to measure the improvement on our sustainability KPI:
us-west-1
region, and click/expand on “consumer_marketing”. You can see in the tool tip that it is a datashare which is connected to a producer cluster. All the tables listed below are from producer cluster.SELECT SUM(size) FROM SVV_TABLE_INFO WHERE "table" NOT LIKE '%auto%';
The above query did not return any table size, which means that the consumer database does not have any tables locally, hence not consuming any data storage to store the tables.
With, that below are revised (improved) metrics and KPI:
For per event data storage sustainability KPI, we see there is 50% reduction (improvement) by using the Amazon Redshift Data Sharing feature.
For per event data transfer KPI, trade-off analysis should be performed comparing daily refresh data transfer vs. all queries execution dataset transfer over network. One option is to analyze data transfer between regions is using AWS Cost Explorer. Refer to this AWS blog post explaining how to use AWS Cost Explorer to analyze data transfer volume and cost.
With the above comparison of the baseline & revised metrics and KPI, we tested how the Amazon Redshift Data Sharing feature helped to improve our sustainability KPI for AnyCompany’s Marketing data warehouse environment.
Next, we will cleanup the AWS resources created to make sure no further costs are incurred.
Now that you have completed this lab, make sure to update your Well-Architected review if you have implemented these changes in your workload.
Click here to access the Well-Architected Tool