DEV Community: mrboogiej

MongoDB 8.0 Debuts on Alibaba Cloud Discover Enhanced Performance and Security!

mrboogiej — Tue, 27 May 2025 07:52:10 +0000

In the ever-evolving landscape of database technology, staying ahead of the curve is not just a preference - it’s a necessity.

Alibaba Cloud is proud to announce the general availability of MongoDB 8.0 on ApsaraDB for MongoDB, delivering groundbreaking performance, security, and scalability to developers and enterprises worldwide. Whether you’re building AI-driven apps, securing sensitive data, or scaling mission-critical workloads, MongoDB 8.0 empowers you to stay ahead.

In this blog post, we will explore the new features, improvements, and the benefits MongoDB 8.0 brings to the table, making it a game-changer in the world of database management.

To experience the power of MongoDB 8.0, get started with a free trial today and reserve your spot in our upcoming MongoDB 8.0 Deep Dive webinar to explore how this release can transform your database management.

Ready to transform your database strategy?
👉 Start Your Free Trial
👉 Reserve Your Webinar Seat

# Why MongoDB 8.0 Matters
MongoDB has consistently been at the forefront of database innovation, and version 8.0 is no exception. This latest iteration introduces a host of new features and improvements, all geared towards ensuring seamless integration, efficient data management, and enhanced security. Whether you are a developer seeking to streamline your application deployment or an enterprise aiming to optimize your data-driven strategies, MongoDB 8.0 has something valuable to offer.

Performance Gains You Can't Ignore
With MongoDB 8.0, you can expect substantial performance improvements compared to version 7.0, including:

36% faster read throughput
56% faster bulk writes
20% faster concurrent writes during replication
200% faster time-series data handling with reduced resource usage and costs

MongoDB 8.0 isn't just an upgrade - it's a leap forward. This release redefines what’s possible. Combine these gains with Alibaba Cloud's battle-tested infrastructure, and you get a database solution built for speed, security, and seamless scalability.

What's New in MongoDB 8.0?

Let's dive into the flagship features that make MongoDB 8.0 a powerful tool for developers and enterprises:

1. Optimal Performance
Performance is a critical factor in any database solution, and MongoDB 8.0 raises the bar with significant enhancements. Thanks to improved indexing capabilities and optimized query processing, users can experience faster read and write operations, even under heavy workloads.

**2. Faster Scalability
For sharded clusters, the introduction of advanced sharding mechanisms ensures faster and more cost-efficient horizontal scaling as your data grows, maintaining high performance levels without compromising on speed.

In MongoDB 8.0, data can be distributed across shards 50x faster for up to 50% lower cost compared to MongoDB 7.0. Faster resharding is now possible for adding or removing sharding, without impacting the workload compared to previous methods. For instance, resharding a 1TB cluster can now be completed in hours rather than days.

3. Enhanced Security Features
In today's digital landscape, data security is paramount. MongoDB 8.0 introduces comprehensive security enhancements, including finer-grained access controls and robust encryption methods. With support for role-based access controls and advanced auditing capabilities, you can ensure that your data remains protected against unauthorized access, while maintaining compliance with industry standards and regulations.

For example, in MongoDB 8.0, Queryable Encryption supports range queries on encrypted fields using the $lt, $lte, $gt, and $gte operators.

Queryable Encryption feature was first officially introduced since MongoDB 7.0 to allow running expressive queries on fully encrypted data - without decrypting it server-side. This “zero-trust” model ensures sensitive data (e.g., PII, financial records) remains encrypted in transit, at rest, and during processing.

4. Advanced Setups for Better Stability
In MongoDB 8.0, you can define a default timeout (maxTimeMS) for all read operations on your cluster. This setting helps protect your cluster from resource-intensive queries due to suboptimal or unindexed queries.

db.adminCommans( { setClusterParameter: { defaultMaxTimeMS: { readOperations: 30000} }}}

Benefits for Enterprises

1. Cost Efficiency and Resource Optimization
MongoDB 8.0’s enhanced performance and automation capabilities translate into cost savings for enterprises. By optimizing resource usage and reducing operational overhead, businesses can allocate their budgets more effectively, allowing for investment in other strategic areas.

2. Robust Security and Compliance
With advanced security features, enterprises can ensure that their data management strategies comply with industry regulations, thereby avoiding potential fines and penalties. The comprehensive security measures provide peace of mind, knowing that sensitive information is safeguarded against breaches.

3. Scalability to Support Growth
As enterprises grow, their data needs grow exponentially. MongoDB 8.0’s scalability features ensure that businesses can support this growth without the need for frequent infrastructure changes or costly upgrades.
Explore these features with a free trial on Alibaba Cloud and see the difference MongoDB 8.0 can make for your business.

# Why ApsaraDB for MongoDB?
ApsaraDB for MongoDB isn't just a hosted database - it's a fully managed service designed for scale, security, and simplicity.
Alibaba Cloud ApsaraDB for MongoDB offers a fully-managed database service that takes the hassle out of database management. By hosting MongoDB 8.0 on ApsaraDB, users can leverage the power of MongoDB while enjoying the benefits of Alibaba Cloud's robust infrastructure and advanced cloud technologies.

Seamless Integration and High Availability
ApsaraDB for MongoDB is designed for high availability and seamless integration, ensuring that your applications remain operational and accessible at all times. With Alibaba Cloud’s global network and data centers, you can deploy your applications closer to your users, reducing latency and improving user experience. Besides, it enables you to seamlessly integrate with other Alibaba Cloud services including Object Storage Service (OSS), Simple Log Service (SLS) and more.

Effortless Management and Monitoring
Alibaba Cloud's automated management tools simplify routine tasks such as backups, monitoring, and scaling. This frees up valuable time for IT teams, allowing them to focus on strategic initiatives that drive business growth.

Tailored Solutions for Every Industry
Whether you're in gaming, finance, healthcare, or e-commerce, Alibaba Cloud ApsaraDB for MongoDB offers tailored solutions to meet the unique needs of your industry. With the flexibility and robustness of MongoDB 8.0 backed by Alibaba Cloud’s infrastructure, enterprises can achieve their business objectives without constraints.

*Comprehensive Support and Resources *
Alibaba Cloud offers extensive support and resources to help users get the most out of MongoDB 8.0. From documentation and tutorials to technical support and consulting services, you can access the expertise needed to maximize the value of your database solution.

The Future is Here

The debut of MongoDB 8.0 on Alibaba Cloud ApsaraDB for MongoDB represents a significant advancement for developers and enterprises alike. With improved performance, enhanced security, and a range of new features designed for modern applications, MongoDB 8.0 is poised to significantly enhance your database management experience.

