If the time zone of your RDS MySQL instance does not match the time zone of your business region, or you need to calibrate the standard time of your instance during the transition between daylight saving time and winter time, you can change the time zone of your instance through the console or API operations. This topic describes how to change and verify the time zone of an RDS MySQL instance and provides a time zone to UTC offset mapping table.
Scenarios
You need to change the time zone of an RDS MySQL instance in the following scenarios:
The time zone of the RDS MySQL instance in your system does not match the time zone of your business region. For example, RDS MySQL instances purchased before May 30, 2021 have a default time zone of SYSTEM, which needs to be changed to the time zone of your business region.
You need to manually adjust the standard time used during the transition between daylight saving time and winter time in countries such as the United States, Canada, Australia, and Europe. For example, when the United Kingdom transitions from winter time to daylight saving time, you need to change the winter time (UTC) to daylight saving time (
UTC+1).
Prerequisites
You have created an RDS MySQL instance.
Precautions
After the time zone parameter is modified, you need to restart the instance for the change to take effect. We recommend that you perform this operation during off-peak hours and ensure that your application has a reconnection mechanism.
When MySQL's default_time_zone is set to SYSTEM, the following risks may exist:
Inconsistent time between primary and secondary nodes
For high-performance local disk high availability instances, different time zones on the operating systems of primary and secondary nodes may cause inconsistent time zones between MySQL primary and secondary nodes, which can affect data consistency in extreme scenarios.
Decreased instance performance
If your business frequently uses
TIMESTAMPtype fields, time zone conversion may cause lock contention issues, leading to instance performance fluctuations.Inconsistent CST time zone parsing between JDBC and MySQL
The CST time zone is ambiguous: MySQL parses it as
UTC+08:00(China Standard Time), while some JDBC versions (such as 8.0.22/23) parse it asUTC - 6(Central Standard Time in the United States). When the operating system time zone is CST, data read from or written to MySQL by JDBC may not meet expectations. Typical case: The time zone CST has different meanings on MySQL Server and on conntector/j.
Change the time zone in the RDS console
Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
In the navigation pane on the left, click Parameters.
On the Modifiable Parameters tab, find the
default_time_zoneparameter, click Running Value, modify the time zone value in the dialog box that appears.NoteFor the meaning of the
default_time_zoneparameter values, see Time zone to UTC offset mapping table.Click Apply Changes, select the effective time period in the dialog box that appears, and then click OK.
NoteIf you want to cancel the modification before submitting the parameter, click Cancel Changes.
Call the API operation to change the time zone
Request example
This example calls the ModifyParameter operation to change the default_time_zone parameter to +9:00.
...
// Parameter settings for API request
ModifyParameterRequest modifyParameterRequest = ModifyParameterRequest.builder()
.DBInstanceId("rm-bp1l94k5sw1zxxxxx")
.parameters("{"default_time_zone":"+9:00"}")
.forcerestart(true)
// Request-level configuration rewrite, can set Http request parameters, etc.
// .requestConfiguration.create().setHttpHeaders(new HttpHeaders()))
.build();
...JSON format response
HTTP/1.1 200 OK
Content-Type:application/json
{
"RequestId": "6D698793-FC2B-5FC1-A6DF-33EDAD1AD6AB"
}Verify the time zone change
Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
In the navigation pane on the left, click Parameters.
On the Edit History tab, check that the modified time zone parameter value has taken effect.

