Managing the service updates - Amazon ElastiCache for Redis
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Managing the service updates

ElastiCache for Redis service updates are released on a regular basis. If you have one or more qualifying clusters for those service updates, you receive notifications through email, SNS, the Personal Health Dashboard (PHD), and Amazon CloudWatch events when the updates are released. The updates are also displayed on the Service Updates page on the ElastiCache for Redis console. By using this dashboard, you can view all the service updates and their status for your ElastiCache for Redis fleet.

You control when to apply an update before an auto-update starts. We strongly recommend that you apply any updates of type security-update as soon as possible to ensure that your ElastiCache for Redis are always up-to-date with current security patches.

The following sections explore these options in detail.

Applying the service updates

You can start applying the service updates to your fleet from the time that the updates have an available status. Service updates are cumulative. In other words, any updates that you haven't applied yet are included with your latest update.

If a service update has auto-update enabled, you can choose to not take any action when it becomes available. ElastiCache for Redis will schedule to apply the update during your clusters' maintenance window after the Auto-update start date. You will receive related notifications for each stage of the update.

Note

You can apply only those service updates that have an available or scheduled status.

For more information about reviewing and applying any service-specific updates to applicable ElastiCache for Redis clusters, see Applying the service updates using the console.

When a new service update is available for one or more of your ElastiCache for Redis clusters, you can use the ElastiCache for Redis console, API, or Amazon CLI to apply the update. The following sections explain the options that you can use to apply updates.

Applying the service updates using the console

To view the list of available service updates, along with other information, go to the Service Updates page in the console.

  1. Sign in to the Amazon Web Services Management Console and open the Amazon ElastiCache console at https://console.amazonaws.cn/elasticache/.

  2. On the navigation pane, choose Service Updates.

  3. Under Service updates you can view the following:

    • Service update name: The unique name of the service update

    • Update type: The type of the service update, which is one of security-update or engine-update

    • Update severity: The priority of applying the update:

      • critical: We recommend that you apply this update immediately (within 14 days or less).

      • important: We recommend that you apply this update as soon as your business flow allows (within 30 days or less).

      • medium: We recommend that you apply this update as soon as you can (within 60 days or less).

      • low: We recommend that you apply this update as soon as you can (within 90 days or less).

    • Engine version: If the update type is engine-update, the engine version that is being updated.

    • Release Date: When the update is released and available to apply on your Redis fleet.

    • Recommended Apply By Date: ElastiCache guidance date to apply the updates by.

    • Status: The status of the update, which is one of the following:

      • available: The update is available for requisite Redis clusters.

      • complete: The update has been applied and all Redis clusters are compliant. For more information, see Self-service security updates for compliance.

      • cancelled: The update has been canceled and is no longer necessary.

      • expired: The update is no longer available to apply.

  4. Choose an individual update (not the button to its left) to view details of the service update.

    In the Cluster update status section, you can view a list of clusters where the service update has not been applied or has just been applied recently. For each cluster, you can view the following:

    • Cluster name: The name of the cluster

    • Nodes updated: The ratio of individual nodes within a specific cluster that were updated or remain available for the specific service update.

    • Update Type: The type of the service update, which is one of security-update or engine-update

    • Status: The status of the service update on the cluster, which is one of the following:

      • available: The update is available for the requisite cluster.

      • in-progres: The update is being applied to this cluster.

      • scheduled: The update date has been scheduled.

      • complete: The update has been successfully applied. Cluster with a complete status will be displayed for 7 days after its completion.

      If you chose any or all of the clusters with the available or scheduled status, and then chose Apply now, the update will start being applied on those clusters.

Applying the service updates using the Amazon CLI

After you receive notification that service updates are available, you can inspect and apply them using the Amazon CLI:

  • To retrieve a description of the service updates that are available, run the following command:

    aws elasticache describe-service-updates --status available

    For more information, see describe-service-updates.

  • To apply a service update on a list of clusters, run the following command:

    aws elasticache batch-update-cluster --service-update ServiceUpdateNameToApply=sample-service-update --cluster-names cluster-1 cluster2

    For more information, see batch-apply-update-action.