We invite you to take advantage of this exciting update and explore the numerous benefits it can bring to your development projects and business operations.

Don't miss out - start your free trial today and see firsthand how this cutting-edge release can transform your applications. Plus, join our MongoDB 8.0 Deep Dive webinar in June for an in-depth exploration of its capabilities.

[Boost]

mrboogiej — Mon, 03 Mar 2025 06:35:56 +0000

Alibaba Cloud’s PolarDB Just Shattered the TPC-C World Record: 2.055B tpmC at $0.11/tpmC

mrboogiej ・ Mar 3

#alibabacloud #polardb #tpcc #databasebenchmark

Alibaba Cloud’s PolarDB Just Shattered the TPC-C World Record: 2.055B tpmC at $0.11/tpmC

mrboogiej — Mon, 03 Mar 2025 06:26:14 +0000

Recently, Alibaba Cloud announced a new milestone: PolarDB contributed record-breaking performance and cost-efficiency in TPC-C benchmark and recognized as the world's No. 1 OLTP database.

[References]

Let’s cut through the hype: When we say PolarDB achieved 2.055 billion transactions per minute (tpmC) with $0.11 per transaction (0.8 CNY/tpmC) in the TPC-C benchmark, what does this actually mean for developers?

Why TPC-C Matters (And Why Most Vendors Avoid It)
TPC-C isn’t another synthetic benchmark. It’s the database equivalent of an Ironman triathlon:
● Long-duration endurance test with ≤2% tpmC fluctuation
● 100% data correctness under hardware failure simulations
● Mixed workload: New orders (45%), payments (43%), deliveries (4%), etc.
● Atomicity checks: Rollback transactions in the event of a failure to verify consistency
The previous record holder (2023) had a performance of 814M tpmC. PolarDB’s 2.055B tpmC isn’t just faster - it’s a fundamental architectural shift.

The Engineering Breakthroughs

1. Killing Sharding Headaches

PolarDB’s Limitless cluster supports multiple RW nodes (Multi-Master) and RO nodes with near-linear performance growth. How?

● PolarTrans: Distributed transaction layer with 25μs latency via RDMA (Remote Direct Memory Access)
● ePQ: Elastic parallel query across CPU cores to enhance query performance
● SmartSSD Offload: Optimizations that help reduce Write-Ahead Logging (WAL) flush latency significantly

2. Cloud-Native, Yet Hardware-Optimized

PolarDB is designed for cloud environments while maximizing the potential of x86 architecture:

● Intel® Xeon® Processors: Utilizing advanced technologies like hardware profile-guided optimization (HW-PGO) to enhance instruction per cycle (IPC) on OLTP hotspots
● Persistent Memory (AliSCM): Capable of achieving millions of IOPS for redo log operations, significantly improving performance.
● Cost Efficiency: Database kernel optimizations to maximize computing performance per CPU core, 18K tpmC/core vs. 10K in previous record holder

Real-World Translation
This isn’t just about benchmarketing. PolarDB’s architecture solves actual pain points:
● Dynamic Scaling: From 1 to 2K nodes without downtime
● MySQL Compatibility: 100% syntax coverage
● Cost Savings: Reduce costs owing to optimized tpmC per core

Why This Matters for Developers
TPC-C is the ultimate stress test for OLTP database systems. If your database can’t pass this, your next production outage is just waiting to happen. PolarDB’s record proves that:
● Horizontal scaling can beat vertical scaling
● Cloud-native != vendor lock-in

Try It Yourself
We’re not hiding behind NDA walls:
● Tear Apart Our Code: PolarDB has an open-source version with Apache 2.0 license. Check out PolarDB on Github.
● Reproduce the Test: Check out the raw TPC-C audit report or read PolarDB performance whitepapers.
● Free Tier: Join the PolarDB Always Free Program to learn or experience PolarDB for free.

Read the blog to find out the story behind, or join the PolarDB Always Free Program and be part of PolarDB.

Discover the Latest in ApsaraDB for MongoDB 7.0 and How It Can Benefit Your Business

mrboogiej — Mon, 15 Apr 2024 14:52:39 +0000

By Zhongli, Feiyou and Summer
Originally posted at: https://www.alibabacloud.com/blog/discover-the-latest-in-apsaradb-for-mongodb-7-0-and-its-advantages-for-your-business_601037

Alibaba Cloud ApsaraDB for MongoDB 7.0 has arrived with a suite of innovative features and notable improvements, designed to enhance performance, bolster data management capabilities, and provide developers with a more extensive and flexible set of tools. Whether it’s managing vast datasets, performing real-time analytics, or building high-performance applications, Alibaba Cloud ApsaraDB for MongoDB 7.0 stands out as a choice worth looking forward to and trusting.

Why MongoDB 7.0?

1. Enhanced Functionality
Shard Key Analyzer: Starting from version 7.0, MongoDB supports analyzing the rationality of collection shard keys based on the results of sampled queries, which can help you better design your schema and shard keys, and make more efficient use of the sharding architecture.

ChangeStream for Large Change Events: The new $changeStreamSplitLargeEvent operator, introduced in version 7.0, enables splitting of change events exceeding 16 MB. This solves past limitations where changeStream couldn't support large change events.

2. Stronger Data Security
Queryable Encryption: Queryable Encryption is previously a preview feature in MongoDB 6.0, and now be ready for prime time in MongoDB 7.0, offering you an unparalleled level of protection for your most sensitive information. With this groundbreaking technology, your data stays encrypted at every stage of its lifecycle and can be decrypted only on the client-side without the server having knowledge of the data it's processing. This feature offers robust, comprehensive security and effectively counters the risks of data breaches.

Figure: Sample Flow of Queryable Encryption Operations
Source: https://www.mongodb.com/blog/post/mongodb-releases-queryable-encryption-preview

User Roles System Variable: The USER_ROLES system variable in MongoDB 7.0 enables the retrieval of the current user's roles, providing a mechanism for role-based access control directly within the database. This feature is particularly beneficial for scenarios where documents contain sensitive information that should be accessible only to users with specific roles.

3. Greater Reliability and Stability
Metadata Consistency Checker: In previous versions of MongoDB, there were potential issues with inconsistencies in routing data or indexes. The MongoDB 7.0 release introduces the checkMetadataConsistency command, which checks for inconsistencies in metadata across different shards. Incorporate this inspection into your routine operations and maintenance tasks to proactively and promptly detect potential risks of metadata/index inconsistencies following maintenance routines or events such as out-of-memory errors or failovers.

