Which solution will meet these requirements with the LEAST operational overhead?
Use AWS Data Exchange for APIs to share data with customers. Configure subscription verification. In the AWS account of the company that produces the data, create an Amazon API Gateway Data API service integration with Amazon Redshift. Require the data customers to subscribe to the data product.
In the AWS account of the company that produces the data, create an AWS Data Exchange datashare by connecting AWS Data Exchange to the Redshift cluster. Configure subscription verification. Require the data customers to subscribe to the data product.
Download the data from the Amazon Redshift tables to an Amazon S3 bucket periodically. Use AWS Data Exchange for S3 to share data with customers. Configure subscription verification. Require the data customers to subscribe to the data product.
Publish the Amazon Redshift data to an Open Data on AWS Data Exchange. Require the customers to subscribe to the data product in AWS Data Exchange. In the AWS account of the company that produces the data, attach IAM resource-based policies to the Amazon Redshift tables to allow access only to verified AWS accounts.
Explanations:
This option suggests using AWS Data Exchange for APIs with Amazon API Gateway to integrate with Amazon Redshift. While it allows for real-time data access, it introduces higher operational overhead for managing APIs and requires custom development for integration, which may complicate the solution.
This option uses AWS Data Exchange to create a datashare directly from the Amazon Redshift cluster, simplifying the process of sharing data with customers. It requires subscription verification and ensures that customers have access to the most recent data with minimal operational overhead. This is the most efficient approach given the requirements.
This option involves downloading data to an Amazon S3 bucket and using AWS Data Exchange for S3 to share it with customers. Although it meets the requirement of sharing data, it introduces additional steps for data management and storage, leading to more operational overhead. It does not provide real-time access to the latest data.
This option proposes publishing data to Open Data on AWS Data Exchange and managing access through IAM policies. While it verifies customer identities, it does not guarantee that customers will have access to the most recent data, as Open Data typically does not allow dynamic updates, resulting in outdated data being shared.
I have a feeling that the answer is:
In the AWS account of the company that produces the data, create an AWS Data Exchange datashare by connecting AWS Data Exchange to the Redshift cluster. Configure subscription verification. Require the data customers to subscribe to the data product.