All Products
Search
Document Center

ApsaraDB RDS:Modify the time zone

Last Updated:Sep 16, 2026

If your RDS MySQL instance's time zone does not match your business region, or if you need to adjust for the switch between daylight saving and standard time, you can modify the instance's time zone in the RDS console or by using an API. This article shows how to modify and verify the time zone of an RDS MySQL instance and provides a reference table of time zones and their UTC offsets.

Scenarios

You may need to modify the time zone of your RDS MySQL instance for the following reasons:

  • The time zone of your RDS MySQL instance does not match the time zone of your business region. For example, the default time zone for RDS MySQL instances purchased before May 30, 2021, is SYSTEM. You need to change this to the time zone of your business region.

  • In countries such as the United States, Canada, Australia, and Europe, you need to manually adjust the standard time when switching between daylight saving time and winter time. For example, when the United Kingdom switches from winter time to daylight saving time, you need to change the time from winter time (UTC) to daylight saving time (UTC+1).

Prerequisites

You have an RDS MySQL instance.

Precautions

  • Changes to the time zone parameter take effect only after you restart an instance. We recommend performing this operation during off-peak hours and ensuring that your application has an automatic reconnection mechanism.

  • Setting the default_time_zone parameter to SYSTEM can pose the following risks:

    • Time inconsistency between primary and secondary nodes

      For a high-availability RDS MySQL instance that uses high-performance local disks, the operating system time zones on the primary and secondary nodes might be different. This mismatch can cause a time zone difference between the primary and secondary MySQL nodes and, in extreme cases, affect data consistency.

    • Instance performance degradation

      If your services frequently use TIMESTAMP fields, lock contention may occur due to time zone conversions, leading to fluctuations in instance performance.

    • Inconsistent CST parsing between JDBC and MySQL

      The CST time zone is ambiguous: MySQL interprets it by default as UTC+08:00 China Standard Time, whereas some JDBC versions (such as 8.0.22/23) interpret it as UTC - 6 Central Standard Time. If the time zone of the host operating system is CST, this can cause unexpected data when JDBC reads from or writes to MySQL. A typical case: The time zone CST has different meanings on MySQL Server and on conntector/j.

Modify the time zone in the console

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

  2. In the navigation pane on the left, click Parameters.

  3. On the Modifiable Parameters tab, find the default_time_zone parameter, click Running Value, and change the time zone value in the dialog box that appears.

    Note

    For a description of the values for the default_time_zone parameter, see Time Zone and UTC Offset Reference Table.

  4. Click Apply Changes. In the dialog box that appears, specify when you want the change to take effect, and then click OK.

    Note

    Before you apply the changes, you can click Cancel to discard the modifications.

Modify the time zone via API

Example request

This example shows how to call the ModifyParameter API to modify 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(RequestConfiguration.create().setHttpHeaders(new HttpHeaders()))
                .build();
...

JSON is the format of the returned result.

HTTP/1.1 200 OK
Content-Type:application/json

{
  "RequestId": "6D698793-FC2B-5FC1-A6DF-33EDAD1AD6AB"
}

Verify the time zone change

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

  2. In the navigation pane on the left, click Parameters.

  3. On the Edit History tab, verify that the new time zone parameter has taken effect.

    修改历史

Time zones and UTC offsets

Time zone

UTC offset

Description

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)

Cape Verde Islands

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+05:45)

Kathmandu

Myanmar Time

(UTC+06:30)

Yangon, Naypyidaw

Uzbekistan Time

(UTC+05:00)

Tashkent

Samoa Western Standard Time

(UTC+13:00)

Nuku'alofa, Apia

UTC-12

(UTC-12:00)

Coordinated Universal Time-12

FAQ

I selected the UTC time zone when purchasing an instance, but system_time_zone is displayed as EDT. Will this affect my business data?

In RDS MySQL, the UTC time zone that you select when you create an instance is directly mapped to the initial value of the default_time_zone parameter. Time calculations and storage behavior for SQL queries are controlled by the default_time_zone parameter. Therefore, by default, time is processed based on the UTC time zone. For more information, see [Product/Feature Change] The default time zone for new RDS MySQL instances is changed from SYSTEM to UTC.

The system_time_zone parameter indicates the time zone of the underlying operating system when MySQL starts and does not directly affect time calculations in SQL queries. However, note that if you change the default_time_zone parameter to SYSTEM after the instance is created (This is not recommended because it may cause additional performance overhead and related risks), time calculations in SQL queries will inherit the time zone setting from system_time_zone, which may affect your business data. You can modify the value of the default_time_zone parameter in the RDS console (Modify the time zone) or by using the ModifyParameter API.

For more information, see the system_time_zone topic in the official MySQL documentation.

Related APIs

You can modify the value of default_time_zone by calling the ModifyParameter API.