Dynamic Concurrent Storage Engine Transactions(Read/Write Tickets): MongoDB 7.0 brings an exciting update that makes working with databases safer and more efficient than ever. The introduction of the Dynamic WiredTiger Tickets in MongoDB 7.0 automatically manages how many concurrent transactions (tickets) can happen at once within the WiredTiger storage engine, with the default value set at 128 tickets, optimizing performance. We strongly recommend adhering to this configuration for the time being. This dynamic control helps prevent the buildup of excessive requests that previously led to database slowdowns. By reducing the likelihood of these "avalanche" scenarios, MongoDB 7.0 ensures smoother operation, safeguarding your business from potential setbacks and maintaining continuous, reliable service for your customers.

Why Alibaba Cloud's MongoDB 7.0?

Since its exclusive debut of version 5.0 in May 2021, Alibaba Cloud ApsaraDB for MongoDB service has consistently kept pace with MongoDB Inc.'s release cadence, dedicated to offering developers the cutting-edge experience of the latest version through its cloud services.

Futhermore, benefitting from its consistent embrace of cloud-native strategies, the exceptional elasticity, backup and recovery capabilities, as well as intelligent operations and maintenance - a hallmark of cloud-native features - ensure an enhanced performance, stability and flexibility.

1. Ultimate Elasticity
Computing and storage is decoupled in ApsaraDB for MongoDB, addressing the issue of resource isolation and allowing for storage massive data. In addition, the independent and rapid scaling of computing and storage can be achievable within minutes. This presents minimal impact, higher speed, and greater flexibility, thereby allowing to swiftly adapt to the changing needs of business.

2. Rapid Recovery Capability
Snapshot-based recovery, can now process 500GB of data in just minutes, offers a 6X increase in speed compared to traditional physical backup recovery methods.

The most recent enhancements include support for database and table-level restoration, which streamlines the process by enabling swift recovery of specific table data.

The diverse rapid backup and recovery options are available for you to choose from, fulfilling personalized backup and recovery needs in various scenarios.

3. Intelligent Operations and Maintenance
You can also take advantage of features such as slow logs, space analysis, and session management with CloudDBA - an intelligent operations and maintenance tool provided by ApsaraDB for MongoDB. CloudDBA simplifies your database management process by enabling you to quickly identify and resolve performance, clustering, and data-related issues.

To explore more about the new features and optimizations of ApsaraDB for MongoDB 7.0, you can check out the New features of MongoDB 7.0. These updates not only boost MongoDB's performance and security but also offer users a more convenient and efficient database management experience, as well as support for more complex application scenarios.

Explore the latest ApsaraDB for MongoDB with its trending scenario solution kit today!

Real-Time Cross-Region Database Synchronization Solution on Alibaba Cloud

mrboogiej — Wed, 24 May 2023 01:58:01 +0000

Overview
In today's digital world, companies often need to transfer or sync data across borders for different reasons, including collaborating with international partners, developing new local markets for business globalization strategy, or storing information in overseas servers for disaster recovery. There are many methods for cross-border data transfer (such as public networks and VPN). No matter what approach you choose, you cannot turn a blind eye to the huge costs and the risk of cyberattacks, which can lead to data breaches, loss of confidential information, and reputational damage for companies.

The article explains the best practice of using a cutting-edge product combo to help users transfer data in a safe, reliable, and cost-effective way.

Who Should Read This
You should follow this best practice if you want to do any of the following:

Perform cross-border database migration and synchronization
Build disaster recovery (DR) ability for business-critical databases

Topology & Workflow
The diagram below shows the resources and topology used in this best practice. It is performed based on the following workflow:

Creating secure network conditions for data transfer through Cloud Enterprise Network (CEN)
Configuring synchronization tasks between databases with Data Transmission Service (DTS)
Verifying data and performing performance evaluation

About CEN
Cloud Enterprise Network (CEN) is a highly available network built on the global private network of Alibaba Cloud. CEN uses transit routers to establish inter-region connections between virtual private clouds (VPCs). This enables VPCs to communicate with data centers and builds flexible, stable, enterprise-class networks on the cloud.

About DTS
Data Transmission Service (DTS) is a real-time data streaming service. DTS supports data transmission between data sources (such as relational, NoSQL, and online analytical processing (OLAP) databases). DTS provides data synchronization, data migration, change tracking, data integration, and data processing features. This enables you to manage data within a secure, scalable, and high-availability architecture.

Read the rest part of the article:
https://www.alibabacloud.com/blog/best-practice-cross-border-database-synchronization_599989

✨ Database Free Trial:
https://www.alibabacloud.com/product/databases#J_2463051000

What I Think Really Matters for Personal Growth in Software Development | My Career Path From Junior Engineer to Expert

mrboogiej — Thu, 16 Feb 2023 07:22:42 +0000

By Øystein Grøvlen

My name is Øystein Grøvlen, I was working as a Senior Staff Engineer in the MySQL Optimizer & SQL group of the PolarDB team at Alibaba for years. I am originally from Norway, but moved to China to work for Alibaba in 2018. After living one year in Hangzhou, I relocated to Alibaba's office in Sunnyvale, California.

My journey as a software developer started as an exchange student in the US where I was introduced to programming in BASIC on APPLE II computers. I found it very satisfying to be able to create my own programs in order to solve different kind of problems, and this inspired me to study computer science at the Norwegian Institute of Technology. During my studies, I found databases and information retrieval particularly interesting, and I decided to pursue a PhD in that area. I came in contact with the research department at the Norwegian Telecom, and I ended up working part-time on their research project, ClustRa, while working on my PhD on Compensation-Based Query Processing.

After my PhD, I started working at a start-up that was set up to commercialize the ClustRa database system. ClustRa was a highly available database system targeted at Telecom operations. The architecture of Clustra was pretty similar to MySQL Cluster, which many of you may have heard about. The focus of our work was on transactions, partitioning, replication, fail-over, and recovery. It was a fun time, solving a lot of interesting problems. Unfortunately, we ran out of funding when the dot-com bubble burst, but we were lucky that Sun Microsystems decided to pick up the pieces. At Sun, I continued to work on Clustra for while, before starting to work on Derby, the open-source version of the Cloudscape, a database implemented in Java. When Sun later bought MySQL, I switch to work on MySQL, and I got the opportunity to work in the Optimizer team. Sun was later bought by Oracle, and I worked on MySQL at Sun/Oracle for 10 years before joining Alibaba.

