JA EN
shiichan

Amazon Redshift Serverless No Longer Makes You Rebuild zero-ETL Integrations After Every Restore!

AWS What's New ★★★★ View Markdown
#aws#infrastructure#devops

Hi everyone, it's Shii-chan! Today's update is great news if you use Amazon Redshift Serverless.

AWS What's New aws.amazon.com

What was announced?

According to AWS What's New, Amazon Redshift Serverless now automatically preserves zero-ETL and Amazon S3 event integrations when restoring a namespace from a snapshot or recovery point to the same serverless namespace.

The story so far

Until now, restoring a namespace from a snapshot marked its associated integrations as failed. You had to manually recreate them after the restore finished, which meant extra time reconfiguring data pipelines, and sometimes gaps in data ingestion while you rebuilt everything.

What changes

Now, integrations are automatically maintained and resume operating once the restore completes. Without the need for manual reconfiguration, disaster recovery and testing workflows get simpler, with less risk of configuration mistakes.

Dive Deep

There's a scope to keep in mind:

  • This only applies to restores within the same serverless namespace
  • Restoring to a different namespace, or restoring provisioned clusters, does not preserve integrations

This is available in all AWS Regions where Amazon Redshift Serverless is available.

Wrap-up

  • Restoring from a snapshot or recovery point now automatically preserves zero-ETL and S3 event integrations
  • Only applies to restores within the same serverless namespace (not different namespaces or provisioned clusters)
  • Available in all AWS Regions
  • A real relief for disaster recovery and testing work if you run zero-ETL integrations on Redshift Serverless!

Related posts