WA Sustainability Pillar - Create new lab: Using Redshift Data Sharing for Sustainable Data Pattern

[rpujani]

Create a new SUS lab

This lab will help implement best practices for data patterns defined in WA Sustainability Pillar - specifically, removing unneeded or redundant data, and minimizing data movement across network.

The use case is AnyCompany (an event management organization) running central data warehouse (around 2PBs data size) environment on AWS Redshift in us-east-1 region, which is used by various departments in organization for their respective storage, analytical processing & reporting. Marketing department is the top consumer of the data warehouse, and have data engineers, analysts, and scientists spread across US offices. At present, they have implemented Redshift replication to keep both us-east-1 and us-west-1 region data warehouse in sync. Since Marketing team analytical processing consumes lots of resources, they perform their analytical processing in us-west-1 region, and other departments use us-east-1 region hosted data warehouse. This requires storing redundant dataset in us-west-2 region, and transferring huge amount of data over network between AWS regions. This is not a Sustainability friendly implementation, and can be optimized using AWS WA Sustainability Pillar best practices for Data patterns.

By introducing Redshift Data Sharing feature, Marketing department can optimize their implementation to make Sustainability impact, and avoid redundant storage & reduce data transfer over network between AWS regions. Data sharing enables instant, granular, and fast data access across Amazon Redshift clusters without the need to copy or move it. With data sharing, you have live access to data, so that your users can see the most up-to-date and consistent information as it's updated in Amazon Redshift clusters, and provides cost benefit.

[setheliot]

I am closing this as I do not see anything actionable here. Please feel free to re-open if there is something we can do.

[setheliot]

oh, ok... I now see the issue is to create a new lab... that was not initially clear. re-opening