I find it really interesting to work on query optimization and query processing. My favorite part is investigating how we can get queries to run faster. POLARDB is based on MySQL code, so I can use my knowledge about the MySQL optimizer to make POLARDB a better product. What I find particularly rewarding about working for the POLARDB team, is that Alibaba is willing to put a lot of resources into POLARDB. We have a large group of people working on improving the product, and I think it is amazing what we have been able to do while I have been here. Most of my time I have spent on the project to support parallel query processing; while MySQL can only use one thread to execute a query, POLARDB can partition the query execution across multiple parallel threads.

I have been asked to give some advice to other developers on what it takes to make a career as a senior architect. I think there are many different paths to success, and some may claim that part of it may be the luck of being at the right place at the right time. However, based on my experience, I will discuss a few aspects that I feel has been essential to prepare myself for the role of software architect.

Make deep dives

I think the only way to learn how a software system works, is to deep dive into the code. Do not just assume that you understand how the code is working, verify it by tracing the execution or stepping through the code with a debugger.

I have met quite a few developers that when faced with a bug, instead of getting a good understanding of how the code works, try to take short-cuts based on trial and error. They may succeed in fixing the bug, but they have learned very little about how the code works. Many times this approach also leads to bug fixes that seems to solve the problem, but the underlying problem may still exist. Do not just be satisfied when all your tests succeed, verify by trace/debugger that it runs as expected! It may take a bit longer to get the job done the first time, but you will get the reward later when you are assigned another task in the same area.

Optimizer Trace is a great tool to learn about the MySQL Query Optimizer

Learn by example

People are different. I find it easier to learn new code by following the execution of some specific examples, and then generalize from that. Other people may be successful in understanding the code just from reading it, but I guess my mental capacity is not at that level.

One of my first tasks at ClustRa was to make transaction rollback work. Much of the code was already prepared for the task, but there was still some missing pieces. By carefully tracing the execution of a transaction, it did not take me long to identify the missing pieces and make it work. I think it would have taken me much longer if I were to identify what was missing just by reading the code.

Be not afraid to ask

When you stumbled on a problem, do not be afraid to ask your co-workers. Share your understanding of the problem and ask for their advice. Most developers are more than happy to share what they know. However, make sure you have put some effort into understanding the problem before you ask. Otherwise, your co-workers may feel you are just trying to make them do your job.

Share your wisdom

Share your knowledge with your co-workers. Welcome their questions; you will often learn something yourself in the process.

Also, write about your work in articles and blog posts, and seek for opportunities to talk about it in public. This is a good way to make people outside your team or company aware of you and your work.

Understand your users

I feel many developers put too little effort into understanding the needs of their users. Often the developer prefer solutions that are either more straight-foward to implement, or more technically "interesting", over solving the real problem. Ask yourself: "How will this be used?", "Will the chosen interface be practical to the users?", and so on.

Before starting the design, it is a good idea to specify a few uses cases that describes how this new feature will be used, and what problem it will solve.

Stay around

It takes time to become an expert on a technology, a product, or a code base. It took me several years before I could consider myself an expert on the MySQL query optimizer. While it is certainly good to have a wide experience, I think that if you change jobs or technologies too often, you will miss the opportunity to get the deep insights that will be necessary to establish yourself as an expert. In other words, be patient, and set long-term goals for yourself!

Learn more about PolarDB and its architecture:
https://www.youtube.com/watch?v=K87Ey4vqf5k&t=11s
https://www.youtube.com/playlist?list=PL54EFTJJZrwhqbWk5lALG2SpZn5OkXCQ8

PolarDB Global Hackathon 2023_Win Up to $10K USD as Prizes

mrboogiej — Wed, 01 Feb 2023 03:29:10 +0000

PolarDB Global Hackathon 2023 is an open-theme contest organized by Alibaba Cloud for developers worldwide, aiming to inspire creativity and passion for cloud-native technologies.

Participates are required to build innovative and valuable applications using at least Alibaba Cloud featured product PolarDB, a cloud-native relational database that is fully compatible with MySQL and PostgreSQL.

Benefits

