On this put up, we take you thru customization choices for managing the schedule of your Amazon Redshift upkeep occasions, together with Amazon Redshift upkeep tracks for optimizing cluster efficiency. We additionally stroll you thru easy methods to arrange Amazon Redshift occasion notifications utilizing Amazon SNS.
For provisioned clusters, Amazon Redshift periodically performs upkeep to use fixes, enhancements, and new options to your cluster. Amazon Redshift assigns a 30-minute upkeep window. To prioritize enterprise continuity and to align along with your operational wants, this upkeep window is totally customizable, both programmatically or by way of the AWS Administration Console for Amazon Redshift. For extra data, see Managing clusters utilizing the console.
A strong notification system is on the market to tell you about upkeep actions in your Amazon Redshift clusters that can assist you plan successfully and preserve communication along with your customers about scheduled system updates. Utilizing the Amazon Redshift integration with Amazon Easy Notification Service (Amazon SNS), you may allow notifications of an upcoming upkeep occasions by creating an Amazon Redshift occasion notification subscription.
Customizing your provisioned cluster upkeep occasions
Amazon Redshift gives a number of methods to manage how AWS maintains your provisioned clusters. The next are the first customization choices out there:
- Modifying the schedule for upcoming upkeep occasions: You may management once we deploy updates to your clusters.
- Deferring upcoming upkeep: You may defer non-mandatory upkeep updates for an outlined time frame.
- Selecting a upkeep observe to optimize efficiency: You may select whether or not your cluster runs probably the most just lately launched model or the model launched previous to probably the most just lately launched model.
- Receiving notifications of upcoming upkeep: You may arrange notifications for upcoming upkeep occasions scheduled in your clusters.
There isn’t a set upkeep window for Amazon Redshift Serverless. When a brand new model turns into out there for a workgroup’s chosen observe, Amazon Redshift Serverless usually applies the replace throughout an idle interval so long as there isn’t a pending observe replace request. If the workgroup doesn’t expertise an idle interval inside 14 days, Redshift Serverless forces the model replace.
Modifying the schedule for upcoming upkeep occasions
If a upkeep occasion is scheduled for a given week, it begins through the assigned 30-minute upkeep window. Whereas Amazon Redshift is performing upkeep, it terminates queries or different operations which might be in progress. If there are not any upkeep duties to carry out through the scheduled upkeep window, your cluster continues to function usually till the subsequent scheduled upkeep window.
You may change the scheduled upkeep window by modifying the cluster, both programmatically or through the use of the Amazon Redshift console. You will discover the upkeep window and set the day and time it happens for the cluster below the Upkeep tab.
Deferring upcoming upkeep
Amazon Redshift gives extra management over cluster upkeep by deferring upcoming upkeep for as much as 45 days. This characteristic is invaluable whenever you want uninterrupted cluster entry throughout essential enterprise durations. As an illustration, in case your cluster’s upkeep window is ready to Thursday from 5:30–6:00 UTC, and it’s essential have nonstop entry to your cluster for the subsequent 2 weeks, you may defer upkeep to a date 2 weeks from now. We don’t carry out upkeep in your cluster throughout a specified deferment.
Whereas commonplace upkeep may be deferred, obligatory updates—resembling essential safety patches, which usually happen at most yearly, or {hardware} updates—should proceed as required. In these instances, Amazon Redshift notifies you thru each the console and your Amazon SNS subscription, marking these as pending occasions, and implements these adjustments no matter deferral settings to take care of the safety and reliability of your infrastructure.
Whereas performing deferred upkeep on Amazon Redshift clusters with Amazon Redshift information sharing configured, sustaining model compatibility between producer and shopper clusters is essential for supporting dependable information sharing. As a greatest observe, you must hold producer and shopper clusters inside two variations of one another to attenuate potential compatibility points. As an illustration, if a producer cluster is operating model P195, shopper clusters needs to be between P193 and P197. To help efficient model administration, you may as well use notification techniques that present well timed alerts about deliberate cluster patching, enabling proactive model alignment and lowering the chance of potential information sharing disruptions.
Selecting a upkeep observe to optimize cluster efficiency
Amazon Redshift gives two upkeep tracks that present you management over how and when cluster model updates are utilized, serving to to make sure optimum efficiency whereas minimizing enterprise disruption. The Present observe mechanically applies updates throughout your scheduled upkeep window, retaining your cluster on the newest model with the latest options and enhancements. For organizations requiring extra validation time, the Trailing observe delays model updates after launch, permitting thorough testing of your workloads in improvement environments earlier than manufacturing deployment.
Utilizing the Amazon Redshift Trailing observe in your manufacturing setting, and the Present observe in your testing and improvement setting, provides you extra diligence and time to judge the newest launch. This method lets you validate model updates totally earlier than they attain your manufacturing setting. Moreover, scheduling upkeep home windows throughout off-peak hours and establishing a communication protocol to inform stakeholders about upcoming upkeep occasions minimizes potential impression on manufacturing due to upkeep occasions.
Receiving notifications of upcoming upkeep occasions
By organising an Amazon SNS e mail notification, you may obtain real-time updates about your cluster’s upkeep particulars immediately in your inbox. See Amazon Redshift provisioned cluster occasion notifications for upkeep occasion classes together with occasion ID, severity, and notification descriptions.
Arrange Amazon Redshift occasion notifications utilizing Amazon SNS
This part demonstrates how one can arrange Amazon SNS notifications for Amazon Redshift upkeep occasions. For organising the occasion notification, we showcase the next two choices on this put up:
Amazon SNS notifications may also be arrange utilizing AWS Command Line Interface (AWS CLI).
Stipulations
We assume you could have already deployed an Amazon Redshift provisioned cluster. For extra data on making a provisioned cluster, see Making a cluster.
You additionally want AWS Identification and Entry Administration (IAM) permission to create occasion subscriptions in an Amazon Redshift cluster and matters in Amazon SNS. For extra data, see Organising entry for Amazon SNS.
Utilizing the console
On this part, you arrange notifications for Amazon Redshift upkeep occasions from the AWS console.
- Open the Amazon Redshift console.
- Within the left navigation pane, select Amazon Redshift after which select Occasions.
- Choose Occasion Subscriptions after which select Create occasion subscription.
- On the Create occasion subscription web page, enter the next data:
- Within the Subscription particulars part, below Occasion subscription identify, enter a reputation for the occasion.
- Within the Subscription kind part, below Supply kind, choose Cluster.
- For Cluster, select Choose clusters, after which choose your cluster IDs.
- For Classes, choose your classes.
- For Severity, choose both Error or Information, Error.
- Within the Subscription actions part, choose an current matter or select Create a brand new Amazon SNS matter, enter a subject identify after which select Create matter. See create a subject for details about creating a brand new matter utilizing the Amazon SNS console.
- Select Create occasion subscription.
- Beneath the Occasion subscriptions part, now you can see the brand new occasion subscription.
- Within the Amazon SNS console, select Matters and choose the subject you configured in Amazon Redshift occasions within the earlier step.
- Select Create Subscription, below Protocol select E mail and enter a sound e mail tackle and select Create Subscription. You too can choose extra protocols based mostly in your desire.
- Select Pending Subscription and select Request Affirmation. After the affirmation e mail is obtained, select the Affirm Subscription hyperlink within the e mail.
These occasion notifications work on the AWS account stage.
Utilizing an AWS CloudFormation stack
On this part, you construct and configure occasion notifications on current Amazon Redshift clusters utilizing an AWS CloudFormation stack:
- Obtain this CloudFormation template.
- Go to the AWS CloudFormation console.
- Select Create Stack and choose With new sources (commonplace).
- Beneath Specify template, choose Add a template file.
- Choose Select file and add the CloudFormation template you downloaded in Step 1 and select Subsequent.
- In Stack Identify, enter
AmazonRedshift-EventSubscription. - Enter the Parameters as follows:
- For ClusterIdentifier, enter the worth in your Amazon Redshift cluster. This may be discovered by navigating to the Amazon Redshift console and finding the cluster identifier. To subscribe for all clusters in your account, depart this area clean.
- For EmailAddress, enter a sound e mail tackle.
- For EventSubscriptionName, enter the worth in your occasion subscription. (for instance,
Redshift-event-subscription). - For MonitorAllClusters, choose from dropdown:
- Choose False should you entered a cluster identifier (subscribing to notification for one cluster)
- Choose True if you wish to monitor all clusters.
- For Severity Degree, choose from dropdown:
- Choose Error if you wish to subscribe to error notifications solely.
- Choose Information if you wish to subscribe to each error and data notifications.
- Select Subsequent, evaluation the ultimate web page, and select Submit.
- You’ll obtain an e mail with topic AWS Notification – Subscription Affirmation. Select Affirm subscription.
- Go to the Amazon Redshift console and below Occasions, confirm the occasion subscription.
Pattern e mail notifications from Amazon SNS
On this part, we present you some examples of notification emails despatched by way of Amazon SNS based mostly on the configuration:
Database Replace notification:
Amazon Redshift usually releases cluster variations. The Scheduled Database Replace notification, proven within the following screenshot, is shipped earlier than an upcoming Amazon Redshift patch model improve.
System Replace notification:
AWS performs common updates to the underlying {hardware} and working system of Amazon Redshift clusters, together with safety patches and efficiency enhancements. The Scheduled System Replace notification, proven within the following screenshot, is shipped earlier than scheduled {hardware} and OS updates.
If you happen to’re operating your non-production clusters on the Present observe and manufacturing companies on the Trailing observe, you may obtain notifications when your non-production clusters endure patching, so you may proactively check the discharge earlier than it goes to your manufacturing servers. You may promptly report points with the replace by way of the AWS Assist Heart console. If the reported points are nonetheless current when your manufacturing clusters are scheduled for a similar patch within the Trailing observe, you may defer upkeep till the issues are resolved for stability. To discover ways to change tracks for an Amazon Redshift cluster, see Switching between tracks.
Keep knowledgeable about model updates utilizing RSS feeds
To remain knowledgeable in regards to the newest cluster variations launched for Amazon Redshift, you may as well use the RSS feed of the Cluster variations for Amazon Redshift web page in your monitoring toolkit. In contrast to real-time cluster notifications, this feed serves as your window into documentation updates, supplying you with early updates into revealed options and greatest practices. Whereas it received’t warn you about speedy cluster upkeep or safety patches, you’ll be notified each time Amazon updates their cluster administration documentation. By including this RSS feed to your most popular reader, you’re subscribing to a steady stream of AWS documentation updates, serving to you to take care of a proactive quite than reactive method to your information warehouse administration.
Organising an RSS feed in your Amazon Redshift documentation is easy and gives a number of choices to fit your workflow preferences. The secret is to first select your most popular RSS reader, resembling Slack or Microsoft Outlook, or your most popular web-based RSS feed reader. To start out receiving notifications about AWS documentation updates, add the RSS feed URL to the reader to begin receiving updates. After setup, you’ll obtain notifications each time the Amazon Redshift cluster administration documentation is up to date, serving to to maintain you knowledgeable about new options and greatest practices.
You too can see the updates immediately on the Cluster variations for Amazon Redshift web page to remain knowledgeable each time a brand new model has been launched and earlier than it’s scheduled to be launched to your cluster.
Cleanup
If you happen to don’t want the Amazon SNS notification created for this put up, delete the Amazon SNS matters from the Amazon SNS console to keep away from incurring future costs. When you’ve got configured the notification utilizing AWS CloudFormation, delete the stack to delete associated configurations. See Amazon SNS Pricing for pricing data for the service.
Conclusion
On this put up, you realized easy methods to configure upkeep occasion notifications for Amazon Redshift provisioned clusters utilizing Amazon SNS. We additionally defined the small print of Amazon Redshift upkeep actions, together with easy methods to handle the schedule for upcoming upkeep through the use of Amazon Redshift upkeep tracks to optimize cluster efficiency, and utilizing RSS feeds to obtain real-time updates about essential cluster data.Upgrading your Amazon Redshift clusters to the steered upkeep observe is essential for optimizing cluster efficiency and to assist to make sure that the newest fixes, safety patches and enhancements are utilized to your clusters. Seamless integration with the Amazon SNS notification system helps make sure that you’re knowledgeable of upkeep occasions forward of time, so that you could put together for them. This proactive method lets you plan successfully and preserve communication along with your customers about scheduled system updates.
To be taught extra about Amazon Redshift cluster variations and upkeep home windows, see to Cluster variations for Amazon Redshift, Cluster upkeep, and MaintenanceTrack.
In regards to the authors
