All Products
Search
Document Center

ApsaraDB RDS:Time zones

Last Updated:Mar 28, 2026

ApsaraDB RDS for MySQL and ApsaraDB RDS for PostgreSQL each handle time zones differently. Use the tables below to find the correct named time zone value for your instance configuration.

  • RDS for MySQL: Use the abbreviation-to-name mapping to translate a common abbreviation (such as CST or JST) into a named time zone value accepted by the time_zone parameter. The common named time zones table lists all supported values for that parameter.

  • RDS for PostgreSQL: Use the region-to-default table to identify the default named time zone assigned when an instance is created in a given region.

Time zone abbreviation mappings for RDS for MySQL

RDS for MySQL accepts named time zone values—not abbreviations—as the time_zone parameter value. Use this table to find the named time zone that corresponds to a common abbreviation.

AbbreviationNamed time zone
CESTEurope/Berlin
CST+08:00
CETEurope/Berlin
GSTAsia/Dubai
JSTAsia/Tokyo
ESTAustralia/Sydney
BSTEurope/London
WIBAsia/Jakarta
AESTAustralia/Sydney
AEDTAustralia/Sydney
PDTAmerica/Los_Angeles
PSTAmerica/Los_Angeles
EDTAmerica/New_York

Supported named time zones for RDS for MySQL and RDS for PostgreSQL

The following named time zones are supported for both RDS for MySQL and RDS for PostgreSQL instances. Named time zones follow the IANA time zone database format.

AreaNamed time zones
AfricaAfrica/Cairo, Africa/Casablanca, Africa/Harare, Africa/Monrovia, Africa/Nairobi, Africa/Tripoli, and Africa/Windhoek
AmericaAmerica/Araguaina, America/Asuncion, America/Bogota, America/Caracas, America/Chihuahua, America/Cuiaba, America/Denver, America/Fortaleza, America/Guatemala, America/Halifax, America/Manaus, America/Matamoros, America/Monterrey, America/Montevideo, America/New_York, America/Phoenix, America/Santiago, and America/Tijuana
AsiaAsia/Amman, Asia/Ashgabat, Asia/Baghdad, Asia/Baku, Asia/Bangkok, Asia/Beirut, Asia/Calcutta, Asia/Damascus, Asia/Dhaka, Asia/Irkutsk, Asia/Jerusalem, Asia/Kabul, Asia/Karachi, Asia/Kathmandu, Asia/Krasnoyarsk, Asia/Madadan, Asia/Muscat, Asia/Novosibirsk, Asia/Riyadh, Asia/Seoul, Asia/Shanghai, Asia/Singapore, Asia/Taipei, Asia/Tehran, Asia/Tokyo, Asia/Ulaanbaatar, Asia/Vladivostok, Asia/Yakutsk, and Asia/Yerevan
AtlanticAtlantic/Azores
AustraliaAustralia/Adelaide, Australia/Brisbane, Australia/Darwin, Australia/Hobart, Australia/Perth, and Australia/Sydney
BrazilBrazil/East
CanadaCanada/Newfoundland and Canada/Saskatchewan
EuropeEurope/Amsterdam, Europe/Athens, Europe/Dublin, Europe/Helsinki, Europe/Istanbul, Europe/Kaliningrad, Europe/Moscow, Europe/Paris, Europe/Prague, and Europe/Sarajevo
PacificPacific/Auckland, Pacific/Fiji, Pacific/Guam, Pacific/Honolulu, and Pacific/Samoa
USUS/Alaska, US/Central, US/East-Indiana, US/Eastern, and US/Pacific

Default time zones by region for RDS for PostgreSQL

When you create an RDS for PostgreSQL instance, it is assigned the default named time zone for its region. The table below lists the default time zone for each available region.

RegionRegion IDDefault time zone
China (Hangzhou)cn-hangzhouAsia/Shanghai
China (Shanghai)cn-shanghaiAsia/Shanghai
China (Nanjing - Local Region - Decommissioning)cn-nanjingAsia/Shanghai
China (Qingdao)cn-qingdaoAsia/Shanghai
China (Beijing)cn-beijingAsia/Shanghai
China (Zhangjiakou)cn-zhangjiakouAsia/Shanghai
China (Hohhot)cn-huhehaoteAsia/Shanghai
China (Ulanqab)cn-wulanchabuAsia/Shanghai
China (Shenzhen)cn-shenzhenAsia/Shanghai
China (Heyuan)cn-heyuanAsia/Shanghai
China (Guangzhou)cn-guangzhouAsia/Shanghai
China (Chengdu)cn-chengduAsia/Shanghai
China (Hong Kong)cn-hongkongAsia/Hong_Kong
Singaporeap-southeast-1Asia/Singapore
Malaysia (Kuala Lumpur)ap-southeast-3Asia/Kuala_Lumpur
Indonesia (Jakarta)ap-southeast-5Asia/Jakarta
Japan (Tokyo)ap-northeast-1Asia/Tokyo
Germany (Frankfurt)eu-central-1Europe/Berlin
UK (London)eu-west-1Europe/London
US (Silicon Valley)us-west-1America/Los_Angeles
US (Virginia)us-east-1America/New_York
UAE (Dubai)me-east-1Asia/Dubai