Time zone to UTC offset mapping table
Time zone | Standard time offset | Remarks |
Afghanistan Standard Time | (UTC+04:30) | Kabul |
Alaskan Standard Time | (UTC-09:00) | Alaska |
Arabian Standard Time | (UTC+04:00) | Abu Dhabi, Muscat |
Atlantic Standard Time | (UTC-04:00) | Atlantic Time (Canada) |
AUS Central Standard Time | (UTC+09:30) | Darwin |
AUS Eastern Standard Time | (UTC+10:00) | Canberra, Melbourne, Sydney |
Belarus Standard Time | (UTC+03:00) | Minsk |
Canada Central Standard Time | (UTC-06:00) | Saskatchewan |
Cape Verde Standard Time | (UTC-01:00) | Cabo Verde Is. |
Cen. Australia Standard Time | (UTC+09:30) | Adelaide |
Central America Standard Time | (UTC-06:00) | Central America |
Central Asia Standard Time | (UTC+06:00) | Astana |
Central Brazilian Standard Time | (UTC-04:00) | Cuiaba |
Central Europe Standard Time | (UTC+01:00) | Belgrade, Bratislava, Budapest, Ljubljana, Prague |
Central European Standard Time | (UTC+01:00) | Sarajevo, Skopje, Warsaw, Zagreb |
Central Pacific Standard Time | (UTC+11:00) | Solomon Islands, New Caledonia |
Central Standard Time | (UTC-06:00) | Central Time (US and Canada) |
Central Standard Time (Mexico) | (UTC-06:00) | Guadalajara, Mexico City, Monterrey |
China Standard Time | (UTC+08:00) | Beijing, Chongqing, Hong Kong, Urumqi |
E. Africa Standard Time | (UTC+03:00) | Nairobi |
E. Australia Standard Time | (UTC+10:00) | Brisbane |
E. Europe Standard Time | (UTC+02:00) | Chisinau |
E. South America Standard Time | (UTC-03:00) | Brasilia |
Eastern Standard Time | (UTC-05:00) | Eastern Time (US and Canada) |
Georgian Standard Time | (UTC+04:00) | Tbilisi |
GMT Standard Time | (UTC) | Dublin, Edinburgh, Lisbon, London |
Greenland Standard Time | (UTC-03:00) | Greenland |
Greenwich Standard Time | (UTC) | Monrovia, Reykjavik |
GTB Standard Time | (UTC+02:00) | Athens, Bucharest |
Hawaiian Standard Time | (UTC-10:00) | Hawaii |
India Standard Time | (UTC+05:30) | Chennai, Kolkata, Mumbai, New Delhi |
Jordan Standard Time | (UTC+02:00) | Amman |
Korea Standard Time | (UTC+09:00) | Seoul |
Middle East Standard Time | (UTC+02:00) | Beirut |
Mountain Standard Time | (UTC-07:00) | Mountain Time (US and Canada) |
Mountain Standard Time (Mexico) | (UTC-07:00) | Chihuahua, La Paz, Mazatlan |
US Mountain Standard Time | (UTC-07:00) | Arizona |
New Zealand Standard Time | (UTC+12:00) | Auckland, Wellington |
Newfoundland Standard Time | (UTC-03:30) | Newfoundland |
Pacific SA Standard Time | (UTC-03:00) | Santiago |
Pacific Standard Time | (UTC-08:00) | Pacific Time (US and Canada) |
Pacific Standard Time (Mexico) | (UTC-08:00) | Baja California |
Russia Standard Time | (UTC+03:00) | Moscow, St. Petersburg, Volgograd |
SA Pacific Standard Time | (UTC-05:00) | Bogota, Lima, Quito, Rio Branco |
SE Asia Standard Time | (UTC+07:00) | Bangkok, Hanoi, Jakarta |
China Standard Time | (UTC+08:00) | Kuala Lumpur, Singapore |
Tokyo Standard Time | (UTC+09:00) | Osaka, Sapporo, Tokyo |
US Eastern Standard Time | (UTC-05:00) | Indiana (East) |
UTC | UTC | Coordinated Universal Time |
UTC-02 | (UTC-02:00) | Coordinated Universal Time-02 |
UTC-08 | (UTC-08:00) | Coordinated Universal Time-08 |
UTC-09 | (UTC-09:00) | Coordinated Universal Time-09 |
UTC-11 | (UTC-11:00) | Coordinated Universal Time-11 |
UTC+12 | (UTC+12:00) | Coordinated Universal Time+12 |
W. Australia Standard Time | (UTC+08:00) | Perth |
W. Central Africa Standard Time | (UTC+01:00) | West Central Africa |
W. Europe Standard Time | (UTC+01:00) | Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna |
Kathmandu Time | (UTC+5:45) | Kathmandu |
Myanmar Time | (UTC+6:30) | Rangoon, Nay Pyi Taw |
Uzbekistan Time | (UTC+5) | Lahore, Karachi, Islamabad |
Samoa Western Standard Time | (UTC+13) | Nuku Alofa, Appiah |
UTC-12 | (UTC-12) | Coordinated Universal Time-12 |
FAQ
Related API operations
Modify the default_time_zone value through the API (ModifyParameter).