Applying the Self-Service Updates - 用于 Redis 的 Amazon ElastiCache
AWS 文档中描述的 AWS 服务或功能可能因区域而异。要查看适用于中国区域的差异,请参阅中国的 AWS 服务入门

如果我们为英文版本指南提供翻译,那么如果存在任何冲突,将以英文版本指南为准。在提供翻译时使用机器翻译。

Applying the Self-Service Updates

您可以从服务更新具有 available (可用) 状态起开始应用服务更新,直到它们具有 expired (过期) 状态为止。security (安全性) 类型的服务更新是累积更新。换句话说,您尚未应用的任何未过期更新都包含在您的最新更新中。

注意

您只能应用具有 available (可用) 状态的服务更新,即使建议的应用截止日期已过也是如此。

有关查看 Redis 队列并向适用的 Redis 集群应用任何特定于服务的更新的更多信息,请参阅Applying the Service Updates Using the Console for Redis

在新的服务更新可用于一个或多个 Redis 集群时,您可以使用 ElastiCache 控制台、API 或 AWS CLI 来应用该更新。以下各节说明了可用于应用更新的选项。

Applying the Service Updates Using the Console

您可以使用以下控制台选项之一应用服务更新。

Applying the Service Updates Using the Console for Redis

选择此项以查看各 Redis 集群的 Update Status (更新状态),然后为服务更新选择 Apply (应用)View (查看)Stop (停止)。如果有服务更新可用,则控制台会在 Redis 页面的顶部显示一个横幅,如下所示。

如果您选择 Apply Now (立即应用),则可选择将服务更新应用于此工作流程中的所有或部分适用的集群,如下所示。

注意

如果您选择 Dismiss (关闭),则控制台将停止显示该控制台会话的横幅。不过,当您下次刷新会话时,横幅将重新出现。

Apply Updates Now (立即应用更新) 页上,可以使用以下选项:

  • Auto-Update after Due Date: If this attribute is yes, after the Recommended apply by Date has passed, ElastiCache schedules clusters yet to be updated in the appropriate maintenance window. Updates are applied along with other applicable updates. You can continue to apply the updates until the update expiration date.

    If this attribute is no and you don't apply the self-service update before it expires, ElastiCache doesn't automatically apply the service update for you. If your cluster is part of one or more ElastiCache-supported compliance programs and isn't updated, it remains out of compliance until the next cumulative update becomes available.

  • The Nodes Updated ratio value for your Redis cluster and the Estimated Update Time value help you plan your maintenance schedule. If service updates exceed the estimated time constraints for your business flows, you can stop updates and reapply them at a later date. For more information, see Stopping the Self-Service Updates.

  • If you choose to apply the service updates to any or all available Redis clusters, choose Confirm. If you choose this, you then view the Service Updates page, where you can monitor the status of your service update.

  • If you choose Cancel, you can explore further options, as explained following.

在 ElastiCache 控制面板上,您可以选中每个 Redis 集群的 Update Status (更新状态),如下所示。

Update Status (更新状态) 显示下列项之一:

  • update available: An update is available to apply to this cluster.

  • not-applied: An update is available but not yet applied.

  • scheduling: The update date is being scheduled.

  • scheduled: The update date has been scheduled.

  • waiting-to-start: The update process will soon begin.

  • in-progress: The update is being applied to this cluster, rendering it unavailable for the duration of the value in Estimated Update Time.

  • stopping: An in-progress update has been interrupted before completion.

  • stopped: The update has been terminated.

    If you stop an in-progress update on a Redis cluster, some nodes might be updated while others are not. The stopping process doesn't roll back any changes to already updated nodes. You can reapply the update to those nodes that still have an available status at your convenience if the update doesn't have an Expired status.

  • complete: The update has been successfully applied.

  • up to date: The cluster doesn't have any outstanding active service updates and your cluster is compliant. For more information about compliance, see 用于实现合规性的自助安全更新。.

Applying the Service Updates Using the Service Updates List

要查看各个服务更新及其状态和其他信息的列表,请选择 Service Updates List (服务更新列表) 选项卡。

Service Updates List (服务更新列表) 中,您可以查看以下内容:

  • Service Update Name: A unique identifier for the service update.

  • 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 用于实现合规性的自助安全更新。.

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

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

  • 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).

  • Update Type: For this version, only security updates are supported.

  • 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.

选择单个更新可提供其他详细信息,包括:

  • Update Description: Provides details on the service update.

  • Update Expiration Date: The date when the service update expires and no longer is available. Any updates that aren't applied before their expiration date are cumulatively rolled into the next update.

重要

强烈建议您尽快应用 security (安全性) 类型的更新。这样做有助于确保您的 Redis 集群始终通过最新的安全补丁保持最新且合规。有关更多信息,请参阅 用于实现合规性的自助安全更新。。)

要查看与适用的 Redis 集群相关的各个服务更新的列表,请选择 Service Update Status (服务更新状态) 选项卡。

Service Updates Status (服务更新状态) 列表中,您可以查看以下内容:

  • Service Update Name: Detailed information about the service update.

  • Cluster Name: The list of your Redis clusters that are eligible for the update.

  • Nodes Updated: The ratio of individual nodes within a specific cluster that were updated or remain available for the specific service 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 you can (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).

  • Update Type: For this version, only security updates are supported.

  • Service Update 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.

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

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

  • Service Update SLA Met: This reflects whether your cluster is compliant.

    • yes: All available updates have been applied to this cluster and available nodes by the apply-by date.

    • no: The service update might have been applied successfully to one or more nodes, but other nodes within the cluster still have an available status. This typically happens when a service update is applied and then stopped.

      注意

      If you stop the progress of a service update on a cluster, any nodes that are already updated have a complete status. Any nodes that have an In Progress or Stopping status revert to a Stopped status, and the Service Update SLA Met status changes to no.

    • N/A: The replication group was created after the recommended apply-by date.

  • Cluster Status Modified Date: The latest date that the cluster was modified with a service update.

注意

Show Previous Updates (显示以前的更新) 复选框(如果选中)显示不再可用的早期更新的列表。

Applying the Service Updates Using the AWS CLI

在收到服务更新可用的通知后,您可以使用 AWS CLI 检测和应用这些更新:

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

    aws elasticache describe-service-updates --service-update-status available

    For more information, see DescribeServiceUpdates.

  • To view update actions that have a not-applied or stopped status, run the following command:

    aws elasticache describe-update-actions --service-update-name sample-service-update --update-action-status not-applied stopped

    For more information, see DescribeUpdateActions.

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

    aws elasticache batch-apply-update-action --service-update-name sample-service-update --replication-group-ids my-replication-group-1 my-replication-group-2

    For more information, see BatchApplyUpdateAction.