[scale-infra] Amazon Aurora MySQL 1 (with MySQL 5.6 compatibility) will reach end of life on February 28, 2023 [AWS Account: 355993445259] [US-EAST-1]

[Ilan Rabinovitch]

(as a non-list member I dont get replies if you're not replying to me as
well)

the upgrade will resulted in a 10 minute outage for reg.

The way to work around it is clone the DB and cut over seems to be spin up
a new cluster thats upgraded, cut over, kill old cluster.

On Fri, Feb 24, 2023 at 4:31 AM Ilan Rabinovitch <ilan at linuxfests.org>
wrote:

>
>
> We really dont want the website down during  or leading up to SCALE.
>
> Let me know if I need to grab this.
>
> ---------- Forwarded message ---------
> From: Amazon Web Services, Inc. <no-reply-aws at amazon.com>
> Date: Fri, Feb 24, 2023 at 4:29 AM
> Subject: Amazon Aurora MySQL 1 (with MySQL 5.6 compatibility) will reach
> end of life on February 28, 2023 [AWS Account: 355993445259] [US-EAST-1]
> To: <ilan at linuxfests.org>
>
>
> Hello,
>
> You are receiving this message because you have one or more Amazon Aurora
> MySQL clusters running a version of Aurora MySQL 1 (with MySQL 5.6
> compatibility) in the US-EAST-1 Region.
>
> Amazon Aurora MySQL 1 (with MySQL 5.6 compatibility) will reach end of
> life on February 28, 2023. We are providing you with a one week notice so
> you have sufficient time to upgrade your database cluster(s). You can find
> additional information needed to plan your upgrade including a detailed
> timeline with milestones in the 'Preparing for Amazon Aurora
> MySQL-Compatible Edition version 1 end of life' documentation [1].
>
> Clusters that are running these deprecated engine versions after March 1,
> 2023 will be upgraded on your behalf within a maintenance window after
> March 1, 2023. The major version upgrade will start within your maintenance
> window and typically finish within that timeframe. Depending on the cluster
> and the database activity at the time, the upgrade process may extend
> beyond the maintenance window. For more information, please refer to the
> Amazon RDS maintenance window [2].
>
> The clusters we identified as affected are listed in your 'Affected
> resources' tab of your AWS Health Dashboard. You may also find clusters
> affected by this deprecation notice by utilizing the 'Finding clusters
> affected by this end-of-life process' guide [3].
>
> Should you have any questions or concerns, the AWS Support Team is
> available on re:Post [4] and via Premium Support [5].
>
> [1]
> https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html
> [2]
> https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html#Concepts.DBMaintenance
> [3]
> https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html#find-cluster
> [4] https://repost.aws/
> [5] https://aws.amazon.com/support
>
> Sincerely,
> Amazon Web Services
>
> Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com
> is a registered trademark of Amazon.com, Inc. This message was produced and
> distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA
> 98109-5210
>
> ---
> Reference:
> https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-east-1::event/RDS/AWS_RDS_OPERATIONAL_NOTIFICATION/AWS_RDS_OPERATIONAL_NOTIFICATION_a6c3c27c8fa9a17b4966661b72fa8534d37f3090b2ca1b5040c2ff611f27a90f&eventTab=details
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfests.org/pipermail/scale-infra/attachments/20230224/f22ed9a3/attachment.html>