Winners will get up to 10 grands US dollar cash as bonuses. (wow... that's so generous, who can be the lucky one?)

Schedule

Start: Jan. 10th 2023
Close: Feb. 28th, EST 6PM
Announce: Mid-March 2023

Learn More & Join

👉https://github.com/ApsaraDB/PolarDB-Hackathon-2023
👉https://www.alibabacloud.com/developer/polardb-global-hackathon-2023

Build your team and join now, unleash creativity and possibility.

How To Create User Account With Privileges Second Only to The 'root' Account in RDS MariaDB?

mrboogiej — Sat, 07 May 2022 10:37:51 +0000

Account Privileges:

①Privileged Account > ②Standard Account(DML+DDL) > ③Standard Account(DDL) > ④Standard Account(DML) > ⑤Standard Account(Read-Only)

① How to create privileged account?

Create on the console.

Or you can create via openAPI, we will discuss in another article.

② How to create standard account with DDL+DML privileges?

See example as below:
The given example will create a user named 'normal3' with DDL and DML privileges on DB 'test3' and it is allowed to access from anywhere.

create user IF NOT EXISTS normal3@'%' identified by 'Passw@rd!';
show grants for normal3;
_// The user will only have USAGE privilege after created. So you would need to grant process, replication slave and replication client on *.* to new user account._
GRANT PROCESS, REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'normal3'@'%';
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, EVENT, TRIGGER ON `test3`.* TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`help_keyword` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`time_zone_name` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`help_category` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`help_relation` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`time_zone_leap_second` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`slow_log` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`time_zone_transition_type` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`func` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`general_log` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`proc` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`time_zone` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`help_topic` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`time_zone_transition` TO 'normal3'@'%';
GRANT SELECT ON `mysql`.`event` TO 'normal3'@'%';

③ How to create standard account with DDL privileges?

create user IF NOT EXISTS normal6@'%' identified by 'Passw@rd!';
GRANT PROCESS, REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'normal6'@'%';
GRANT CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE ON `sampledb`.* TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`help_keyword` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`time_zone_name` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`help_category` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`help_relation` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`time_zone_leap_second` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`slow_log` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`time_zone_transition_type` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`func` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`general_log` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`proc` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`time_zone` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`help_topic` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`time_zone_transition` TO 'normal6'@'%';
GRANT SELECT ON `mysql`.`event` TO 'normal6'@'%';

④ How to create standard account with DML privileges?

create user IF NOT EXISTS normal5@'%' identified by 'Passw@rd!';
GRANT PROCESS, REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'normal5'@'%';
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, SHOW VIEW, EVENT, TRIGGER ON `sampledb`.* TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`help_keyword` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`time_zone_name` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`help_category` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`help_relation` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`time_zone_leap_second` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`slow_log` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`time_zone_transition_type` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`func` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`general_log` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`proc` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`time_zone` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`help_topic` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`time_zone_transition` TO 'normal5'@'%';
GRANT SELECT ON `mysql`.`event` TO 'normal5'@'%';

⑤ How to create standard account with Read-Only privileges?

create user IF NOT EXISTS normal4@'%' identified by 'Passw@rd!';
GRANT PROCESS, REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'normal4'@'%';
GRANT SELECT, LOCK TABLES, SHOW VIEW ON `test4`.* TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`help_keyword` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`time_zone_name` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`help_category` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`help_relation` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`time_zone_leap_second` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`slow_log` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`time_zone_transition_type` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`func` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`general_log` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`proc` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`time_zone` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`help_topic` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`time_zone_transition` TO 'normal4'@'%';
GRANT SELECT ON `mysql`.`event` TO 'normal4'@'%';

PolarDB Always Free Program: More Regions, More Options

mrboogiej — Fri, 29 Apr 2022 04:05:27 +0000

Good news for all!!!

More regions are available for PolarDB Always Free Program, you can claim PolarDB on any of the followings, free of charge.

「
Australia(Sydney), China(Hong Kong), Germany(Frankfurt), Japan(Tokyo), Singapore, UK(London)
」

Wanna know how cloud native database services can help you? Apply now on our website👇
https://www.alibabacloud.com/product/polardb?#J_5764451150

Alibaba Cloud Infrastructure Guide for AWS Professionals

mrboogiej — Fri, 01 Apr 2022 09:43:16 +0000

Please find full read at:
https://resource.alibabacloud.com/whitepaper/alibaba-cloud-infrastructure-guide-for-aws-professionals_4651?key=

Database Service Highlight

DATA WAREHOUSE
NOSQL DATABASE
RELATIONAL DATABASE
UTILITY & TOOLS

Deepen Your Cloud Skills for Free | Digital Talent x Alibaba Cloud 2022 | Indonesia

mrboogiej — Fri, 11 Mar 2022 09:47:09 +0000

【Free Cloud Skill Courses For Indonesian Users】

Good news for users in Indonesia, you are free to go with Digital Talent Scholarship Program which is initiated by Indonesia Ministry of Communications and Informatics, and it is sponsored by Alibaba Cloud Academy.

Take your chance to join in and get FREE access to all Apsara Clouder courses, certifications and labs!

Join Now:
https://id.alibabacloud.com/en/campaign/digital-talent-2022-database

What are the region code and Availability Zone (AZ) code of Alibaba Cloud ApsaraDB?

mrboogiej — Fri, 04 Mar 2022 09:46:00 +0000

When you try to manage cloud resources through automation methods like python scripts or Terraform scripts, you must know where to launch your resources before creation or figure out where your resource resides in before doing any changes.

So for changing resource configurations, you can execute operations with instance ID which you can easily find on the console. But for resource creation, it might be not that easy to get code (or we say ID) that stands a specific region or a specific Availability Zone (AZ).

Here is what you may need.

RegionID and Availability Zone (AZ) ID for RDS

Select via OpenAPI of DescribeRegions: https://next.api.alibabacloud.com/api/Rds/2014-08-15/DescribeRegions?params={}&tab=DEBUG&accounttraceid=a9a7db9c10e04bdbb255d39794a85fc3ayze

{
  "RequestId": "94018C0D-043C-366F-AE8F-8B6BF3A7655A",
  "Regions": {
    "RDSRegion": [
      {
        "ZoneName": "Hangzhou Zone H",
        "ZoneId": "cn-hangzhou-h",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "East China 1 MZone10 H+I",
        "ZoneId": "cn-hangzhou-MAZ10(h,i)",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "East China 1 MZone8 F+G",
        "ZoneId": "cn-hangzhou-MAZ8(f,g)",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "Hangzhou Zone I",
        "ZoneId": "cn-hangzhou-i",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "East China 1 MZone9 G+H",
        "ZoneId": "cn-hangzhou-MAZ9(g,h)",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "Hangzhou Zone J",
        "ZoneId": "cn-hangzhou-j",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "Hangzhou Zone B",
        "ZoneId": "cn-hangzhou-b",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "Hangzhou Zone D",
        "ZoneId": "cn-hangzhou-d",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "Hangzhou Zone E",
        "ZoneId": "cn-hangzhou-e",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "East China 1 MZone6 B+F",
        "ZoneId": "cn-hangzhou-MAZ6(b,f)",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "Hangzhou Zone F",
        "ZoneId": "cn-hangzhou-f",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "East China 1 MZone5 B+E+F",
        "ZoneId": "cn-hangzhou-MAZ5(b,e,f)",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "East China 1 MZone4 B+D+F",
        "ZoneId": "cn-hangzhou-MAZ4(b,d,f)",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "Hangzhou Zone G",
        "ZoneId": "cn-hangzhou-g",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "Hangzhou Zone K",
        "ZoneId": "cn-hangzhou-k",
        "RegionId": "cn-hangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hangzhou)"
      },
      {
        "ZoneName": "Shanghai Zone M",
        "ZoneId": "cn-shanghai-m",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "Shanghai Zone N",
        "ZoneId": "cn-shanghai-n",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "China East 2 MZone4 E+F",
        "ZoneId": "cn-shanghai-MAZ4(e,f)",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "Shanghai Zone E",
        "ZoneId": "cn-shanghai-e",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "Shanghai Zone G",
        "ZoneId": "cn-shanghai-g",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "China East 2 MZone5 F+G",
        "ZoneId": "cn-shanghai-MAZ5(f,g)",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "Shanghai Zone F",
        "ZoneId": "cn-shanghai-f",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "Shanghai Zone A",
        "ZoneId": "cn-shanghai-a",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "Shanghai Zone B",
        "ZoneId": "cn-shanghai-b",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "East China 2 MZone1 B+C",
        "ZoneId": "cn-shanghai-MAZ1(b,c)",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "East China 2 MZone2 B+D",
        "ZoneId": "cn-shanghai-MAZ2(b,d)",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "East China 2 MZone3 A+B+D",
        "ZoneId": "cn-shanghai-MAZ3(a,b,d)",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "Shanghai Zone L",
        "ZoneId": "cn-shanghai-l",
        "RegionId": "cn-shanghai",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shanghai)"
      },
      {
        "ZoneName": "Qingdao Zone B",
        "ZoneId": "cn-qingdao-b",
        "RegionId": "cn-qingdao",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Qingdao)"
      },
      {
        "ZoneName": "Qingdao Zone C",
        "ZoneId": "cn-qingdao-c",
        "RegionId": "cn-qingdao",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Qingdao)"
      },
      {
        "ZoneName": "Beijing MZone7 G+H",
        "ZoneId": "cn-beijing-MAZ7(g,h)",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "China North 2 MZone4 F+G",
        "ZoneId": "cn-beijing-MAZ4(f,g)",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "China North 2 MZone3 C+E",
        "ZoneId": "cn-beijing-MAZ3(c,e)",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "Beijing Zone H",
        "ZoneId": "cn-beijing-h",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "Beijing Zone L",
        "ZoneId": "cn-beijing-l",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "Beijing Zone F",
        "ZoneId": "cn-beijing-f",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "Beijing Zone G",
        "ZoneId": "cn-beijing-g",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "China North 2 MZone5 A+C",
        "ZoneId": "cn-beijing-MAZ5(a,c)",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "Beijing Zone I",
        "ZoneId": "cn-beijing-i",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "Beijing Zone A",
        "ZoneId": "cn-beijing-a",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "Beijing Zone B",
        "ZoneId": "cn-beijing-b",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "Beijing Zone C",
        "ZoneId": "cn-beijing-c",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "Beijing Zone D",
        "ZoneId": "cn-beijing-d",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "North China 2 MZone2 A+C+D",
        "ZoneId": "cn-beijing-MAZ2(a,c,d)",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "Beijing Zone E",
        "ZoneId": "cn-beijing-e",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "Beijing Zone K",
        "ZoneId": "cn-beijing-k",
        "RegionId": "cn-beijing",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Beijing)"
      },
      {
        "ZoneName": "China North 3 MZone1 A+B",
        "ZoneId": "cn-zhangjiakou-MAZ1(a,b)",
        "RegionId": "cn-zhangjiakou",
        "RegionEndpoint": "rds.cn-zhangjiakou.aliyuncs.com",
        "LocalName": "China (Zhangjiakou)"
      },
      {
        "ZoneName": "Zhangjiakou Zone C",
        "ZoneId": "cn-zhangjiakou-c",
        "RegionId": "cn-zhangjiakou",
        "RegionEndpoint": "rds.cn-zhangjiakou.aliyuncs.com",
        "LocalName": "China (Zhangjiakou)"
      },
      {
        "ZoneName": "Zhangjiakou Zone B",
        "ZoneId": "cn-zhangjiakou-b",
        "RegionId": "cn-zhangjiakou",
        "RegionEndpoint": "rds.cn-zhangjiakou.aliyuncs.com",
        "LocalName": "China (Zhangjiakou)"
      },
      {
        "ZoneName": "Zhangjiakou Zone A",
        "ZoneId": "cn-zhangjiakou-a",
        "RegionId": "cn-zhangjiakou",
        "RegionEndpoint": "rds.cn-zhangjiakou.aliyuncs.com",
        "LocalName": "China (Zhangjiakou)"
      },
      {
        "ZoneName": "China North 5 MZone1 A+B",
        "ZoneId": "cn-huhehaote-MAZ1(a,b)",
        "RegionId": "cn-huhehaote",
        "RegionEndpoint": "rds.cn-huhehaote.aliyuncs.com",
        "LocalName": "China (Hohhot)"
      },
      {
        "ZoneName": "Hohhot Zone B",
        "ZoneId": "cn-huhehaote-b",
        "RegionId": "cn-huhehaote",
        "RegionEndpoint": "rds.cn-huhehaote.aliyuncs.com",
        "LocalName": "China (Hohhot)"
      },
      {
        "ZoneName": "Hohhot Zone A",
        "ZoneId": "cn-huhehaote-a",
        "RegionId": "cn-huhehaote",
        "RegionEndpoint": "rds.cn-huhehaote.aliyuncs.com",
        "LocalName": "China (Hohhot)"
      },
      {
        "ZoneName": "Ulanqab Zone A",
        "ZoneId": "cn-wulanchabu-a",
        "RegionId": "cn-wulanchabu",
        "RegionEndpoint": "rds.cn-wulanchabu.aliyuncs.com",
        "LocalName": "China (Ulanqab)"
      },
      {
        "ZoneName": "Ulanqab Zone C",
        "ZoneId": "cn-wulanchabu-c",
        "RegionId": "cn-wulanchabu",
        "RegionEndpoint": "rds.cn-wulanchabu.aliyuncs.com",
        "LocalName": "China (Ulanqab)"
      },
      {
        "ZoneName": "Ulanqab Zone B",
        "ZoneId": "cn-wulanchabu-b",
        "RegionId": "cn-wulanchabu",
        "RegionEndpoint": "rds.cn-wulanchabu.aliyuncs.com",
        "LocalName": "China (Ulanqab)"
      },
      {
        "ZoneName": "Shenzhen Zone F",
        "ZoneId": "cn-shenzhen-f",
        "RegionId": "cn-shenzhen",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shenzhen)"
      },
      {
        "ZoneName": "Shenzhen Zone D",
        "ZoneId": "cn-shenzhen-d",
        "RegionId": "cn-shenzhen",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shenzhen)"
      },
      {
        "ZoneName": "Shenzhen Zone E",
        "ZoneId": "cn-shenzhen-e",
        "RegionId": "cn-shenzhen",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shenzhen)"
      },
      {
        "ZoneName": "South China 1 MZone D+E",
        "ZoneId": "cn-shenzhen-MAZ5(d,e)",
        "RegionId": "cn-shenzhen",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shenzhen)"
      },
      {
        "ZoneName": "Shenzhen Zone A",
        "ZoneId": "cn-shenzhen-a",
        "RegionId": "cn-shenzhen",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shenzhen)"
      },
      {
        "ZoneName": "Shenzhen Zone B",
        "ZoneId": "cn-shenzhen-b",
        "RegionId": "cn-shenzhen",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shenzhen)"
      },
      {
        "ZoneName": "South China 1 MZone1 A+B",
        "ZoneId": "cn-shenzhen-MAZ1(a,b)",
        "RegionId": "cn-shenzhen",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shenzhen)"
      },
      {
        "ZoneName": "Shenzhen Zone C",
        "ZoneId": "cn-shenzhen-c",
        "RegionId": "cn-shenzhen",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shenzhen)"
      },
      {
        "ZoneName": "South China 1 MZone2 B+C",
        "ZoneId": "cn-shenzhen-MAZ2(b,c)",
        "RegionId": "cn-shenzhen",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Shenzhen)"
      },
      {
        "ZoneName": "Heyuan Zone B",
        "ZoneId": "cn-heyuan-b",
        "RegionId": "cn-heyuan",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Heyuan)"
      },
      {
        "ZoneName": "Heyuan MZone1 A+B",
        "ZoneId": "cn-heyuan-MAZ1(a,b)",
        "RegionId": "cn-heyuan",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Heyuan)"
      },
      {
        "ZoneName": "Heyuan Zone A",
        "ZoneId": "cn-heyuan-a",
        "RegionId": "cn-heyuan",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Heyuan)"
      },
      {
        "ZoneName": "Guangzhou Zone A",
        "ZoneId": "cn-guangzhou-a",
        "RegionId": "cn-guangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Guangzhou)"
      },
      {
        "ZoneName": "Guangzhou Zone B",
        "ZoneId": "cn-guangzhou-b",
        "RegionId": "cn-guangzhou",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Guangzhou)"
      },
      {
        "ZoneName": "Chengdu Zone A",
        "ZoneId": "cn-chengdu-a",
        "RegionId": "cn-chengdu",
        "RegionEndpoint": "rds.cn-chengdu.aliyuncs.com",
        "LocalName": "China (Chengdu)"
      },
      {
        "ZoneName": "Chengdu Zone B",
        "ZoneId": "cn-chengdu-b",
        "RegionId": "cn-chengdu",
        "RegionEndpoint": "rds.cn-chengdu.aliyuncs.com",
        "LocalName": "China (Chengdu)"
      },
      {
        "ZoneName": "Hong Kong Zone D",
        "ZoneId": "cn-hongkong-d",
        "RegionId": "cn-hongkong",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hong Kong)"
      },
      {
        "ZoneName": "Hong Kong Zone B",
        "ZoneId": "cn-hongkong-b",
        "RegionId": "cn-hongkong",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hong Kong)"
      },
      {
        "ZoneName": "Hong Kong Zone C",
        "ZoneId": "cn-hongkong-c",
        "RegionId": "cn-hongkong",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hong Kong)"
      },
      {
        "ZoneName": "Hong Kong MZone1 B+C",
        "ZoneId": "cn-hongkong-MAZ1(b,c)",
        "RegionId": "cn-hongkong",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "China (Hong Kong)"
      },
      {
        "ZoneName": "Singapore Zone C",
        "ZoneId": "ap-southeast-1c",
        "RegionId": "ap-southeast-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "Singapore"
      },
      {
        "ZoneName": "Singapore Mzone2 B+C",
        "ZoneId": "ap-southeast-1MAZ2(b,c)",
        "RegionId": "ap-southeast-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "Singapore"
      },
      {
        "ZoneName": "Singapore Mzone3 A+B+C",
        "ZoneId": "ap-southeast-1MAZ3(a,b,c)",
        "RegionId": "ap-southeast-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "Singapore"
      },
      {
        "ZoneName": "Singapore Zone A",
        "ZoneId": "ap-southeast-1a",
        "RegionId": "ap-southeast-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "Singapore"
      },
      {
        "ZoneName": "Singapore Zone B",
        "ZoneId": "ap-southeast-1b",
        "RegionId": "ap-southeast-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "Singapore"
      },
      {
        "ZoneName": "Singapore Mzone1 A+B",
        "ZoneId": "ap-southeast-1MAZ1(a,b)",
        "RegionId": "ap-southeast-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "Singapore"
      },
      {
        "ZoneName": "Sydney Zone B",
        "ZoneId": "ap-southeast-2b",
        "RegionId": "ap-southeast-2",
        "RegionEndpoint": "rds.ap-southeast-2.aliyuncs.com",
        "LocalName": "Australia (Sydney)"
      },
      {
        "ZoneName": "Sydney Mzone1 A+B",
        "ZoneId": "ap-southeast-2MAZ1(a,b)",
        "RegionId": "ap-southeast-2",
        "RegionEndpoint": "rds.ap-southeast-2.aliyuncs.com",
        "LocalName": "Australia (Sydney)"
      },
      {
        "ZoneName": "Sydney Zone A",
        "ZoneId": "ap-southeast-2a",
        "RegionId": "ap-southeast-2",
        "RegionEndpoint": "rds.ap-southeast-2.aliyuncs.com",
        "LocalName": "Australia (Sydney)"
      },
      {
        "ZoneName": "Seoul Zone A",
        "ZoneId": "ap-northeast-2a",
        "RegionId": "ap-northeast-2",
        "RegionEndpoint": "rds.ap-northeast-2.aliyuncs.com",
        "LocalName": "South Korea (Seoul)"
      },
      {
        "ZoneName": "Kuala Lumpur Zone B",
        "ZoneId": "ap-southeast-3b",
        "RegionId": "ap-southeast-3",
        "RegionEndpoint": "rds.ap-southeast-3.aliyuncs.com",
        "LocalName": "Malaysia (Kuala Lumpur)"
      },
      {
        "ZoneName": "Asia Pacific SE 3 Mzone1 A+B",
        "ZoneId": "ap-southeast-3MAZ1(a,b)",
        "RegionId": "ap-southeast-3",
        "RegionEndpoint": "rds.ap-southeast-3.aliyuncs.com",
        "LocalName": "Malaysia (Kuala Lumpur)"
      },
      {
        "ZoneName": "Kuala Lumpur Zone A",
        "ZoneId": "ap-southeast-3a",
        "RegionId": "ap-southeast-3",
        "RegionEndpoint": "rds.ap-southeast-3.aliyuncs.com",
        "LocalName": "Malaysia (Kuala Lumpur)"
      },
      {
        "ZoneName": "Jakarta Zone B",
        "ZoneId": "ap-southeast-5b",
        "RegionId": "ap-southeast-5",
        "RegionEndpoint": "rds.ap-southeast-5.aliyuncs.com",
        "LocalName": "Indonesia (Jakarta)"
      },
      {
        "ZoneName": "Jakarta MZone1 A+B",
        "ZoneId": "ap-southeast-5MAZ1(a,b)",
        "RegionId": "ap-southeast-5",
        "RegionEndpoint": "rds.ap-southeast-5.aliyuncs.com",
        "LocalName": "Indonesia (Jakarta)"
      },
      {
        "ZoneName": "Jakarta Zone C",
        "ZoneId": "ap-southeast-5c",
        "RegionId": "ap-southeast-5",
        "RegionEndpoint": "rds.ap-southeast-5.aliyuncs.com",
        "LocalName": "Indonesia (Jakarta)"
      },
      {
        "ZoneName": "Jakarta Zone A",
        "ZoneId": "ap-southeast-5a",
        "RegionId": "ap-southeast-5",
        "RegionEndpoint": "rds.ap-southeast-5.aliyuncs.com",
        "LocalName": "Indonesia (Jakarta)"
      },
      {
        "ZoneName": "Tokyo Zone C",
        "ZoneId": "ap-northeast-1c",
        "RegionId": "ap-northeast-1",
        "RegionEndpoint": "rds.ap-northeast-1.aliyuncs.com",
        "LocalName": "Japan (Tokyo)"
      },
      {
        "ZoneName": "Tokyo Zone B",
        "ZoneId": "ap-northeast-1b",
        "RegionId": "ap-northeast-1",
        "RegionEndpoint": "rds.ap-northeast-1.aliyuncs.com",
        "LocalName": "Japan (Tokyo)"
      },
      {
        "ZoneName": "Tokyo MZone1 A+B",
        "ZoneId": "ap-northeast-1MAZ1(a,b)",
        "RegionId": "ap-northeast-1",
        "RegionEndpoint": "rds.ap-northeast-1.aliyuncs.com",
        "LocalName": "Japan (Tokyo)"
      },
      {
        "ZoneName": "Tokyo Zone A",
        "ZoneId": "ap-northeast-1a",
        "RegionId": "ap-northeast-1",
        "RegionEndpoint": "rds.ap-northeast-1.aliyuncs.com",
        "LocalName": "Japan (Tokyo)"
      },
      {
        "ZoneName": "EU Central 1 Mzone1 A+B",
        "ZoneId": "eu-central-1MAZ1(a,b)",
        "RegionId": "eu-central-1",
        "RegionEndpoint": "rds.eu-central-1.aliyuncs.com",
        "LocalName": "Germany (Frankfurt)"
      },
      {
        "ZoneName": "Frankfurt Zone C",
        "ZoneId": "eu-central-1c",
        "RegionId": "eu-central-1",
        "RegionEndpoint": "rds.eu-central-1.aliyuncs.com",
        "LocalName": "Germany (Frankfurt)"
      },
      {
        "ZoneName": "Frankfurt Zone A",
        "ZoneId": "eu-central-1a",
        "RegionId": "eu-central-1",
        "RegionEndpoint": "rds.eu-central-1.aliyuncs.com",
        "LocalName": "Germany (Frankfurt)"
      },
      {
        "ZoneName": "Frankfurt Zone B",
        "ZoneId": "eu-central-1b",
        "RegionId": "eu-central-1",
        "RegionEndpoint": "rds.eu-central-1.aliyuncs.com",
        "LocalName": "Germany (Frankfurt)"
      },
      {
        "ZoneName": "London MZone1 A+B",
        "ZoneId": "eu-west-1MAZ1(a,b)",
        "RegionId": "eu-west-1",
        "RegionEndpoint": "rds.eu-west-1.aliyuncs.com",
        "LocalName": "UK (London)"
      },
      {
        "ZoneName": "London Zone A",
        "ZoneId": "eu-west-1a",
        "RegionId": "eu-west-1",
        "RegionEndpoint": "rds.eu-west-1.aliyuncs.com",
        "LocalName": "UK (London)"
      },
      {
        "ZoneName": "London Zone B",
        "ZoneId": "eu-west-1b",
        "RegionId": "eu-west-1",
        "RegionEndpoint": "rds.eu-west-1.aliyuncs.com",
        "LocalName": "UK (London)"
      },
      {
        "ZoneName": "US West 1 Mzone1 A+B",
        "ZoneId": "us-west-1MAZ1(a,b)",
        "RegionId": "us-west-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "US (Silicon Valley)"
      },
      {
        "ZoneName": "Silicon Valley Zone A",
        "ZoneId": "us-west-1a",
        "RegionId": "us-west-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "US (Silicon Valley)"
      },
      {
        "ZoneName": "Silicon Valley Zone B",
        "ZoneId": "us-west-1b",
        "RegionId": "us-west-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "US (Silicon Valley)"
      },
      {
        "ZoneName": "US East 1 Mzone1 A+B",
        "ZoneId": "us-east-1MAZ1(a,b)",
        "RegionId": "us-east-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "US (Virginia)"
      },
      {
        "ZoneName": "Virginia Zone B",
        "ZoneId": "us-east-1b",
        "RegionId": "us-east-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "US (Virginia)"
      },
      {
        "ZoneName": "Virginia Zone A",
        "ZoneId": "us-east-1a",
        "RegionId": "us-east-1",
        "RegionEndpoint": "rds.aliyuncs.com",
        "LocalName": "US (Virginia)"
      },
      {
        "ZoneName": "Dubai Zone A",
        "ZoneId": "me-east-1a",
        "RegionId": "me-east-1",
        "RegionEndpoint": "rds.me-east-1.aliyuncs.com",
        "LocalName": "UAE (Dubai)"
      },
      {
        "ZoneName": "Riyadh Zone B",
        "ZoneId": "me-central-1b",
        "RegionId": "me-central-1",
        "RegionEndpoint": "rds.me-central-1.aliyuncs.com",
        "LocalName": "SAU (Riyadh)"
      },
      {
        "ZoneName": "Riyadh Zone A",
        "ZoneId": "me-central-1a",
        "RegionId": "me-central-1",
        "RegionEndpoint": "rds.me-central-1.aliyuncs.com",
        "LocalName": "SAU (Riyadh)"
      },
      {
        "ZoneName": "Manila Zone A",
        "ZoneId": "ap-southeast-6a",
        "RegionId": "ap-southeast-6",
        "RegionEndpoint": "rds.ap-southeast-6.aliyuncs.com",
        "LocalName": "Philippines (Manila)"
      },
      {
        "ZoneName": "Bangkok Zone A",
        "ZoneId": "ap-southeast-7a",
        "RegionId": "ap-southeast-7",
        "RegionEndpoint": "rds.ap-southeast-7.aliyuncs.com",
        "LocalName": "Thailand (Bangkok)"
      },
      {
        "ZoneName": "Asia Pacific SOU 1 Mzone1 A+B",
        "ZoneId": "ap-south-1MAZ1(a,b)",
        "RegionId": "ap-south-1",
        "RegionEndpoint": "rds.ap-south-1.aliyuncs.com",
        "LocalName": "India (Mumbai)"
      },
      {
        "ZoneName": "Mumbai Zone B",
        "ZoneId": "ap-south-1b",
        "RegionId": "ap-south-1",
        "RegionEndpoint": "rds.ap-south-1.aliyuncs.com",
        "LocalName": "India (Mumbai)"
      },
      {
        "ZoneName": "Mumbai Zone A",
        "ZoneId": "ap-south-1a",
        "RegionId": "ap-south-1",
        "RegionEndpoint": "rds.ap-south-1.aliyuncs.com",
        "LocalName": "India (Mumbai)"
      }
    ]
  }
}