1 Answer
- Newest
- Most votes
- Most comments
1
Hello Od,
Thank you very much for your question. Regarding your questions, please find the answer below:
- Are these queries for AWS's internal monitoring purposes? Yes, the queries are most likely executed by AWS for monitoring and management purposes. The
pg_last_query_id()
function retrieves the last query ID executed on the cluster, while theSVV_INTEGRATION
view provides information about the Zero-ETL integration between Aurora and Redshift Serverless. - Is there any way to disable or reduce the frequency of these periodic checks? Unfortunately, there is no direct way for customers to disable or reduce the frequency of these internal monitoring queries. AWS manages the Redshift Serverless cluster and performs these checks to ensure the proper functioning and availability of the service.
- Is it possible to pause the Zero-ETL integration periodically? Currently, there is no option to pause the Zero-ETL integration between Aurora and Redshift Serverless. The integration is designed to provide a seamless and continuous data transfer between the two services. You could provide feedback to AWS regarding the cost impact of these monitoring queries and request the ability to control or reduce their frequency. AWS may consider implementing such a feature in the future if there is sufficient customer demand.
It's important to note that while these monitoring queries may incur some additional costs due to cluster activation, they are essential for AWS to ensure the proper functioning and availability of the Redshift Serverless service. AWS likely balances the frequency of these checks to minimize the cost impact while still maintaining the necessary level of monitoring and management. Hope it helps!
answered a month ago
Relevant content
- asked 9 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 days ago