The maintenance schedule type of the DB system. EARLY: Maintenance schedule follows a cycle where upgrades are performed when versions become deprecated. REGULAR: Maintenance schedule follows the normal cycle where upgrades are performed when versions become unavailable.
The version that is expected to be targeted during the next scheduled maintenance run.
The time the scheduled maintenance is expected to start, as described by RFC 3339.
The preferred version to target when performing an automatic MySQL upgrade.
OLDEST: Choose the oldest available MySQL version based on the current version of the DB System. SECOND_NEWEST: Choose the MySQL version before the newest for auto-upgrade. NEWEST: Choose the latest and greatest MySQL version available for auto-upgrade.
The preferred version track to target when performing an automatic MySQL upgrade. LONG_TERM_SUPPORT: No MySQL database behavior changes. INNOVATION: Provides access to the latest features and all bug fixes. FOLLOW: Follows the track of the current MySQL version.
The start time of the maintenance window.
This string is of the format: \"{day-of-week} {time-of-day}\".
\"{day-of-week}\" is a case-insensitive string like \"mon\", \"tue\", &c.
\"{time-of-day}\" is the \"Time\" portion of an RFC3339-formatted timestamp. Any second or sub-second time data will be truncated to zero.
If you set the read replica maintenance window to \"\" or if not specified, the read replica is set same as the DB system maintenance window.
The Maintenance Policy for the DB System or Read Replica that this model is included in.