You create a Globally Distributed Autonomous Database configuration, which is used as a blueprint for the service to procure VMs, deploy the Globally Distributed Autonomous Database software components on systems you designate in the configuration and start required services. You can then monitor and perform life cycle operations on the database.

The topics that follow explain how to configure, deploy, and perform operations on Globally Distributed Autonomous Database.

• Creation and Deployment Workflow
  To get started with Globally Distributed Autonomous Database, you must create the configuration, ensure signed certificates are uploaded, and then deploy the configuration.
• Creating a Globally Distributed Autonomous Database Resource
  A Globally Distributed Autonomous Database resource contains the connectivity and configuration details of the shards and shard catalog databases.
• Listing Globally Distributed Databases
  
• Viewing Globally Distributed Autonomous Database Details
  You view Globally Distributed Autonomous Database configuration, backup, and maintenance information by going to its Details page.
• Managing Certificates
  You must upload signed certificates for the shard directors (GSMs) to the Globally Distributed Autonomous Database before you can deploy the configuration.
• Deploying Globally Distributed Autonomous Database
  You deploy a Globally Distributed Autonomous Database after uploading signed certificates and any time you make changes to the configuration, such as add a shard.
• Downloading Client Credentials
  You need the client credentials and connection information to connect to your Globally Distributed Autonomous Database. The client credentials include the wallet.
• Adding Shards
  Add shards to scale out your Globally Distributed Autonomous Database
• Modifying Shards
  You can modify a shard's ECPU count, auto-scaling setting, and storage allocation.
• Terminating (Deleting) a Shard
  Terminating a shard in a Globally Distributed Autonomous Database configuration permanently deletes it and removes all automatic backups. You cannot recover a terminated shard.
• Stopping a Globally Distributed Autonomous Database
  
• Starting a Globally Distributed Autonomous Database
  
• Terminating (Deleting) a Globally Distributed Autonomous Database
  Terminating Globally Distributed Autonomous Database permanently deletes it and removes all automatic backups. You cannot recover a terminated Globally Distributed Autonomous Database.
• Moving Globally Distributed Autonomous Database Resources
  You can move a Globally Distributed Autonomous Database from one compartment to another.
• Backing Up and Restoring a Globally Distributed Autonomous Database
  Backup and restore is done at the shard (and catalog) database level and is managed by the underlying Autonomous Database.
• Updating the Display Name
  You can change the display name of a Globally Distributed Autonomous Database from its details page.
• Managing Tags
  Tags help you locate resources within your tenancy.
• Globally Distributed Autonomous Database REST APIs
  The following REST APIs are used to interact with the Globally Distributed Autonomous Database (distributed-autonomous-database) resource.