Dokumentasi ini AWS CLI hanya untuk Versi 1.

Kami mengumumkan akhir dukungan yang akan datang untuk AWS CLI versi 1. Kami menyarankan Anda bermigrasi ke AWS CLI versi 2. Untuk tanggal, detail tambahan, dan informasi tentang cara bermigrasi, lihat pengumuman. Untuk dokumentasi yang terkait dengan Versi 2 AWS CLI, lihat Panduan Pengguna Versi 2.

Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris.

Contoh Amazon RDS menggunakan AWS CLI

Contoh kode berikut menunjukkan cara melakukan tindakan dan menerapkan skenario umum dengan menggunakan AWS Command Line Interface dengan Amazon RDS.

Tindakan merupakan kutipan kode dari program yang lebih besar dan harus dijalankan dalam konteks. Sementara tindakan menunjukkan cara memanggil fungsi layanan individual, Anda dapat melihat tindakan dalam konteks dalam skenario terkait.

Setiap contoh menyertakan tautan ke kode sumber lengkap, di mana Anda dapat menemukan instruksi tentang cara mengatur dan menjalankan kode dalam konteks.

Topik

Tindakan

Tindakan

Contoh kode berikut menunjukkan cara menggunakanadd-option-to-option-group.

AWS CLI

Untuk menambahkan opsi ke grup opsi

add-option-to-option-groupContoh berikut menambahkan opsi ke grup opsi yang ditentukan.


aws rds add-option-to-option-group \
    --option-group-name myoptiongroup \
    --options OptionName=OEM,Port=5500,DBSecurityGroupMemberships=default \
    --apply-immediately

Output:


{
    "OptionGroup": {
        "OptionGroupName": "myoptiongroup",
        "OptionGroupDescription": "Test Option Group",
        "EngineName": "oracle-ee",
        "MajorEngineVersion": "12.1",
        "Options": [
            {
                "OptionName": "Timezone",
                "OptionDescription": "Change time zone",
                "Persistent": true,
                "Permanent": false,
                "OptionSettings": [
                    {
                        "Name": "TIME_ZONE",
                        "Value": "Australia/Sydney",
                        "DefaultValue": "UTC",
                        "Description": "Specifies the timezone the user wants to change the system time to",
                        "ApplyType": "DYNAMIC",
                        "DataType": "STRING",
                        "AllowedValues": "Africa/Cairo,Africa/Casablanca,Africa/Harare,Africa/Lagos,Africa/Luanda,Africa/Monrovia,Africa/Nairobi,Africa/Tripoli,Africa/Windhoek,America/Araguaina,America/Argentina/Buenos_Aires,America/Asuncion,America/Bogota,America/Caracas,America/Chicago,America/Chihuahua,America/Cuiaba,America/Denver,America/Detroit,America/Fortaleza,America/Godthab,America/Guatemala,America/Halifax,America/Lima,America/Los_Angeles,America/Manaus,America/Matamoros,America/Mexico_City,America/Monterrey,America/Montevideo,America/New_York,America/Phoenix,America/Santiago,America/Sao_Paulo,America/Tijuana,America/Toronto,Asia/Amman,Asia/Ashgabat,Asia/Baghdad,Asia/Baku,Asia/Bangkok,Asia/Beirut,Asia/Calcutta,Asia/Damascus,Asia/Dhaka,Asia/Hong_Kong,Asia/Irkutsk,Asia/Jakarta,Asia/Jerusalem,Asia/Kabul,Asia/Karachi,Asia/Kathmandu,Asia/Kolkata,Asia/Krasnoyarsk,Asia/Magadan,Asia/Manila,Asia/Muscat,Asia/Novosibirsk,Asia/Rangoon,Asia/Riyadh,Asia/Seoul,Asia/Shanghai,Asia/Singapore,Asia/Taipei,Asia/Tehran,Asia/Tokyo,Asia/Ulaanbaatar,Asia/Vladivostok,Asia/Yakutsk,Asia/Yerevan,Atlantic/Azores,Atlantic/Cape_Verde,Australia/Adelaide,Australia/Brisbane,Australia/Darwin,Australia/Eucla,Australia/Hobart,Australia/Lord_Howe,Australia/Perth,Australia/Sydney,Brazil/DeNoronha,Brazil/East,Canada/Newfoundland,Canada/Saskatchewan,Etc/GMT-3,Europe/Amsterdam,Europe/Athens,Europe/Berlin,Europe/Dublin,Europe/Helsinki,Europe/Kaliningrad,Europe/London,Europe/Madrid,Europe/Moscow,Europe/Paris,Europe/Prague,Europe/Rome,Europe/Sarajevo,Pacific/Apia,Pacific/Auckland,Pacific/Chatham,Pacific/Fiji,Pacific/Guam,Pacific/Honolulu,Pacific/Kiritimati,Pacific/Marquesas,Pacific/Samoa,Pacific/Tongatapu,Pacific/Wake,US/Alaska,US/Central,US/East-Indiana,US/Eastern,US/Pacific,UTC",
                        "IsModifiable": true,
                        "IsCollection": false
                    }
                ],
                "DBSecurityGroupMemberships": [],
                "VpcSecurityGroupMemberships": []
            },
            {
                "OptionName": "OEM",
                "OptionDescription": "Oracle 12c EM Express",
                "Persistent": false,
                "Permanent": false,
                "Port": 5500,
                "OptionSettings": [],
                "DBSecurityGroupMemberships": [
                    {
                        "DBSecurityGroupName": "default",
                        "Status": "authorized"
                    }
                ],
                "VpcSecurityGroupMemberships": []
            }
        ],
        "AllowsVpcAndNonVpcInstanceMemberships": false,
        "OptionGroupArn": "arn:aws:rds:us-east-1:123456789012:og:myoptiongroup"
    }
}

Untuk informasi selengkapnya, lihat Men ambahkan Opsi ke Grup Opsi di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat AddOptionToOptionGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanadd-role-to-db-cluster.

AWS CLI

Untuk mengaitkan peran AWS Identitas dan Manajemen Akses (IAM) dengan cluster DB

add-role-to-db-clusterContoh berikut mengaitkan peran dengan cluster DB.


aws rds add-role-to-db-cluster \
    --db-cluster-identifier mydbcluster \
    --role-arn arn:aws:iam::123456789012:role/RDSLoadFromS3

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Mengaitkan peran IAM dengan cluster DB Amazon Aurora MySQL di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat AddRoleToDbCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanadd-role-to-db-instance.

AWS CLI

Untuk mengaitkan peran AWS Identitas dan Manajemen Akses (IAM) dengan instans DB

add-role-to-db-instanceContoh berikut menambahkan peran ke instance Oracle DB bernamatest-instance.


aws rds add-role-to-db-instance \
    --db-instance-identifier test-instance \
    --feature-name S3_INTEGRATION \
    --role-arn arn:aws:iam::111122223333:role/rds-s3-integration-role

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Prasyarat untuk Integrasi Amazon RDS Oracle dengan Amazon S3 di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat AddRoleToDbInstance di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanadd-source-identifier-to-subscription.

AWS CLI

Untuk menambahkan pengidentifikasi sumber ke langganan

add-source-identifierContoh berikut menambahkan pengidentifikasi sumber lain ke langganan yang ada.


aws rds add-source-identifier-to-subscription \
    --subscription-name my-instance-events \
    --source-identifier test-instance-repl

Output:


{
    "EventSubscription": {
        "SubscriptionCreationTime": "Tue Jul 31 23:22:01 UTC 2018",
        "CustSubscriptionId": "my-instance-events",
        "EventSubscriptionArn": "arn:aws:rds:us-east-1:123456789012:es:my-instance-events",
        "Enabled": false,
        "Status": "modifying",
        "EventCategoriesList": [
            "backup",
            "recovery"
        ],
        "CustomerAwsId": "123456789012",
        "SnsTopicArn": "arn:aws:sns:us-east-1:123456789012:interesting-events",
        "SourceType": "db-instance",
        "SourceIdsList": [
            "test-instance",
            "test-instance-repl"
        ]
    }
}

Untuk detail API, lihat AddSourceIdentifierToSubscription di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanadd-tags-to-resource.

AWS CLI

Untuk menambahkan tag ke sumber daya

add-tags-to-resourceContoh berikut menambahkan tag ke database RDS.


aws rds add-tags-to-resource \
    --resource-name arn:aws:rds:us-east-1:123456789012:db:database-mysql \
    --tags "[{\"Key\": \"Name\",\"Value\": \"MyDatabase\"},{\"Key\": \"Environment\",\"Value\": \"test\"}]"

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Menandai Sumber Daya Amazon RDS di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat AddTagsToResource di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanapply-pending-maintenance-action.

AWS CLI

Untuk menerapkan tindakan pemeliharaan yang tertunda

apply-pending-maintenance-actionContoh berikut menerapkan tindakan pemeliharaan tertunda untuk cluster DB.


aws rds apply-pending-maintenance-action \
    --resource-identifier arn:aws:rds:us-east-1:123456789012:cluster:my-db-cluster \
    --apply-action system-update \
    --opt-in-type immediate

Output:


{
    "ResourcePendingMaintenanceActions": {
        "ResourceIdentifier": "arn:aws:rds:us-east-1:123456789012:cluster:my-db-cluster",
        "PendingMaintenanceActionDetails": [
            {
                "Action": "system-update",
                "OptInStatus": "immediate",
                "CurrentApplyDate": "2021-01-23T01:07:36.100Z",
                "Description": "Upgrade to Aurora PostgreSQL 3.3.2"
            }
        ]
    }
}

Untuk informasi selengkapnya, lihat Mempertahankan instans DB di Panduan Pengguna Amazon RDS dan Memelihara cluster Amazon Aurora DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ApplyPendingMaintenanceAction di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanauthorize-db-security-group-ingress.

AWS CLI

Untuk mengaitkan peran AWS Identitas dan Manajemen Akses (IAM) dengan instans DB

authorize-db-security-group-ingressContoh berikut mengonfigurasi grup keamanan default dengan aturan masuk untuk kisaran IP CIDR 192.0.2. 0/24.


aws rds authorize-db-security-group-ingress \
    --db-security-group-name default \
    --cidrip 192.0.2.0/24

Output:


{
    "DBSecurityGroup": {
        "OwnerId": "123456789012",
        "DBSecurityGroupName": "default",
        "DBSecurityGroupDescription": "default",
        "EC2SecurityGroups": [],
        "IPRanges": [
            {
                "Status": "authorizing",
                "CIDRIP": "192.0.2.0/24"
            }
        ],
        "DBSecurityGroupArn": "arn:aws:rds:us-east-1:111122223333:secgrp:default"
    }
}

Untuk informasi selengkapnya, lihat Mengotorisasi Akses Jaringan ke Grup Keamanan DB dari Rentang IP di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat AuthorizeDbSecurityGroupIngress di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanbacktrack-db-cluster.

AWS CLI

Untuk melacak kembali cluster Aurora DB

backtrack-db-clusterContoh berikut melacak kembali cluster sampel cluster DB yang ditentukan ke 19 Maret 2018, pukul 10 pagi.


aws rds backtrack-db-cluster --db-cluster-identifier sample-cluster --backtrack-to 2018-03-19T10:00:00+00:00

Perintah ini mengeluarkan blok JSON yang mengakui perubahan pada sumber daya RDS.

Untuk detail API, lihat BacktrackDbCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancancel-export-task.

AWS CLI

Untuk membatalkan ekspor snapshot ke Amazon S3

cancel-export-taskContoh berikut membatalkan tugas ekspor yang sedang berlangsung yang mengekspor snapshot ke Amazon S3.


aws rds cancel-export-task \
    --export-task-identifier my-s3-export-1

Output:


{
    "ExportTaskIdentifier": "my-s3-export-1",
    "SourceArn": "arn:aws:rds:us-east-1:123456789012:snapshot:publisher-final-snapshot",
    "SnapshotTime": "2019-03-24T20:01:09.815Z",
    "S3Bucket": "amzn-s3-demo-bucket",
    "S3Prefix": "",
    "IamRoleArn": "arn:aws:iam::123456789012:role/service-role/export-snap-S3-role",
    "KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/abcd0000-7bfd-4594-af38-aabbccddeeff",
    "Status": "CANCELING",
    "PercentProgress": 0,
    "TotalExtractedDataInGB": 0
}

Untuk informasi selengkapnya, lihat Mem batalkan tugas ekspor snapshot di Panduan Pengguna Amazon RDS atau Mem batalkan tugas ekspor snapshot di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CancelExportTask di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancopy-db-cluster-parameter-group.

AWS CLI

Untuk menyalin grup parameter cluster DB

copy-db-cluster-parameter-groupContoh berikut membuat salinan grup parameter cluster DB.


aws rds copy-db-cluster-parameter-group \
    --source-db-cluster-parameter-group-identifier mydbclusterpg \
    --target-db-cluster-parameter-group-identifier mydbclusterpgcopy \
    --target-db-cluster-parameter-group-description "Copy of mydbclusterpg parameter group"

Output:


{
    "DBClusterParameterGroup": {
        "DBClusterParameterGroupName": "mydbclusterpgcopy",
        "DBClusterParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:cluster-pg:mydbclusterpgcopy",
        "DBParameterGroupFamily": "aurora-mysql5.7",
        "Description": "Copy of mydbclusterpg parameter group"
    }
}

Untuk informasi selengkapnya, lihat Men yal in Grup Parameter Cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CopyDbClusterParameterGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancopy-db-cluster-snapshot.

AWS CLI

Untuk menyalin snapshot cluster DB

copy-db-cluster-snapshotContoh berikut membuat salinan snapshot cluster DB, termasuk tagnya.


aws rds copy-db-cluster-snapshot \
    --source-db-cluster-snapshot-identifier arn:aws:rds:us-east-1:123456789012:cluster-snapshot:rds:myaurora-2019-06-04-09-16
    --target-db-cluster-snapshot-identifier myclustersnapshotcopy \
    --copy-tags

Output:


{
    "DBClusterSnapshot": {
        "AvailabilityZones": [
            "us-east-1a",
            "us-east-1b",
            "us-east-1e"
        ],
        "DBClusterSnapshotIdentifier": "myclustersnapshotcopy",
        "DBClusterIdentifier": "myaurora",
        "SnapshotCreateTime": "2019-06-04T09:16:42.649Z",
        "Engine": "aurora-mysql",
        "AllocatedStorage": 0,
        "Status": "available",
        "Port": 0,
        "VpcId": "vpc-6594f31c",
        "ClusterCreateTime": "2019-04-15T14:18:42.785Z",
        "MasterUsername": "myadmin",
        "EngineVersion": "5.7.mysql_aurora.2.04.2",
        "LicenseModel": "aurora-mysql",
        "SnapshotType": "manual",
        "PercentProgress": 100,
        "StorageEncrypted": true,
        "KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/AKIAIOSFODNN7EXAMPLE",
        "DBClusterSnapshotArn": "arn:aws:rds:us-east-1:123456789012:cluster-snapshot:myclustersnapshotcopy",
        "IAMDatabaseAuthenticationEnabled": false
    }
}

Untuk informasi selengkapnya, lihat Men yal in Snapshot di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CopyDbClusterSnapshot di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancopy-db-parameter-group.

AWS CLI

Untuk menyalin grup parameter cluster DB

copy-db-parameter-groupContoh berikut membuat salinan grup parameter DB.


aws rds copy-db-parameter-group \
    --source-db-parameter-group-identifier mydbpg \
    --target-db-parameter-group-identifier mydbpgcopy \
    --target-db-parameter-group-description "Copy of mydbpg parameter group"

Output:


{
    "DBParameterGroup": {
        "DBParameterGroupName": "mydbpgcopy",
        "DBParameterGroupArn": "arn:aws:rds:us-east-1:814387698303:pg:mydbpgcopy",
        "DBParameterGroupFamily": "mysql5.7",
        "Description": "Copy of mydbpg parameter group"
    }
}

Untuk informasi selengkapnya, lihat Menyal in Grup Parameter DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat CopyDbParameterGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancopy-db-snapshot.

AWS CLI

Untuk menyalin snapshot DB

copy-db-snapshotContoh berikut membuat salinan snapshot DB.


aws rds copy-db-snapshot \
    --source-db-snapshot-identifier rds:database-mysql-2019-06-06-08-38
    --target-db-snapshot-identifier mydbsnapshotcopy

Output:


{
    "DBSnapshot": {
        "VpcId": "vpc-6594f31c",
        "Status": "creating",
        "Encrypted": true,
        "SourceDBSnapshotIdentifier": "arn:aws:rds:us-east-1:123456789012:snapshot:rds:database-mysql-2019-06-06-08-38",
        "MasterUsername": "admin",
        "Iops": 1000,
        "Port": 3306,
        "LicenseModel": "general-public-license",
        "DBSnapshotArn": "arn:aws:rds:us-east-1:123456789012:snapshot:mydbsnapshotcopy",
        "EngineVersion": "5.6.40",
        "OptionGroupName": "default:mysql-5-6",
        "ProcessorFeatures": [],
        "Engine": "mysql",
        "StorageType": "io1",
        "DbiResourceId": "db-ZI7UJ5BLKMBYFGX7FDENCKADC4",
        "KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/AKIAIOSFODNN7EXAMPLE",
        "SnapshotType": "manual",
        "IAMDatabaseAuthenticationEnabled": false,
        "SourceRegion": "us-east-1",
        "DBInstanceIdentifier": "database-mysql",
        "InstanceCreateTime": "2019-04-30T15:45:53.663Z",
        "AvailabilityZone": "us-east-1f",
        "PercentProgress": 0,
        "AllocatedStorage": 100,
        "DBSnapshotIdentifier": "mydbsnapshotcopy"
    }
}

Untuk informasi selengkapnya, lihat Menyal in Snapshot di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat CopyDbSnapshot di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancopy-option-group.

AWS CLI

Untuk menyalin grup opsi

copy-option-groupContoh berikut membuat salinan grup opsi.


aws rds copy-option-group \
    --source-option-group-identifier myoptiongroup \
    --target-option-group-identifier new-option-group \
    --target-option-group-description "My option group copy"

Output:


{
    "OptionGroup": {
        "Options": [],
        "OptionGroupName": "new-option-group",
        "MajorEngineVersion": "11.2",
        "OptionGroupDescription": "My option group copy",
        "AllowsVpcAndNonVpcInstanceMemberships": true,
        "EngineName": "oracle-ee",
        "OptionGroupArn": "arn:aws:rds:us-east-1:123456789012:og:new-option-group"
    }
}

Untuk informasi selengkapnya, lihat Membuat Salinan Grup Opsi di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat CopyOptionGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-blue-green-deployment.

AWS CLI

Contoh 1: Untuk membuat blue/green penerapan untuk instance RDS untuk MySQL DB

create-blue-green-deploymentContoh berikut membuat blue/green penerapan untuk instance MySQL DB.


aws rds create-blue-green-deployment \
    --blue-green-deployment-name bgd-cli-test-instance \
    --source arn:aws:rds:us-east-1:123456789012:db:my-db-instance \
    --target-engine-version 8.0 \
    --target-db-parameter-group-name mysql-80-group

Output:


{
    "BlueGreenDeployment": {
        "BlueGreenDeploymentIdentifier": "bgd-v53303651eexfake",
        "BlueGreenDeploymentName": "bgd-cli-test-instance",
        "Source": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance",
        "SwitchoverDetails": [
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-1"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-2"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-3"
            }
        ],
        "Tasks": [
            {
                "Name": "CREATING_READ_REPLICA_OF_SOURCE",
                "Status": "PENDING"
            },
            {
                "Name": "DB_ENGINE_VERSION_UPGRADE",
                "Status": "PENDING"
            },
            {
                "Name": "CONFIGURE_BACKUPS",
                "Status": "PENDING"
            },
            {
                "Name": "CREATING_TOPOLOGY_OF_SOURCE",
                "Status": "PENDING"
            }
        ],
        "Status": "PROVISIONING",
        "CreateTime": "2022-02-25T21:18:51.183000+00:00"
    }
}

Untuk informasi selengkapnya, lihat Membuat blue/green pener apan di Panduan Pengguna Amazon RDS.

Contoh 2: Untuk membuat blue/green penerapan untuk cluster Aurora MySQL DB

create-blue-green-deploymentContoh berikut membuat blue/green penerapan untuk cluster Aurora MySQL DB.


aws rds create-blue-green-deployment \
    --blue-green-deployment-name my-blue-green-deployment \
    --source arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster \
    --target-engine-version 8.0 \
    --target-db-cluster-parameter-group-name ams-80-binlog-enabled \
    --target-db-parameter-group-name mysql-80-cluster-group

Output:


{
      "BlueGreenDeployment": {
        "BlueGreenDeploymentIdentifier": "bgd-wi89nwzglccsfake",
        "BlueGreenDeploymentName": "my-blue-green-deployment",
        "Source": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
        "SwitchoverDetails": [
          {
            "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
            "Status": "PROVISIONING"
          },
          {
            "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-1",
            "Status": "PROVISIONING"
          },
          {
            "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-2",
            "Status": "PROVISIONING"
          },
          {
            "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-3",
            "Status": "PROVISIONING"
          },
          {
            "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-excluded-member-endpoint",
            "Status": "PROVISIONING"
          },
          {
            "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-reader-endpoint",
            "Status": "PROVISIONING"
          }
        ],
        "Tasks": [
          {
            "Name": "CREATING_READ_REPLICA_OF_SOURCE",
            "Status": "PENDING"
          },
          {
            "Name": "DB_ENGINE_VERSION_UPGRADE",
            "Status": "PENDING"
          },
          {
            "Name": "CREATE_DB_INSTANCES_FOR_CLUSTER",
            "Status": "PENDING"
          },
          {
            "Name": "CREATE_CUSTOM_ENDPOINTS",
            "Status": "PENDING"
          }
        ],
        "Status": "PROVISIONING",
        "CreateTime": "2022-02-25T21:12:00.288000+00:00"
      }
}

Untuk informasi selengkapnya, lihat Membuat blue/green pener apan di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CreateBlueGreenDeployment di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-db-cluster-endpoint.

AWS CLI

Untuk membuat titik akhir cluster DB kustom

create-db-cluster-endpointContoh berikut membuat titik akhir cluster DB kustom dan mengaitkannya dengan cluster Aurora DB yang ditentukan.


aws rds create-db-cluster-endpoint \
    --db-cluster-endpoint-identifier mycustomendpoint \
    --endpoint-type reader \
    --db-cluster-identifier mydbcluster \
    --static-members dbinstance1 dbinstance2

Output:


{
    "DBClusterEndpointIdentifier": "mycustomendpoint",
    "DBClusterIdentifier": "mydbcluster",
    "DBClusterEndpointResourceIdentifier": "cluster-endpoint-ANPAJ4AE5446DAEXAMPLE",
    "Endpoint": "mycustomendpoint.cluster-custom-cnpexample.us-east-1.rds.amazonaws.com",
    "Status": "creating",
    "EndpointType": "CUSTOM",
    "CustomEndpointType": "READER",
    "StaticMembers": [
        "dbinstance1",
        "dbinstance2"
    ],
    "ExcludedMembers": [],
    "DBClusterEndpointArn": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:mycustomendpoint"
}

Untuk informasi selengkapnya, lihat Manajemen Koneksi Amazon Aurora di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CreateDbClusterEndpoint di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-db-cluster-parameter-group.

AWS CLI

Untuk membuat grup parameter cluster DB

create-db-cluster-parameter-groupContoh berikut membuat grup parameter cluster DB.


aws rds create-db-cluster-parameter-group \
    --db-cluster-parameter-group-name mydbclusterparametergroup \
    --db-parameter-group-family aurora5.6 \
    --description "My new cluster parameter group"

Output:


{
    "DBClusterParameterGroup": {
        "DBClusterParameterGroupName": "mydbclusterparametergroup",
        "DBParameterGroupFamily": "aurora5.6",
        "Description": "My new cluster parameter group",
        "DBClusterParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:cluster-pg:mydbclusterparametergroup"
    }
}

Untuk informasi selengkapnya, lihat Membuat Grup Parameter Cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CreateDbClusterParameterGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-db-cluster-snapshot.

AWS CLI

Untuk membuat snapshot cluster DB

create-db-cluster-snapshotContoh berikut membuat snapshot cluster DB.


aws rds create-db-cluster-snapshot \
    --db-cluster-identifier mydbcluster \
    --db-cluster-snapshot-identifier mydbclustersnapshot

Output:


{
    "DBClusterSnapshot": {
        "AvailabilityZones": [
            "us-east-1a",
            "us-east-1b",
            "us-east-1e"
        ],
        "DBClusterSnapshotIdentifier": "mydbclustersnapshot",
        "DBClusterIdentifier": "mydbcluster",
        "SnapshotCreateTime": "2019-06-18T21:21:00.469Z",
        "Engine": "aurora-mysql",
        "AllocatedStorage": 1,
        "Status": "creating",
        "Port": 0,
        "VpcId": "vpc-6594f31c",
        "ClusterCreateTime": "2019-04-15T14:18:42.785Z",
        "MasterUsername": "myadmin",
        "EngineVersion": "5.7.mysql_aurora.2.04.2",
        "LicenseModel": "aurora-mysql",
        "SnapshotType": "manual",
        "PercentProgress": 0,
        "StorageEncrypted": true,
        "KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/AKIAIOSFODNN7EXAMPLE",
        "DBClusterSnapshotArn": "arn:aws:rds:us-east-1:123456789012:cluster-snapshot:mydbclustersnapshot",
        "IAMDatabaseAuthenticationEnabled": false
    }
}

Untuk informasi selengkapnya, lihat Membuat Snapshot Cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CreateDbClusterSnapshot di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-db-cluster.

AWS CLI

Contoh 1: Untuk membuat kluster DB yang kompatibel dengan MySQL 5.7

create-db-clusterContoh berikut membuat kluster DB yang kompatibel dengan MySQL 5.7 menggunakan versi mesin default. Ganti kata sandi sampel secret99 dengan kata sandi yang aman. Saat Anda menggunakan konsol untuk membuat cluster DB, Amazon RDS secara otomatis membuat instance DB penulis untuk cluster DB Anda. Namun, ketika Anda menggunakan AWS CLI untuk membuat cluster DB, Anda harus secara eksplisit membuat instance Writer DB untuk cluster DB Anda menggunakan perintah create-db-instance AWS CLI.


aws rds create-db-cluster \
    --db-cluster-identifier sample-cluster \
    --engine aurora-mysql \
    --engine-version 5.7 \
    --master-username admin \
    --master-user-password secret99 \
    --db-subnet-group-name default \
    --vpc-security-group-ids sg-0b9130572daf3dc16

Output:


{
    "DBCluster": {
        "DBSubnetGroup": "default",
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sg-0b9130572daf3dc16",
                "Status": "active"
            }
        ],
        "AllocatedStorage": 1,
        "AssociatedRoles": [],
        "PreferredBackupWindow": "09:12-09:42",
        "ClusterCreateTime": "2023-02-27T23:21:33.048Z",
        "DeletionProtection": false,
        "IAMDatabaseAuthenticationEnabled": false,
        "ReadReplicaIdentifiers": [],
        "EngineMode": "provisioned",
        "Engine": "aurora-mysql",
        "StorageEncrypted": false,
        "MultiAZ": false,
        "PreferredMaintenanceWindow": "mon:04:31-mon:05:01",
        "HttpEndpointEnabled": false,
        "BackupRetentionPeriod": 1,
        "DbClusterResourceId": "cluster-ANPAJ4AE5446DAEXAMPLE",
        "DBClusterIdentifier": "sample-cluster",
        "AvailabilityZones": [
            "us-east-1a",
            "us-east-1b",
            "us-east-1e"
        ],
        "MasterUsername": "master",
        "EngineVersion": "5.7.mysql_aurora.2.11.1",
        "DBClusterArn": "arn:aws:rds:us-east-1:123456789012:cluster:sample-cluster",
        "DBClusterMembers": [],
        "Port": 3306,
        "Status": "creating",
        "Endpoint": "sample-cluster.cluster-cnpexample.us-east-1.rds.amazonaws.com",
        "DBClusterParameterGroup": "default.aurora-mysql5.7",
        "HostedZoneId": "Z2R2ITUGPM61AM",
        "ReaderEndpoint": "sample-cluster.cluster-ro-cnpexample.us-east-1.rds.amazonaws.com",
        "CopyTagsToSnapshot": false
    }
}

Contoh 2: Untuk membuat cluster DB yang kompatibel dengan PostgreSQL

create-db-clusterContoh berikut membuat cluster PostgreSQL-compatible DB menggunakan versi mesin default. Ganti contoh kata sandi secret99 dengan kata sandi yang aman. Saat Anda menggunakan konsol untuk membuat cluster DB, Amazon RDS secara otomatis membuat instance DB penulis untuk cluster DB Anda. Namun, ketika Anda menggunakan AWS CLI untuk membuat cluster DB, Anda harus secara eksplisit membuat instance Writer DB untuk cluster DB Anda menggunakan perintah create-db-instance AWS CLI.


aws rds create-db-cluster \
    --db-cluster-identifier sample-pg-cluster \
    --engine aurora-postgresql \
    --master-username master \
    --master-user-password secret99 \
    --db-subnet-group-name default \
    --vpc-security-group-ids sg-0b9130572daf3dc16

Output:


{
    "DBCluster": {
        "Endpoint": "sample-pg-cluster.cluster-cnpexample.us-east-1.rds.amazonaws.com",
        "HttpEndpointEnabled": false,
        "DBClusterMembers": [],
        "EngineMode": "provisioned",
        "CopyTagsToSnapshot": false,
        "HostedZoneId": "Z2R2ITUGPM61AM",
        "IAMDatabaseAuthenticationEnabled": false,
        "AllocatedStorage": 1,
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sg-0b9130572daf3dc16",
                "Status": "active"
            }
        ],
        "DeletionProtection": false,
        "StorageEncrypted": false,
        "BackupRetentionPeriod": 1,
        "PreferredBackupWindow": "09:56-10:26",
        "ClusterCreateTime": "2023-02-27T23:26:08.371Z",
        "DBClusterParameterGroup": "default.aurora-postgresql13",
        "EngineVersion": "13.7",
        "Engine": "aurora-postgresql",
        "Status": "creating",
        "DBClusterIdentifier": "sample-pg-cluster",
        "MultiAZ": false,
        "Port": 5432,
        "DBClusterArn": "arn:aws:rds:us-east-1:123456789012:cluster:sample-pg-cluster",
        "AssociatedRoles": [],
        "DbClusterResourceId": "cluster-ANPAJ4AE5446DAEXAMPLE",
        "PreferredMaintenanceWindow": "wed:03:33-wed:04:03",
        "ReaderEndpoint": "sample-pg-cluster.cluster-ro-cnpexample.us-east-1.rds.amazonaws.com",
        "MasterUsername": "master",
        "AvailabilityZones": [
            "us-east-1a",
            "us-east-1b",
            "us-east-1c"
        ],
        "ReadReplicaIdentifiers": [],
        "DBSubnetGroup": "default"
    }
}

Contoh 3: Untuk membuat cluster DB Aurora PostgreSQL dengan Konfigurasi Ekspres

create-db-clusterContoh berikut membuat cluster Aurora PostgreSQL-compatible DB dengan Konfigurasi Ekspres diaktifkan. Tidak seperti klaster buat standar, Konfigurasi Ekspres secara otomatis menambahkan instance DB sample-cluster-instance-1 untuk cluster DB Anda, sehingga Anda tidak perlu memanggil perintah create-db-instance AWS CLI secara terpisah.


aws rds create-db-cluster \
    --db-cluster-identifier sample-cluster \
    --engine aurora-postgresql \
    --with-express-configuration

Output:


{
    "DBCluster": {
        "AllocatedStorage": 1,
        "AvailabilityZones": [
            "us-east-1c",
            "us-east-1a",
            "us-east-1b"
        ],
        "BackupRetentionPeriod": 7,
        "DBClusterIdentifier": "sample-cluster",
        "DBClusterParameterGroup": "default.aurora-postgresql17",
        "Status": "creating",
        "MultiAZ": false,
        "Engine": "aurora-postgresql",
        "EngineVersion": "17.7",
        "Port": 5432,
        "MasterUsername": "postgres",
        "PreferredBackupWindow": "06:15-06:45",
        "PreferredMaintenanceWindow": "sat:03:44-sat:04:14",
        "ReadReplicaIdentifiers": [],
        "DBClusterMembers": [
            {
                "DBInstanceIdentifier": "sample-cluster-instance-1",
                "IsClusterWriter": false,
                "DBClusterParameterGroupStatus": "in-sync",
                "PromotionTier": 1
            }
        ],
        "VpcSecurityGroups": [],
        "StorageEncrypted": false,
        "DbClusterResourceId": "cluster-EXAMPLE4RESOURCE",
        "DBClusterArn": "arn:aws:rds:us-east-1:123456789012:cluster:sample-cluster",
        "AssociatedRoles": [],
        "IAMDatabaseAuthenticationEnabled": true,
        "ClusterCreateTime": "2026-01-10T22:14:02Z",
        "EngineMode": "provisioned",
        "AutoMinorVersionUpgrade": true,
        "DeletionProtection": false,
        "HttpEndpointEnabled": false,
        "CopyTagsToSnapshot": false,
        "CrossAccountClone": false,
        "DomainMemberships": [],
        "TagList": [],
        "ServerlessV2ScalingConfiguration": {
            "MinCapacity": 0.0,
            "MaxCapacity": 16.0,
            "SecondsUntilAutoPause": 300
        },
        "ServerlessV2PlatformVersion": "3",
        "DatabaseInsightsMode": "standard",
        "PerformanceInsightsEnabled": false,
        "LocalWriteForwardingStatus": "disabled",
        "EngineLifecycleSupport": "open-source-rds-extended-support"
    }
}

Untuk informasi selengkapnya, lihat Membuat cluster Amazon Aurora DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CreateDbCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-db-instance-read-replica.

AWS CLI

Untuk membuat instance DB baca replika

Contoh ini membuat replika baca dari instance DB yang ada bernamatest-instance. Replika yang dibaca diberi namatest-instance-repl.


aws rds create-db-instance-read-replica \
    --db-instance-identifier test-instance-repl \
    --source-db-instance-identifier test-instance

Output:


{
    "DBInstance": {
        "IAMDatabaseAuthenticationEnabled": false,
        "MonitoringInterval": 0,
        "DBInstanceArn": "arn:aws:rds:us-east-1:123456789012:db:test-instance-repl",
        "ReadReplicaSourceDBInstanceIdentifier": "test-instance",
        "DBInstanceIdentifier": "test-instance-repl",
        ...some output truncated...
    }
}

Untuk detail API, lihat CreateDbInstanceReadReplica di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-db-instance.

AWS CLI

Untuk membuat instance DB

create-db-instanceContoh berikut menggunakan opsi yang diperlukan untuk meluncurkan instance DB baru.


aws rds create-db-instance \
    --db-instance-identifier test-mysql-instance \
    --db-instance-class db.t3.micro \
    --engine mysql \
    --master-username admin \
    --master-user-password secret99 \
    --allocated-storage 20

Output:


{
    "DBInstance": {
        "DBInstanceIdentifier": "test-mysql-instance",
        "DBInstanceClass": "db.t3.micro",
        "Engine": "mysql",
        "DBInstanceStatus": "creating",
        "MasterUsername": "admin",
        "AllocatedStorage": 20,
        "PreferredBackupWindow": "12:55-13:25",
        "BackupRetentionPeriod": 1,
        "DBSecurityGroups": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sg-12345abc",
                "Status": "active"
            }
        ],
        "DBParameterGroups": [
            {
                "DBParameterGroupName": "default.mysql5.7",
                "ParameterApplyStatus": "in-sync"
            }
        ],
        "DBSubnetGroup": {
            "DBSubnetGroupName": "default",
            "DBSubnetGroupDescription": "default",
            "VpcId": "vpc-2ff2ff2f",
            "SubnetGroupStatus": "Complete",
            "Subnets": [
                {
                    "SubnetIdentifier": "subnet-########",
                    "SubnetAvailabilityZone": {
                        "Name": "us-west-2c"
                    },
                    "SubnetStatus": "Active"
                },
                {
                    "SubnetIdentifier": "subnet-########",
                    "SubnetAvailabilityZone": {
                        "Name": "us-west-2d"
                    },
                    "SubnetStatus": "Active"
                },
                {
                    "SubnetIdentifier": "subnet-########",
                    "SubnetAvailabilityZone": {
                        "Name": "us-west-2a"
                    },
                    "SubnetStatus": "Active"
                },
                {
                    "SubnetIdentifier": "subnet-########",
                    "SubnetAvailabilityZone": {
                        "Name": "us-west-2b"
                    },
                    "SubnetStatus": "Active"
                }
            ]
        },
        "PreferredMaintenanceWindow": "sun:08:07-sun:08:37",
        "PendingModifiedValues": {
            "MasterUserPassword": "****"
        },
        "MultiAZ": false,
        "EngineVersion": "5.7.22",
        "AutoMinorVersionUpgrade": true,
        "ReadReplicaDBInstanceIdentifiers": [],
        "LicenseModel": "general-public-license",
        "OptionGroupMemberships": [
            {
                "OptionGroupName": "default:mysql-5-7",
                "Status": "in-sync"
            }
        ],
        "PubliclyAccessible": true,
        "StorageType": "gp2",
        "DbInstancePort": 0,
        "StorageEncrypted": false,
        "DbiResourceId": "db-5555EXAMPLE44444444EXAMPLE",
        "CACertificateIdentifier": "rds-ca-2019",
        "DomainMemberships": [],
        "CopyTagsToSnapshot": false,
        "MonitoringInterval": 0,
        "DBInstanceArn": "arn:aws:rds:us-west-2:123456789012:db:test-mysql-instance",
        "IAMDatabaseAuthenticationEnabled": false,
        "PerformanceInsightsEnabled": false,
        "DeletionProtection": false,
        "AssociatedRoles": []
    }
}

Untuk informasi selengkapnya, lihat Membuat Instans DB Amazon RDS di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat CreatedBInst ance di Referensi Perintah. AWS CLI

Contoh kode berikut menunjukkan cara menggunakancreate-db-parameter-group.

AWS CLI

Untuk membuat grup parameter DB

create-db-parameter-groupContoh berikut membuat grup parameter DB.


aws rds create-db-parameter-group \
    --db-parameter-group-name mydbparametergroup \
    --db-parameter-group-family MySQL5.6 \
    --description "My new parameter group"

Output:


{
    "DBParameterGroup": {
        "DBParameterGroupName": "mydbparametergroup",
        "DBParameterGroupFamily": "mysql5.6",
        "Description": "My new parameter group",
        "DBParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:pg:mydbparametergroup"
    }
}

Untuk informasi selengkapnya, lihat Membuat Grup Parameter DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat CreateDBParameterGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-db-proxy-endpoint.

AWS CLI

Untuk membuat titik akhir proxy DB untuk database RDS

create-db-proxy-endpointContoh berikut membuat titik akhir proxy DB.


aws rds create-db-proxy-endpoint \
    --db-proxy-name proxyExample \
    --db-proxy-endpoint-name "proxyep1" \
    --vpc-subnet-ids subnetgroup1 subnetgroup2

Output:


{
"DBProxyEndpoint": {
        "DBProxyEndpointName": "proxyep1",
        "DBProxyEndpointArn": "arn:aws:rds:us-east-1:123456789012:db-proxy-endpoint:prx-endpoint-0123a01b12345c0ab",
        "DBProxyName": "proxyExample",
        "Status": "creating",
        "VpcId": "vpc-1234567",
        "VpcSecurityGroupIds": [
            "sg-1234",
            "sg-5678"
        ],
        "VpcSubnetIds": [
            "subnetgroup1",
            "subnetgroup2"
        ],
        "Endpoint": "proxyep1.endpoint.proxy-ab0cd1efghij.us-east-1.rds.amazonaws.com",
        "CreatedDate": "2023-04-05T16:09:33.452000+00:00",
        "TargetRole": "READ_WRITE",
        "IsDefault": false
    }
}

Untuk informasi selengkapnya, lihat Membuat titik akhir proxy di Panduan Pengguna Amazon RDS dan Membuat titik akhir proxy di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CreateDbProxyEndpoint di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-db-proxy.

AWS CLI

Untuk membuat proxy DB untuk database RDS

create-db-proxyContoh berikut membuat proxy DB.


aws rds create-db-proxy \
    --db-proxy-name proxyExample \
    --engine-family MYSQL \
    --auth Description="proxydescription1",AuthScheme="SECRETS",SecretArn="arn:aws:secretsmanager:us-west-2:123456789123:secret:secretName-1234f",IAMAuth="DISABLED",ClientPasswordAuthType="MYSQL_NATIVE_PASSWORD" \
    --role-arn arn:aws:iam::123456789123:role/ProxyRole \
    --vpc-subnet-ids subnetgroup1 subnetgroup2

Output:


{
"DBProxy": {
        "DBProxyName": "proxyExample",
        "DBProxyArn": "arn:aws:rds:us-east-1:123456789012:db-proxy:prx-0123a01b12345c0ab",
        "EngineFamily": "MYSQL",
        "VpcId": "vpc-1234567",
        "VpcSecuritytGroupIds": [
            "sg-1234",
            "sg-5678",
            "sg-9101"
        ],
        "VpcSubnetIds": [
            "subnetgroup1",
            "subnetgroup2"
        ],
        "Auth": "[
            {
                "Description": "proxydescription1",
                "AuthScheme": "SECRETS",
                "SecretArn": "arn:aws:secretsmanager:us-west-2:123456789123:secret:proxysecret1-Abcd1e",
                "IAMAuth": "DISABLED"
            }
        ]",
        "RoleArn": "arn:aws:iam::12345678912:role/ProxyRole",
        "Endpoint": "proxyExample.proxy-ab0cd1efghij.us-east-1.rds.amazonaws.com",
        "RequireTLS": false,
        "IdleClientTimeout": 1800,
        "DebuggingLogging": false,
        "CreatedDate": "2023-04-05T16:09:33.452000+00:00",
        "UpdatedDate": "2023-04-13T01:49:38.568000+00:00"
    }
}

Untuk informasi selengkapnya, lihat Membuat Proksi RDS di Panduan Pengguna Amazon RDS dan Membuat Proksi RDS di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CreateDbProxy di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-db-security-group.

AWS CLI

Cara membuat grup keamanan Amazon RDS DB

Per create-db-security-group intah berikut membuat grup keamanan Amazon RDS DB baru:


aws rds create-db-security-group --db-security-group-name mysecgroup --db-security-group-description "My Test Security Group"

Dalam contoh, grup keamanan DB baru diberi nama mysecgroup dan memiliki deskripsi.

Output:


{
    "DBSecurityGroup": {
        "OwnerId": "123456789012",
        "DBSecurityGroupName": "mysecgroup",
        "DBSecurityGroupDescription": "My Test Security Group",
        "VpcId": "vpc-a1b2c3d4",
        "EC2SecurityGroups": [],
        "IPRanges": [],
        "DBSecurityGroupArn": "arn:aws:rds:us-west-2:123456789012:secgrp:mysecgroup"
    }
}

Untuk detail API, lihat CreateDbSecurityGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-db-shard-group.

AWS CLI

Contoh 1: Untuk membuat cluster DB primer Aurora PostgreSQL

create-db-clusterContoh berikut membuat cluster DB primer SQL Aurora PostgreSQL yang kompatibel dengan Aurora Serverless v2 dan Aurora Limitless Database.


aws rds create-db-cluster \
    --db-cluster-identifier my-sv2-cluster \
    --engine aurora-postgresql \
    --engine-version 15.2-limitless \
    --storage-type aurora-iopt1 \
    --serverless-v2-scaling-configuration MinCapacity=2,MaxCapacity=16 \
    --enable-limitless-database \
    --master-username myuser \
    --master-user-password mypassword \
    --enable-cloudwatch-logs-exports postgresql

Output:


{
    "DBCluster": {
        "AllocatedStorage": 1,
        "AvailabilityZones": [
            "us-east-2b",
            "us-east-2c",
            "us-east-2a"
        ],
        "BackupRetentionPeriod": 1,
        "DBClusterIdentifier": "my-sv2-cluster",
        "DBClusterParameterGroup": "default.aurora-postgresql15",
        "DBSubnetGroup": "default",
        "Status": "creating",
        "Endpoint": "my-sv2-cluster.cluster-cekycexample.us-east-2.rds.amazonaws.com",
        "ReaderEndpoint": "my-sv2-cluster.cluster-ro-cekycexample.us-east-2.rds.amazonaws.com",
        "MultiAZ": false,
        "Engine": "aurora-postgresql",
        "EngineVersion": "15.2-limitless",
        "Port": 5432,
        "MasterUsername": "myuser",
        "PreferredBackupWindow": "06:05-06:35",
        "PreferredMaintenanceWindow": "mon:08:25-mon:08:55",
        "ReadReplicaIdentifiers": [],
        "DBClusterMembers": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sg-########",
                "Status": "active"
            }
        ],
        "HostedZoneId": "Z2XHWR1EXAMPLE",
        "StorageEncrypted": false,
        "DbClusterResourceId": "cluster-XYEDT6ML6FHIXH4Q2J1EXAMPLE",
        "DBClusterArn": "arn:aws:rds:us-east-2:123456789012:cluster:my-sv2-cluster",
        "AssociatedRoles": [],
        "IAMDatabaseAuthenticationEnabled": false,
        "ClusterCreateTime": "2024-02-19T16:24:07.771000+00:00",
        "EnabledCloudwatchLogsExports": [
            "postgresql"
        ],
        "EngineMode": "provisioned",
        "DeletionProtection": false,
        "HttpEndpointEnabled": false,
        "CopyTagsToSnapshot": false,
        "CrossAccountClone": false,
        "DomainMemberships": [],
        "TagList": [],
        "StorageType": "aurora-iopt1",
        "AutoMinorVersionUpgrade": true,
        "ServerlessV2ScalingConfiguration": {
            "MinCapacity": 2.0,
            "MaxCapacity": 16.0
        },
        "NetworkType": "IPV4",
        "IOOptimizedNextAllowedModificationTime": "2024-03-21T16:24:07.781000+00:00",
        "LimitlessDatabase": {
            "Status": "not-in-use",
            "MinRequiredACU": 96.0
        }
    }
}

Contoh 2: Untuk membuat instance DB primer (penulis)

create-db-instanceContoh berikut membuat instance DB primer (penulis) Aurora Serverless v2. Saat Anda menggunakan konsol untuk membuat cluster DB, Amazon RDS secara otomatis membuat instance DB penulis untuk cluster DB Anda. Namun, ketika Anda menggunakan AWS CLI untuk membuat cluster DB, Anda harus secara eksplisit membuat instance Writer DB untuk cluster DB Anda menggunakan perintah create-db-instance AWS CLI.


aws rds create-db-instance \
    --db-instance-identifier my-sv2-instance \
    --db-cluster-identifier my-sv2-cluster \
    --engine aurora-postgresql \
    --db-instance-class db.serverless

Output:


{
    "DBInstance": {
        "DBInstanceIdentifier": "my-sv2-instance",
        "DBInstanceClass": "db.serverless",
        "Engine": "aurora-postgresql",
        "DBInstanceStatus": "creating",
        "MasterUsername": "myuser",
        "AllocatedStorage": 1,
        "PreferredBackupWindow": "06:05-06:35",
        "BackupRetentionPeriod": 1,
        "DBSecurityGroups": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sg-########",
                "Status": "active"
            }
        ],
        "DBParameterGroups": [
            {
                "DBParameterGroupName": "default.aurora-postgresql15",
                "ParameterApplyStatus": "in-sync"
            }
        ],
        "DBSubnetGroup": {
            "DBSubnetGroupName": "default",
            "DBSubnetGroupDescription": "default",
            "VpcId": "vpc-########",
            "SubnetGroupStatus": "Complete",
            "Subnets": [
                {
                    "SubnetIdentifier": "subnet-########",
                    "SubnetAvailabilityZone": {
                        "Name": "us-east-2c"
                    },
                    "SubnetOutpost": {},
                    "SubnetStatus": "Active"
                },
                {
                    "SubnetIdentifier": "subnet-########",
                    "SubnetAvailabilityZone": {
                        "Name": "us-east-2a"
                    },
                    "SubnetOutpost": {},
                    "SubnetStatus": "Active"
                },
                {
                    "SubnetIdentifier": "subnet-########",
                    "SubnetAvailabilityZone": {
                        "Name": "us-east-2b"
                    },
                    "SubnetOutpost": {},
                    "SubnetStatus": "Active"
                }
            ]
        },
        "PreferredMaintenanceWindow": "fri:09:01-fri:09:31",
        "PendingModifiedValues": {
            "PendingCloudwatchLogsExports": {
                "LogTypesToEnable": [
                    "postgresql"
                ]
            }
        },
        "MultiAZ": false,
        "EngineVersion": "15.2-limitless",
        "AutoMinorVersionUpgrade": true,
        "ReadReplicaDBInstanceIdentifiers": [],
        "LicenseModel": "postgresql-license",
        "OptionGroupMemberships": [
            {
                "OptionGroupName": "default:aurora-postgresql-15",
                "Status": "in-sync"
            }
        ],
        "PubliclyAccessible": false,
        "StorageType": "aurora-iopt1",
        "DbInstancePort": 0,
        "DBClusterIdentifier": "my-sv2-cluster",
        "StorageEncrypted": false,
        "DbiResourceId": "db-BIQTE3B3K3RM7M74SK5EXAMPLE",
        "CACertificateIdentifier": "rds-ca-rsa2048-g1",
        "DomainMemberships": [],
        "CopyTagsToSnapshot": false,
        "MonitoringInterval": 0,
        "PromotionTier": 1,
        "DBInstanceArn": "arn:aws:rds:us-east-2:123456789012:db:my-sv2-instance",
        "IAMDatabaseAuthenticationEnabled": false,
        "PerformanceInsightsEnabled": false,
        "DeletionProtection": false,
        "AssociatedRoles": [],
        "TagList": [],
        "CustomerOwnedIpEnabled": false,
        "BackupTarget": "region",
        "NetworkType": "IPV4",
        "StorageThroughput": 0,
        "CertificateDetails": {
            "CAIdentifier": "rds-ca-rsa2048-g1"
        },
        "DedicatedLogVolume": false
    }
}

Contoh 3: Untuk membuat grup pecahan DB

create-db-shard-groupContoh berikut membuat grup pecahan DB di cluster DB utama Aurora PostgreSQL Anda.


aws rds create-db-shard-group \
    --db-shard-group-identifier my-db-shard-group \
    --db-cluster-identifier my-sv2-cluster \
    --max-acu 768

Output:


{
    "DBShardGroupResourceId": "shardgroup-a6e3a0226aa243e2ac6c7a1234567890",
    "DBShardGroupIdentifier": "my-db-shard-group",
    "DBClusterIdentifier": "my-sv2-cluster",
    "MaxACU": 768.0,
    "ComputeRedundancy": 0,
    "Status": "creating",
    "PubliclyAccessible": false,
    "Endpoint": "my-sv2-cluster.limitless-cekycexample.us-east-2.rds.amazonaws.com"
}

Untuk informasi selengkapnya, lihat Menggunakan Aurora Serverless v2 di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CreateDbShardGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-db-snapshot.

AWS CLI

Untuk membuat snapshot DB

create-db-snapshotContoh berikut membuat snapshot DB.


aws rds create-db-snapshot \
    --db-instance-identifier database-mysql \
    --db-snapshot-identifier mydbsnapshot

Output:


{
    "DBSnapshot": {
        "DBSnapshotIdentifier": "mydbsnapshot",
        "DBInstanceIdentifier": "database-mysql",
        "Engine": "mysql",
        "AllocatedStorage": 100,
        "Status": "creating",
        "Port": 3306,
        "AvailabilityZone": "us-east-1b",
        "VpcId": "vpc-6594f31c",
        "InstanceCreateTime": "2019-04-30T15:45:53.663Z",
        "MasterUsername": "admin",
        "EngineVersion": "5.6.40",
        "LicenseModel": "general-public-license",
        "SnapshotType": "manual",
        "Iops": 1000,
        "OptionGroupName": "default:mysql-5-6",
        "PercentProgress": 0,
        "StorageType": "io1",
        "Encrypted": true,
        "KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/AKIAIOSFODNN7EXAMPLE",
        "DBSnapshotArn": "arn:aws:rds:us-east-1:123456789012:snapshot:mydbsnapshot",
        "IAMDatabaseAuthenticationEnabled": false,
        "ProcessorFeatures": [],
        "DbiResourceId": "db-AKIAIOSFODNN7EXAMPLE"
    }
}

Untuk informasi selengkapnya, lihat Membuat Snapshot DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat CreatedBSnapshot di Referensi Perintah. AWS CLI

Contoh kode berikut menunjukkan cara menggunakancreate-db-subnet-group.

AWS CLI

Untuk membuat grup subnet DB

create-db-subnet-groupContoh berikut membuat grup subnet DB yang disebut mysubnetgroup menggunakan subnet yang ada.


aws rds create-db-subnet-group \
    --db-subnet-group-name mysubnetgroup \
    --db-subnet-group-description "test DB subnet group" \
    --subnet-ids '["subnet-0a1dc4e1a6f123456","subnet-070dd7ecb3aaaaaaa","subnet-00f5b198bc0abcdef"]'

Output:


{
    "DBSubnetGroup": {
        "DBSubnetGroupName": "mysubnetgroup",
        "DBSubnetGroupDescription": "test DB subnet group",
        "VpcId": "vpc-0f08e7610a1b2c3d4",
        "SubnetGroupStatus": "Complete",
        "Subnets": [
            {
                "SubnetIdentifier": "subnet-070dd7ecb3aaaaaaa",
                "SubnetAvailabilityZone": {
                    "Name": "us-west-2b"
                },
                "SubnetStatus": "Active"
            },
            {
                "SubnetIdentifier": "subnet-00f5b198bc0abcdef",
                "SubnetAvailabilityZone": {
                    "Name": "us-west-2d"
                },
                "SubnetStatus": "Active"
            },
            {
                "SubnetIdentifier": "subnet-0a1dc4e1a6f123456",
                "SubnetAvailabilityZone": {
                    "Name": "us-west-2b"
                },
                "SubnetStatus": "Active"
            }
        ],
        "DBSubnetGroupArn": "arn:aws:rds:us-west-2:0123456789012:subgrp:mysubnetgroup"
    }
}

Untuk informasi selengkapnya, lihat Membuat Instans DB di VPC di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat CreateDbSubnetGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-event-subscription.

AWS CLI

Untuk membuat langganan acara

create-event-subscriptionContoh berikut membuat langganan untuk acara pencadangan dan pemulihan untuk instans DB di AWS akun saat ini. Pemberitahuan dikirim ke topik Layanan Pemberitahuan Sederhana Amazon, yang ditentukan oleh--sns-topic-arn.


aws rds create-event-subscription \
    --subscription-name my-instance-events \
    --source-type db-instance \
    --event-categories '["backup","recovery"]' \
    --sns-topic-arn arn:aws:sns:us-east-1:123456789012:interesting-events

Output:


{
    "EventSubscription": {
        "Status": "creating",
        "CustSubscriptionId": "my-instance-events",
        "SubscriptionCreationTime": "Tue Jul 31 23:22:01 UTC 2018",
        "EventCategoriesList": [
            "backup",
            "recovery"
        ],
        "SnsTopicArn": "arn:aws:sns:us-east-1:123456789012:interesting-events",
        "CustomerAwsId": "123456789012",
        "EventSubscriptionArn": "arn:aws:rds:us-east-1:123456789012:es:my-instance-events",
        "SourceType": "db-instance",
        "Enabled": true
    }
}

Untuk detail API, lihat CreateEventSubscription di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-global-cluster.

AWS CLI

Untuk membuat cluster DB global

create-global-clusterContoh berikut membuat cluster DB MySQL-compatible global Aurora baru.


aws rds create-global-cluster \
    --global-cluster-identifier myglobalcluster \
    --engine aurora-mysql

Output:


{
    "GlobalCluster": {
        "GlobalClusterIdentifier": "myglobalcluster",
        "GlobalClusterResourceId": "cluster-f0e523bfe07aabb",
        "GlobalClusterArn": "arn:aws:rds::123456789012:global-cluster:myglobalcluster",
        "Status": "available",
        "Engine": "aurora-mysql",
        "EngineVersion": "5.7.mysql_aurora.2.07.2",
        "StorageEncrypted": false,
        "DeletionProtection": false,
        "GlobalClusterMembers": []
    }
}

Untuk informasi selengkapnya, lihat Membuat database global Aurora di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat CreateGlobalCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakancreate-option-group.

AWS CLI

Cara Membuat grup opsi Amazon RDS

Per create-option-group intah berikut membuat grup opsi Amazon RDS baru untuk Oracle Enterprise Edition versi 11.2`, is named ``MyOptionGroup dan menyertakan deskripsi.


aws rds create-option-group \
    --option-group-name MyOptionGroup \
    --engine-name oracle-ee \
    --major-engine-version 11.2 \
    --option-group-description "Oracle Database Manager Database Control"

Output:


{
    "OptionGroup": {
        "OptionGroupName": "myoptiongroup",
        "OptionGroupDescription": "Oracle Database Manager Database Control",
        "EngineName": "oracle-ee",
        "MajorEngineVersion": "11.2",
        "Options": [],
        "AllowsVpcAndNonVpcInstanceMemberships": true,
        "OptionGroupArn": "arn:aws:rds:us-west-2:123456789012:og:myoptiongroup"
    }
}

Untuk detail API, lihat CreateOptionGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-blue-green-deployment.

AWS CLI

Contoh 1: Untuk menghapus sumber daya di lingkungan hijau untuk RDS untuk instance MySQL DB

delete-blue-green-deploymentContoh berikut menghapus sumber daya di lingkungan hijau untuk RDS untuk instance MySQL DB.


aws rds delete-blue-green-deployment \
    --blue-green-deployment-identifier bgd-v53303651eexfake \
    --delete-target

Output:


{
    "BlueGreenDeployment": {
        "BlueGreenDeploymentIdentifier": "bgd-v53303651eexfake",
        "BlueGreenDeploymentName": "bgd-cli-test-instance",
        "Source": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance",
        "Target": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-green-rkfbpe",
        "SwitchoverDetails": [
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-green-rkfbpe",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-1",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-1-green-j382ha",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-2",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-2-green-ejv4ao",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-3",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-3-green-vlpz3t",
                "Status": "AVAILABLE"
            }
        ],
        "Tasks": [
            {
                "Name": "CREATING_READ_REPLICA_OF_SOURCE",
                "Status": "COMPLETED"
            },
            {
                "Name": "DB_ENGINE_VERSION_UPGRADE",
                "Status": "COMPLETED"
            },
            {
                "Name": "CONFIGURE_BACKUPS",
                "Status": "COMPLETED"
            },
            {
                "Name": "CREATING_TOPOLOGY_OF_SOURCE",
                "Status": "COMPLETED"
            }
        ],
        "Status": "DELETING",
        "CreateTime": "2022-02-25T21:18:51.183000+00:00",
        "DeleteTime": "2022-02-25T22:25:31.331000+00:00"
    }
}

Untuk informasi selengkapnya, lihat Menghapus blue/green pener apan di Panduan Pengguna Amazon RDS.

Contoh 2: Untuk menghapus sumber daya di lingkungan hijau untuk cluster Aurora MySQL DB

delete-blue-green-deploymentContoh berikut menghapus sumber daya di lingkungan hijau untuk cluster Aurora MySQL DB.


aws rds delete-blue-green-deployment \
    --blue-green-deployment-identifier bgd-wi89nwzglccsfake \
    --delete-target

Output:


{
    "BlueGreenDeployment": {
        "BlueGreenDeploymentIdentifier": "bgd-wi89nwzglccsfake",
        "BlueGreenDeploymentName": "my-blue-green-deployment",
        "Source": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
        "Target": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster-green-3rnukl",
        "SwitchoverDetails": [
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster-green-3rnukl",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-1",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-1-green-gpmaxf",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-2",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-2-green-j2oajq",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-3",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-3-green-mkxies",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-excluded-member-endpoint",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-excluded-member-endpoint-green-4sqjrq",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-reader-endpoint",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-reader-endpoint-green-gwwzlg",
                "Status": "AVAILABLE"
            }
        ],
        "Tasks": [
            {
                "Name": "CREATING_READ_REPLICA_OF_SOURCE",
                "Status": "COMPLETED"
            },
            {
                "Name": "DB_ENGINE_VERSION_UPGRADE",
                "Status": "COMPLETED"
            },
            {
                "Name": "CREATE_DB_INSTANCES_FOR_CLUSTER",
                "Status": "COMPLETED"
            },
            {
                "Name": "CREATE_CUSTOM_ENDPOINTS",
                "Status": "COMPLETED"
            }
        ],
        "Status": "DELETING",
        "CreateTime": "2022-02-25T21:12:00.288000+00:00",
        "DeleteTime": "2022-02-25T22:29:11.336000+00:00"
    }
}

Untuk informasi selengkapnya, lihat Mengh blue/green apus penerapan di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DeleteBlueGreenDeployment di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-cluster-endpoint.

AWS CLI

Untuk menghapus titik akhir cluster DB kustom

delete-db-cluster-endpointContoh berikut menghapus titik akhir cluster DB kustom yang ditentukan.


aws rds delete-db-cluster-endpoint \
    --db-cluster-endpoint-identifier mycustomendpoint

Output:


{
    "DBClusterEndpointIdentifier": "mycustomendpoint",
    "DBClusterIdentifier": "mydbcluster",
    "DBClusterEndpointResourceIdentifier": "cluster-endpoint-ANPAJ4AE5446DAEXAMPLE",
    "Endpoint": "mycustomendpoint.cluster-custom-cnpexample.us-east-1.rds.amazonaws.com",
    "Status": "deleting",
    "EndpointType": "CUSTOM",
    "CustomEndpointType": "READER",
    "StaticMembers": [
        "dbinstance1",
        "dbinstance2",
        "dbinstance3"
    ],
    "ExcludedMembers": [],
    "DBClusterEndpointArn": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:mycustomendpoint"
}

Untuk informasi selengkapnya, lihat Manajemen Koneksi Amazon Aurora di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DeleteDbClusterEndpoint di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-cluster-parameter-group.

AWS CLI

Untuk menghapus grup parameter cluster DB

delete-db-cluster-parameter-groupContoh berikut menghapus grup parameter cluster DB yang ditentukan.


aws rds delete-db-cluster-parameter-group \
    --db-cluster-parameter-group-name mydbclusterparametergroup

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Bek erja dengan Grup Parameter DB dan Grup Parameter Cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DeleteDbClusterParameterGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-cluster-snapshot.

AWS CLI

Untuk menghapus snapshot cluster DB

delete-db-cluster-snapshotContoh berikut menghapus snapshot cluster DB yang ditentukan.


aws rds delete-db-cluster-snapshot \
    --db-cluster-snapshot-identifier mydbclustersnapshot

Output:


{
    "DBClusterSnapshot": {
        "AvailabilityZones": [
            "us-east-1a",
            "us-east-1b",
            "us-east-1e"
        ],
        "DBClusterSnapshotIdentifier": "mydbclustersnapshot",
        "DBClusterIdentifier": "mydbcluster",
        "SnapshotCreateTime": "2019-06-18T21:21:00.469Z",
        "Engine": "aurora-mysql",
        "AllocatedStorage": 0,
        "Status": "available",
        "Port": 0,
        "VpcId": "vpc-6594f31c",
        "ClusterCreateTime": "2019-04-15T14:18:42.785Z",
        "MasterUsername": "myadmin",
        "EngineVersion": "5.7.mysql_aurora.2.04.2",
        "LicenseModel": "aurora-mysql",
        "SnapshotType": "manual",
        "PercentProgress": 100,
        "StorageEncrypted": true,
        "KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/AKIAIOSFODNN7EXAMPLE",
        "DBClusterSnapshotArn": "arn:aws:rds:us-east-1:123456789012:cluster-snapshot:mydbclustersnapshot",
        "IAMDatabaseAuthenticationEnabled": false
    }
}

Untuk informasi selengkapnya, lihat Menghapus Snapshot di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DeleteDbClusterSnapshot di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-cluster.

AWS CLI

Contoh 1: Untuk menghapus instans DB di cluster DB

delete-db-instanceContoh berikut menghapus instance DB akhir dalam cluster DB. Anda tidak dapat menghapus cluster DB jika berisi instance DB yang tidak dalam status pengh ap usan. Anda tidak dapat mengambil snapshot akhir saat menghapus instans DB di cluster DB.


aws rds delete-db-instance \
    --db-instance-identifier database-3

Output:


{
    "DBInstance": {
        "DBInstanceIdentifier": "database-3",
        "DBInstanceClass": "db.r4.large",
        "Engine": "aurora-postgresql",
        "DBInstanceStatus": "deleting",

    ...output omitted...

    }
}

Untuk informasi selengkapnya, lihat Menghapus Instans DB di Cluster DB Aurora di Panduan Pengguna Amazon Aurora.

Contoh 2: Untuk menghapus cluster DB

delete-db-clusterContoh berikut menghapus cluster DB bernama mycluster dan mengambil snapshot akhir bernamamycluster-final-snapshot. Status cluster DB tersedia saat snapshot sedang diambil. Untuk mengikuti kemajuan penghapusan, gunakan perintah describe-db-clusters CLI.


aws rds delete-db-cluster \
    --db-cluster-identifier mycluster \
    --no-skip-final-snapshot \
    --final-db-snapshot-identifier mycluster-final-snapshot

Output:


{
    "DBCluster": {
        "AllocatedStorage": 20,
        "AvailabilityZones": [
            "eu-central-1b",
            "eu-central-1c",
            "eu-central-1a"
        ],
        "BackupRetentionPeriod": 7,
        "DBClusterIdentifier": "mycluster",
        "DBClusterParameterGroup": "default.aurora-postgresql10",
        "DBSubnetGroup": "default-vpc-aa11bb22",
        "Status": "available",

    ...output omitted...

    }
}

Untuk informasi selengkapnya, lihat Cluster Aurora dengan Instans DB Tunggal di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DeleteDbCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-instance-automated-backup.

AWS CLI

Untuk menghapus cadangan otomatis yang direplikasi dari Wilayah

delete-db-instance-automated-backupContoh berikut menghapus cadangan otomatis dengan Nama Sumber Daya Amazon (ARN) yang ditentukan.


aws rds delete-db-instance-automated-backup \
    --db-instance-automated-backups-arn "arn:aws:rds:us-west-2:123456789012:auto-backup:ab-jkib2gfq5rv7replzadausbrktni2bn4example"

Output:


{
    "DBInstanceAutomatedBackup": {
        "DBInstanceArn": "arn:aws:rds:us-east-1:123456789012:db:new-orcl-db",
        "DbiResourceId": "db-JKIB2GFQ5RV7REPLZA4EXAMPLE",
        "Region": "us-east-1",
        "DBInstanceIdentifier": "new-orcl-db",
        "RestoreWindow": {},
        "AllocatedStorage": 20,
        "Status": "deleting",
        "Port": 1521,
        "AvailabilityZone": "us-east-1b",
        "VpcId": "vpc-########",
        "InstanceCreateTime": "2020-12-04T15:28:31Z",
        "MasterUsername": "admin",
        "Engine": "oracle-se2",
        "EngineVersion": "12.1.0.2.v21",
        "LicenseModel": "bring-your-own-license",
        "OptionGroupName": "default:oracle-se2-12-1",
        "Encrypted": false,
        "StorageType": "gp2",
        "IAMDatabaseAuthenticationEnabled": false,
        "BackupRetentionPeriod": 7,
        "DBInstanceAutomatedBackupsArn": "arn:aws:rds:us-west-2:123456789012:auto-backup:ab-jkib2gfq5rv7replzadausbrktni2bn4example"
    }
}

Untuk informasi selengkapnya, lihat Menghapus cadangan yang direplikasi di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DeleteDbInstanceAutomatedBackup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-instance.

AWS CLI

Untuk menghapus instans DB

delete-db-instanceContoh berikut menghapus instance DB yang ditentukan setelah membuat snapshot DB akhir bernamatest-instance-final-snap.


aws rds delete-db-instance \
    --db-instance-identifier test-instance \
    --final-db-snapshot-identifier test-instance-final-snap

Output:


{
    "DBInstance": {
        "DBInstanceIdentifier": "test-instance",
        "DBInstanceStatus": "deleting",
        ...some output truncated...
    }
}

Untuk detail API, lihat DeleteDBInstance di AWS CLI Referensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-parameter-group.

AWS CLI

Untuk menghapus grup parameter DB

commandContoh berikut menghapus grup parameter DB.


aws rds delete-db-parameter-group \
    --db-parameter-group-name mydbparametergroup

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Bekerja dengan Grup Parameter DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DeleteDBParameterGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-proxy-endpoint.

AWS CLI

Untuk menghapus titik akhir proxy DB untuk database RDS

delete-db-proxy-endpointContoh berikut menghapus titik akhir proxy DB untuk database target.


aws rds delete-db-proxy-endpoint \
    --db-proxy-endpoint-name proxyEP1

Output:


{
"DBProxyEndpoint":
    {
        "DBProxyEndpointName": "proxyEP1",
        "DBProxyEndpointArn": "arn:aws:rds:us-east-1:123456789012:db-proxy-endpoint:prx-endpoint-0123a01b12345c0ab",
        "DBProxyName": "proxyExample",
        "Status": "deleting",
        "VpcId": "vpc-1234567",
        "VpcSecurityGroupIds": [
            "sg-1234",
            "sg-5678"
        ],
        "VpcSubnetIds": [
            "subnetgroup1",
            "subnetgroup2"
        ],
        "Endpoint": "proxyEP1.endpoint.proxy-ab0cd1efghij.us-east-1.rds.amazonaws.com",
        "CreatedDate": "2023-04-13T01:49:38.568000+00:00",
        "TargetRole": "READ_ONLY",
        "IsDefault": false
    }
}

Untuk informasi selengkapnya, lihat Menghapus titik akhir proxy di Panduan Pengguna Amazon RDS dan Menghapus titik akhir proxy di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DeleteDbProxyEndpoint di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-proxy.

AWS CLI

Untuk menghapus proxy DB untuk database RDS

delete-db-proxyContoh berikut menghapus proxy DB.


aws rds delete-db-proxy \
    --db-proxy-name proxyExample

Output:


{
        "DBProxy":
        {
            "DBProxyName": "proxyExample",
            "DBProxyArn": "arn:aws:rds:us-east-1:123456789012:db-proxy:prx-0123a01b12345c0ab",
            "Status": "deleting",
            "EngineFamily": "PostgreSQL",
            "VpcId": "vpc-1234567",
            "VpcSecurityGroupIds": [
                "sg-1234",
                "sg-5678"
            ],
            "VpcSubnetIds": [
                "subnetgroup1",
                "subnetgroup2"
            ],
            "Auth": "[
                {
                "Description": "proxydescription`"
                "AuthScheme": "SECRETS",
                "SecretArn": "arn:aws:secretsmanager:us-west-2:123456789123:secret:proxysecret1-Abcd1e",
                "IAMAuth": "DISABLED"
                } ],
            "RoleArn": "arn:aws:iam::12345678912:role/ProxyPostgreSQLRole",
            "Endpoint": "proxyExample.proxy-ab0cd1efghij.us-east-1.rds.amazonaws.com",
            "RequireTLS": false,
            "IdleClientTimeout": 1800,
            "DebuggingLogging": false,
        "CreatedDate": "2023-04-05T16:09:33.452000+00:00",
        "UpdatedDate": "2023-04-13T01:49:38.568000+00:00"
    }
}

Untuk informasi selengkapnya, lihat Menghapus Proxy RDS di Panduan Pengguna Amazon RDS dan Menghapus Proksi RDS di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DeleteDbProxy di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-security-group.

AWS CLI

Untuk menghapus grup keamanan DB

delete-db-security-groupContoh berikut menghapus grup keamanan DB bernamamysecuritygroup.


aws rds delete-db-security-group \
    --db-security-group-name mysecuritygroup

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Bek erja dengan grup keamanan DB (EC2-Classic platform) di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DeleteDbSecurityGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-shard-group.

AWS CLI

Contoh 1: Untuk menghapus grup pecahan DB tidak berhasil

delete-db-shard-groupContoh berikut menunjukkan kesalahan yang terjadi ketika Anda mencoba menghapus grup pecahan DB sebelum menghapus semua database dan skema Anda.


aws rds delete-db-shard-group \
    --db-shard-group-identifier limitless-test-shard-grp

Output:


An error occurred (InvalidDBShardGroupState) when calling the DeleteDBShardGroup operation: Unable to delete the DB shard group limitless-test-db-shard-group.
Delete all of your Limitless Database databases and schemas, then try again.

Contoh 2: Untuk menghapus grup pecahan DB dengan sukses

delete-db-shard-groupContoh berikut menghapus grup pecahan DB setelah Anda menghapus semua database dan skema Anda, termasuk skema. public


aws rds delete-db-shard-group \
    --db-shard-group-identifier limitless-test-shard-grp

Output:


{
    "DBShardGroupResourceId": "shardgroup-7bb446329da94788b3f957746example",
    "DBShardGroupIdentifier": "limitless-test-shard-grp",
    "DBClusterIdentifier": "limitless-test-cluster",
    "MaxACU": 768.0,
    "ComputeRedundancy": 0,
    "Status": "deleting",
    "PubliclyAccessible": true,
    "Endpoint": "limitless-test-cluster.limitless-cekycexample.us-east-2.rds.amazonaws.com"
}

Untuk informasi selengkapnya, lihat Menghapus cluster Aurora DB dan inst ans DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DeleteDbShardGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-snapshot.

AWS CLI

Untuk menghapus snapshot DB

delete-db-snapshotContoh berikut menghapus snapshot DB yang ditentukan.


aws rds delete-db-snapshot \
    --db-snapshot-identifier mydbsnapshot

Output:


{
    "DBSnapshot": {
        "DBSnapshotIdentifier": "mydbsnapshot",
        "DBInstanceIdentifier": "database-mysql",
        "SnapshotCreateTime": "2019-06-18T22:08:40.702Z",
        "Engine": "mysql",
        "AllocatedStorage": 100,
        "Status": "deleted",
        "Port": 3306,
        "AvailabilityZone": "us-east-1b",
        "VpcId": "vpc-6594f31c",
        "InstanceCreateTime": "2019-04-30T15:45:53.663Z",
        "MasterUsername": "admin",
        "EngineVersion": "5.6.40",
        "LicenseModel": "general-public-license",
        "SnapshotType": "manual",
        "Iops": 1000,
        "OptionGroupName": "default:mysql-5-6",
        "PercentProgress": 100,
        "StorageType": "io1",
        "Encrypted": true,
        "KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/AKIAIOSFODNN7EXAMPLE",
        "DBSnapshotArn": "arn:aws:rds:us-east-1:123456789012:snapshot:mydbsnapshot",
        "IAMDatabaseAuthenticationEnabled": false,
        "ProcessorFeatures": [],
        "DbiResourceId": "db-AKIAIOSFODNN7EXAMPLE"
    }
}

Untuk informasi selengkapnya, lihat Menghapus Snapshot di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DeleteDbSnapshot di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-db-subnet-group.

AWS CLI

Untuk menghapus grup subnet DB

delete-db-subnet-groupContoh berikut menghapus grup subnet DB yang dipanggil. mysubnetgroup


aws rds delete-db-subnet-group --db-subnet-group-name mysubnetgroup

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Bek erja dengan Instans DB di VPC di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DeleteDbSubnetGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-event-subscription.

AWS CLI

Untuk menghapus langganan acara

delete-event-subscriptionContoh berikut menghapus langganan acara yang ditentukan.


aws rds delete-event-subscription --subscription-name my-instance-events

Output:


{
    "EventSubscription": {
        "EventSubscriptionArn": "arn:aws:rds:us-east-1:123456789012:es:my-instance-events",
        "CustomerAwsId": "123456789012",
        "Enabled": false,
        "SourceIdsList": [
            "test-instance"
        ],
        "SourceType": "db-instance",
        "EventCategoriesList": [
            "backup",
            "recovery"
        ],
        "SubscriptionCreationTime": "2018-07-31 23:22:01.893",
        "CustSubscriptionId": "my-instance-events",
        "SnsTopicArn": "arn:aws:sns:us-east-1:123456789012:interesting-events",
        "Status": "deleting"
    }
}

Untuk detail API, lihat DeleteEventSubscription di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-global-cluster.

AWS CLI

Untuk menghapus cluster DB global

delete-global-clusterContoh berikut menghapus cluster DB MySQL-compatible global Aurora. Output menunjukkan cluster yang Anda hapus, tetapi describe-global-clusters perintah berikutnya tidak mencantumkan cluster DB itu.


aws rds delete-global-cluster \
    --global-cluster-identifier myglobalcluster

Output:


{
    "GlobalCluster": {
        "GlobalClusterIdentifier": "myglobalcluster",
        "GlobalClusterResourceId": "cluster-f0e523bfe07aabb",
        "GlobalClusterArn": "arn:aws:rds::123456789012:global-cluster:myglobalcluster",
        "Status": "available",
        "Engine": "aurora-mysql",
        "EngineVersion": "5.7.mysql_aurora.2.07.2",
        "StorageEncrypted": false,
        "DeletionProtection": false,
        "GlobalClusterMembers": []
    }
}

Untuk informasi selengkapnya, lihat Menghapus database global Aurora di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DeleteGlobalCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandelete-option-group.

AWS CLI

Untuk menghapus grup opsi

delete-option-groupContoh berikut menghapus grup opsi yang ditentukan.


aws rds delete-option-group \
    --option-group-name myoptiongroup

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Menghapus Grup Opsi di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DeleteOptionGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanderegister-db-proxy-targets.

AWS CLI

Untuk membatalkan pendaftaran target proxy DB dari kelompok target database

deregister-db-proxy-targetsContoh berikut menghapus hubungan antara proxy proxyExample dan targetnya.


aws rds deregister-db-proxy-targets \
    --db-proxy-name proxyExample \
    --db-instance-identifiers database-1

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Menghapus Proxy RDS di Panduan Pengguna Amazon RDS dan Menghapus Proksi RDS di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DeregisterDbProxyTargets di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-account-attributes.

AWS CLI

Untuk menjelaskan atribut akun

describe-account-attributesContoh berikut mengambil atribut untuk AWS akun saat ini.


aws rds describe-account-attributes

Output:


{
    "AccountQuotas": [
        {
            "Max": 40,
            "Used": 4,
            "AccountQuotaName": "DBInstances"
        },
        {
            "Max": 40,
            "Used": 0,
            "AccountQuotaName": "ReservedDBInstances"
        },
        {
            "Max": 100000,
            "Used": 40,
            "AccountQuotaName": "AllocatedStorage"
        },
        {
            "Max": 25,
            "Used": 0,
            "AccountQuotaName": "DBSecurityGroups"
        },
        {
            "Max": 20,
            "Used": 0,
            "AccountQuotaName": "AuthorizationsPerDBSecurityGroup"
        },
        {
            "Max": 50,
            "Used": 1,
            "AccountQuotaName": "DBParameterGroups"
        },
        {
            "Max": 100,
            "Used": 3,
            "AccountQuotaName": "ManualSnapshots"
        },
        {
            "Max": 20,
            "Used": 0,
            "AccountQuotaName": "EventSubscriptions"
        },
        {
            "Max": 50,
            "Used": 1,
            "AccountQuotaName": "DBSubnetGroups"
        },
        {
            "Max": 20,
            "Used": 1,
            "AccountQuotaName": "OptionGroups"
        },
        {
            "Max": 20,
            "Used": 6,
            "AccountQuotaName": "SubnetsPerDBSubnetGroup"
        },
        {
            "Max": 5,
            "Used": 0,
            "AccountQuotaName": "ReadReplicasPerMaster"
        },
        {
            "Max": 40,
            "Used": 1,
            "AccountQuotaName": "DBClusters"
        },
        {
            "Max": 50,
            "Used": 0,
            "AccountQuotaName": "DBClusterParameterGroups"
        },
        {
            "Max": 5,
            "Used": 0,
            "AccountQuotaName": "DBClusterRoles"
        }
    ]
}

Untuk detail API, lihat DescribeAccountAttributes di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-blue-green-deployments.

AWS CLI

Contoh 1: Untuk menjelaskan blue/green penerapan instance DB RDS setelah pembuatan selesai

describe-blue-green-deploymentContoh berikut mengambil detail penerapan setelah blue/green pembuatan selesai.


aws rds describe-blue-green-deployments \
    --blue-green-deployment-identifier bgd-v53303651eexfake

Output:


{
    "BlueGreenDeployments": [
        {
            "BlueGreenDeploymentIdentifier": "bgd-v53303651eexfake",
            "BlueGreenDeploymentName": "bgd-cli-test-instance",
            "Source": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance",
            "Target": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-green-rkfbpe",
            "SwitchoverDetails": [
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-green-rkfbpe",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-1-green-j382ha",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-2",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-2-green-ejv4ao",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-3",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-3-green-vlpz3t",
                    "Status": "AVAILABLE"
                }
            ],
            "Tasks": [
                {
                    "Name": "CREATING_READ_REPLICA_OF_SOURCE",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "DB_ENGINE_VERSION_UPGRADE",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "CONFIGURE_BACKUPS",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "CREATING_TOPOLOGY_OF_SOURCE",
                    "Status": "COMPLETED"
                }
            ],
            "Status": "AVAILABLE",
            "CreateTime": "2022-02-25T21:18:51.183000+00:00"
        }
    ]
}

Untuk informasi selengkapnya, lihat Melihat blue/green pener apan di Panduan Pengguna Amazon RDS.

Contoh 2: Untuk menjelaskan blue/green penerapan untuk cluster Aurora MySQL DB

describe-blue-green-deploymentContoh berikut mengambil detail blue/green penerapan.


aws rds describe-blue-green-deployments \
    --blue-green-deployment-identifier bgd-wi89nwzglccsfake

Output:


{
    "BlueGreenDeployments": [
        {
            "BlueGreenDeploymentIdentifier": "bgd-wi89nwzglccsfake",
            "BlueGreenDeploymentName": "my-blue-green-deployment",
            "Source": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
            "Target": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster-green-3rnukl",
            "SwitchoverDetails": [
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster-green-3rnukl",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-1-green-gpmaxf",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-2",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-2-green-j2oajq",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-3",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-3-green-mkxies",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-excluded-member-endpoint",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-excluded-member-endpoint-green-4sqjrq",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-reader-endpoint",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-reader-endpoint-green-gwwzlg",
                    "Status": "AVAILABLE"
                }
            ],
            "Tasks": [
                {
                    "Name": "CREATING_READ_REPLICA_OF_SOURCE",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "DB_ENGINE_VERSION_UPGRADE",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "CREATE_DB_INSTANCES_FOR_CLUSTER",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "CREATE_CUSTOM_ENDPOINTS",
                    "Status": "COMPLETED"
                }
            ],
            "Status": "AVAILABLE",
            "CreateTime": "2022-02-25T21:12:00.288000+00:00"
        }
    ]
}

Untuk informasi selengkapnya, lihat Meli blue/green hat penerapan di Panduan Pengguna Amazon Aurora.

Contoh 3: Untuk menjelaskan blue/green penerapan untuk cluster Aurora MySQL setelah peralihan

describe-blue-green-deploymentContoh berikut mengambil detail tentang blue/green penerapan setelah lingkungan hijau dipromosikan menjadi lingkungan produksi.


aws rds describe-blue-green-deployments \
    --blue-green-deployment-identifier bgd-wi89nwzglccsfake

Output:


{
    "BlueGreenDeployments": [
        {
            "BlueGreenDeploymentIdentifier": "bgd-wi89nwzglccsfake",
            "BlueGreenDeploymentName": "my-blue-green-deployment",
            "Source": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster-old1",
            "Target": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
            "SwitchoverDetails": [
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster-old1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
                    "Status": "SWITCHOVER_COMPLETED"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-1-old1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-1",
                    "Status": "SWITCHOVER_COMPLETED"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-2-old1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-2",
                    "Status": "SWITCHOVER_COMPLETED"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-3-old1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-3",
                    "Status": "SWITCHOVER_COMPLETED"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-excluded-member-endpoint-old1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-excluded-member-endpoint",
                    "Status": "SWITCHOVER_COMPLETED"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-reader-endpoint-old1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-reader-endpoint",
                    "Status": "SWITCHOVER_COMPLETED"
                }
            ],
            "Tasks": [
                {
                    "Name": "CREATING_READ_REPLICA_OF_SOURCE",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "DB_ENGINE_VERSION_UPGRADE",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "CREATE_DB_INSTANCES_FOR_CLUSTER",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "CREATE_CUSTOM_ENDPOINTS",
                    "Status": "COMPLETED"
                }
            ],
            "Status": "SWITCHOVER_COMPLETED",
            "CreateTime": "2022-02-25T22:38:49.522000+00:00"
        }
    ]
}

Untuk informasi selengkapnya, lihat Meli blue/green hat penerapan di Panduan Pengguna Amazon Aurora.

Contoh 4: Untuk menggambarkan penerapan gabungan blue/green

describe-blue-green-deploymentContoh berikut mengambil rincian penerapan gab blue/green ungan.


aws rds describe-blue-green-deployments

Output:


{
    "BlueGreenDeployments": [
        {
            "BlueGreenDeploymentIdentifier": "bgd-wi89nwzgfakelccs",
            "BlueGreenDeploymentName": "my-blue-green-deployment",
            "Source": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
            "Target": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster-green-3rnukl",
            "SwitchoverDetails": [
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster-green-3rnukl",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-1-green-gpmaxf",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-2",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-2-green-j2oajq",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-3",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-3-green-mkxies",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-excluded-member-endpoint",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-excluded-member-endpoint-green-4sqjrq",
                    "Status": "AVAILABLE"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-reader-endpoint",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-reader-endpoint-green-gwwzlg",
                    "Status": "AVAILABLE"
                }
            ],
            "Tasks": [
                {
                    "Name": "CREATING_READ_REPLICA_OF_SOURCE",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "DB_ENGINE_VERSION_UPGRADE",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "CREATE_DB_INSTANCES_FOR_CLUSTER",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "CREATE_CUSTOM_ENDPOINTS",
                    "Status": "COMPLETED"
                }
            ],
            "Status": "AVAILABLE",
            "CreateTime": "2022-02-25T21:12:00.288000+00:00"
        },
        {
            "BlueGreenDeploymentIdentifier": "bgd-v5330365fake1eex",
            "BlueGreenDeploymentName": "bgd-cli-test-instance",
            "Source": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-old1",
            "Target": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance",
            "SwitchoverDetails": [
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-old1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance",
                    "Status": "SWITCHOVER_COMPLETED"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-1-old1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-1",
                    "Status": "SWITCHOVER_COMPLETED"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-2-old1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-2",
                    "Status": "SWITCHOVER_COMPLETED"
                },
                {
                    "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-3-old1",
                    "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-3",
                    "Status": "SWITCHOVER_COMPLETED"
                }
            ],
            "Tasks": [
                {
                    "Name": "CREATING_READ_REPLICA_OF_SOURCE",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "DB_ENGINE_VERSION_UPGRADE",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "CONFIGURE_BACKUPS",
                    "Status": "COMPLETED"
                },
                {
                    "Name": "CREATING_TOPOLOGY_OF_SOURCE",
                    "Status": "COMPLETED"
                }
            ],
            "Status": "SWITCHOVER_COMPLETED",
            "CreateTime": "2022-02-25T22:33:22.225000+00:00"
        }
    ]
}

Untuk informasi selengkapnya, lihat Meli blue/green hat penerapan di Panduan Pengguna Amazon RDS dan Melihat blue/green pener apan di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeBlueGreenDeployments di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-certificates.

AWS CLI

Untuk mendeskripsikan sertifikat

describe-certificatesContoh berikut mengambil rincian sertifikat yang terkait dengan wilayah default pengguna.


aws rds describe-certificates

Output:


{
    "Certificates": [
        {
            "CertificateIdentifier": "rds-ca-ecc384-g1",
            "CertificateType": "CA",
            "Thumbprint": "2ee3dcc06e50192559b13929e73484354f23387d",
            "ValidFrom": "2021-05-24T22:06:59+00:00",
            "ValidTill": "2121-05-24T23:06:59+00:00",
            "CertificateArn": "arn:aws:rds:us-west-2::cert:rds-ca-ecc384-g1",
            "CustomerOverride": false
        },
        {
            "CertificateIdentifier": "rds-ca-rsa4096-g1",
            "CertificateType": "CA",
            "Thumbprint": "19da4f2af579a8ae1f6a0fa77aa5befd874b4cab",
            "ValidFrom": "2021-05-24T22:03:20+00:00",
            "ValidTill": "2121-05-24T23:03:20+00:00",
            "CertificateArn": "arn:aws:rds:us-west-2::cert:rds-ca-rsa4096-g1",
            "CustomerOverride": false
        },
        {
            "CertificateIdentifier": "rds-ca-rsa2048-g1",
            "CertificateType": "CA",
            "Thumbprint": "7c40cb42714b6fdb2b296f9bbd0e8bb364436a76",
            "ValidFrom": "2021-05-24T21:59:00+00:00",
            "ValidTill": "2061-05-24T22:59:00+00:00",
            "CertificateArn": "arn:aws:rds:us-west-2::cert:rds-ca-rsa2048-g1",
            "CustomerOverride": true,
            "CustomerOverrideValidTill": "2061-05-24T22:59:00+00:00"
        },
        {
            "CertificateIdentifier": "rds-ca-2019",
            "CertificateType": "CA",
            "Thumbprint": "d40ddb29e3750dffa671c3140bbf5f478d1c8096",
            "ValidFrom": "2019-08-22T17:08:50+00:00",
            "ValidTill": "2024-08-22T17:08:50+00:00",
            "CertificateArn": "arn:aws:rds:us-west-2::cert:rds-ca-2019",
            "CustomerOverride": false
        }
    ],
    "DefaultCertificateForNewLaunches": "rds-ca-rsa2048-g1"
}

Untuk informasi selengkapnya, lihat Menggunakan SSL/TLS untuk mengenkripsi koneksi ke instans DB di Panduan Pengguna Amazon RDS dan Menggunakan SSL/TLS untuk mengenkripsi koneksi ke cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeCertificates di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-cluster-backtracks.

AWS CLI

Untuk menjelaskan backtrack untuk cluster DB

describe-db-cluster-backtracksContoh berikut mengambil detail tentang cluster DB yang ditentukan.


aws rds describe-db-cluster-backtracks \
    --db-cluster-identifier mydbcluster

Output:


{
    "DBClusterBacktracks": [
        {
            "DBClusterIdentifier": "mydbcluster",
            "BacktrackIdentifier": "2f5f5294-0dd2-44c9-9f50-EXAMPLE",
            "BacktrackTo": "2021-02-12T04:59:22Z",
            "BacktrackedFrom": "2021-02-12T14:37:31.640Z",
            "BacktrackRequestCreationTime": "2021-02-12T14:36:18.819Z",
            "Status": "COMPLETED"
        },
        {
            "DBClusterIdentifier": "mydbcluster",
            "BacktrackIdentifier": "3c7a6421-af2a-4ea3-ae95-EXAMPLE",
            "BacktrackTo": "2021-02-11T22:53:46Z",
            "BacktrackedFrom": "2021-02-12T00:09:27.006Z",
            "BacktrackRequestCreationTime": "2021-02-12T00:07:53.487Z",
            "Status": "COMPLETED"
        }
    ]
}

Untuk informasi selengkapnya, lihat Melacak kembali cluster Aurora DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbClusterBacktracks di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-cluster-endpoints.

AWS CLI

Contoh 1: Untuk menjelaskan titik akhir cluster DB

describe-db-cluster-endpointsContoh berikut mengambil detail untuk titik akhir cluster DB Anda. Jenis cluster Aurora yang paling umum memiliki dua titik akhir. Satu titik akhir memiliki tipeWRITER. Anda dapat menggunakan titik akhir ini untuk semua pernyataan SQL. Titik akhir lainnya memiliki tipeREADER. Anda dapat menggunakan titik akhir ini hanya untuk SELECT dan pernyataan SQL read-only lainnya.


aws rds describe-db-cluster-endpoints

Output:


{
    "DBClusterEndpoints": [
        {
            "DBClusterIdentifier": "my-database-1",
            "Endpoint": "my-database-1.cluster-cnpexample.us-east-1.rds.amazonaws.com",
            "Status": "creating",
            "EndpointType": "WRITER"
        },
        {
            "DBClusterIdentifier": "my-database-1",
            "Endpoint": "my-database-1.cluster-ro-cnpexample.us-east-1.rds.amazonaws.com",
            "Status": "creating",
            "EndpointType": "READER"
        },
        {
            "DBClusterIdentifier": "mydbcluster",
            "Endpoint": "mydbcluster.cluster-cnpexamle.us-east-1.rds.amazonaws.com",
            "Status": "available",
            "EndpointType": "WRITER"
        },
        {
            "DBClusterIdentifier": "mydbcluster",
            "Endpoint": "mydbcluster.cluster-ro-cnpexample.us-east-1.rds.amazonaws.com",
            "Status": "available",
            "EndpointType": "READER"
        }
    ]
}

Contoh 2: Untuk menjelaskan titik akhir cluster DB dari satu cluster DB

describe-db-cluster-endpointsContoh berikut mengambil detail untuk titik akhir cluster DB dari satu cluster DB tertentu. Cluster Aurora Serverless hanya memiliki satu titik akhir dengan tipeWRITER.


aws rds describe-db-cluster-endpoints \
    --db-cluster-identifier serverless-cluster

Output:


{
    "DBClusterEndpoints": [
        {
            "Status": "available",
            "Endpoint": "serverless-cluster.cluster-cnpexample.us-east-1.rds.amazonaws.com",
            "DBClusterIdentifier": "serverless-cluster",
            "EndpointType": "WRITER"
        }
    ]
}

Untuk informasi selengkapnya, lihat Manajemen Koneksi Amazon Aurora di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbClusterEndpoints di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-cluster-parameter-groups.

AWS CLI

Untuk mendeskripsikan grup parameter cluster DB

describe-db-cluster-parameter-groupsContoh berikut mengambil detail untuk grup parameter cluster DB Anda.


aws rds describe-db-cluster-parameter-groups

Output:


{
    "DBClusterParameterGroups": [
        {
            "DBClusterParameterGroupName": "default.aurora-mysql5.7",
            "DBParameterGroupFamily": "aurora-mysql5.7",
            "Description": "Default cluster parameter group for aurora-mysql5.7",
            "DBClusterParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:cluster-pg:default.aurora-mysql5.7"
        },
        {
            "DBClusterParameterGroupName": "default.aurora-postgresql9.6",
            "DBParameterGroupFamily": "aurora-postgresql9.6",
            "Description": "Default cluster parameter group for aurora-postgresql9.6",
            "DBClusterParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:cluster-pg:default.aurora-postgresql9.6"
        },
        {
            "DBClusterParameterGroupName": "default.aurora5.6",
            "DBParameterGroupFamily": "aurora5.6",
            "Description": "Default cluster parameter group for aurora5.6",
            "DBClusterParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:cluster-pg:default.aurora5.6"
        },
        {
            "DBClusterParameterGroupName": "mydbclusterpg",
            "DBParameterGroupFamily": "aurora-mysql5.7",
            "Description": "My DB cluster parameter group",
            "DBClusterParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:cluster-pg:mydbclusterpg"
        },
        {
            "DBClusterParameterGroupName": "mydbclusterpgcopy",
            "DBParameterGroupFamily": "aurora-mysql5.7",
            "Description": "Copy of mydbclusterpg parameter group",
            "DBClusterParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:cluster-pg:mydbclusterpgcopy"
        }
    ]
}

Untuk informasi selengkapnya, lihat Bek erja dengan Grup Parameter DB dan Grup Parameter Cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbClusterParameterGroups di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-cluster-parameters.

AWS CLI

Contoh 1: Untuk menggambarkan parameter dalam kelompok parameter cluster DB

describe-db-cluster-parametersContoh berikut mengambil detail tentang parameter dalam kelompok parameter cluster DB.


aws rds describe-db-cluster-parameters \
    --db-cluster-parameter-group-name mydbclusterpg

Output:


{
    "Parameters": [
        {
            "ParameterName": "allow-suspicious-udfs",
            "Description": "Controls whether user-defined functions that have only an xxx symbol for the main function can be loaded",
            "Source": "engine-default",
            "ApplyType": "static",
            "DataType": "boolean",
            "AllowedValues": "0,1",
            "IsModifiable": false,
            "ApplyMethod": "pending-reboot",
            "SupportedEngineModes": [
                "provisioned"
            ]
        },
        {
            "ParameterName": "aurora_lab_mode",
            "ParameterValue": "0",
            "Description": "Enables new features in the Aurora engine.",
            "Source": "engine-default",
            "ApplyType": "static",
            "DataType": "boolean",
            "AllowedValues": "0,1",
            "IsModifiable": true,
            "ApplyMethod": "pending-reboot",
            "SupportedEngineModes": [
                "provisioned"
            ]
        },
        ...some output truncated...
    ]
}

Contoh 2: Untuk mencantumkan hanya nama parameter dalam grup parameter cluster DB

describe-db-cluster-parametersContoh berikut hanya mengambil nama-nama parameter dalam kelompok parameter cluster DB.


aws rds describe-db-cluster-parameters \
    --db-cluster-parameter-group-name default.aurora-mysql5.7 \
    --query 'Parameters[].{ParameterName:ParameterName}'

Output:


[
    {
        "ParameterName": "allow-suspicious-udfs"
    },
    {
        "ParameterName": "aurora_binlog_read_buffer_size"
    },
    {
        "ParameterName": "aurora_binlog_replication_max_yield_seconds"
    },
    {
        "ParameterName": "aurora_binlog_use_large_read_buffer"
    },
    {
        "ParameterName": "aurora_lab_mode"
    },

    ...some output truncated...
    }
]

Contoh 3: Untuk menjelaskan hanya parameter yang dapat dimodifikasi dalam grup parameter cluster DB

describe-db-cluster-parametersContoh berikut mengambil nama hanya parameter yang dapat Anda modifikasi dalam kelompok parameter cluster DB.


aws rds describe-db-cluster-parameters \
    --db-cluster-parameter-group-name default.aurora-mysql5.7 \
    --query 'Parameters[].{ParameterName:ParameterName,IsModifiable:IsModifiable} | [?IsModifiable == `true`]'

Output:


[
    {
        "ParameterName": "aurora_binlog_read_buffer_size",
        "IsModifiable": true
    },
    {
        "ParameterName": "aurora_binlog_replication_max_yield_seconds",
        "IsModifiable": true
    },
    {
        "ParameterName": "aurora_binlog_use_large_read_buffer",
        "IsModifiable": true
    },
    {
        "ParameterName": "aurora_lab_mode",
        "IsModifiable": true
    },

    ...some output truncated...
    }
]

Contoh 4: Untuk menjelaskan hanya parameter Boolean yang dapat dimodifikasi dalam grup parameter cluster DB

describe-db-cluster-parametersContoh berikut mengambil nama hanya parameter yang dapat Anda modifikasi dalam kelompok parameter cluster DB dan yang memiliki tipe data Boolean.


aws rds describe-db-cluster-parameters \
    --db-cluster-parameter-group-name default.aurora-mysql5.7 \
    --query 'Parameters[].{ParameterName:ParameterName,DataType:DataType,IsModifiable:IsModifiable} | [?DataType == `boolean`] | [?IsModifiable == `true`]'

Output:


[
    {
        "DataType": "boolean",
        "ParameterName": "aurora_binlog_use_large_read_buffer",
        "IsModifiable": true
    },
    {
        "DataType": "boolean",
        "ParameterName": "aurora_lab_mode",
        "IsModifiable": true
    },
    {
        "DataType": "boolean",
        "ParameterName": "autocommit",
        "IsModifiable": true
    },
    {
        "DataType": "boolean",
        "ParameterName": "automatic_sp_privileges",
        "IsModifiable": true
    },
    ...some output truncated...
    }
]

Untuk informasi selengkapnya, lihat Bek erja dengan Grup Parameter DB dan Grup Parameter Cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbClusterParameters di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-cluster-snapshot-attributes.

AWS CLI

Untuk menjelaskan nama atribut dan nilai untuk snapshot cluster DB

describe-db-cluster-snapshot-attributesContoh berikut mengambil rincian nama atribut dan nilai untuk snapshot cluster DB yang ditentukan.


aws rds describe-db-cluster-snapshot-attributes \
    --db-cluster-snapshot-identifier myclustersnapshot

Output:


{
    "DBClusterSnapshotAttributesResult": {
        "DBClusterSnapshotIdentifier": "myclustersnapshot",
        "DBClusterSnapshotAttributes": [
            {
                "AttributeName": "restore",
                "AttributeValues": [
                    "123456789012"
                ]
            }
        ]
    }
}

Untuk informasi selengkapnya, lihat Berbagi Snapshot Cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbClusterSnapshotAttributes di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-cluster-snapshots.

AWS CLI

Untuk menjelaskan snapshot cluster DB untuk cluster DB

describe-db-cluster-snapshotsContoh berikut mengambil detail untuk snapshot cluster DB untuk cluster DB yang ditentukan.


aws rds describe-db-cluster-snapshots \
    --db-cluster-identifier mydbcluster

Output:


{
    "DBClusterSnapshots": [
        {
            "AvailabilityZones": [
                "us-east-1a",
                "us-east-1b",
                "us-east-1e"
            ],
            "DBClusterSnapshotIdentifier": "myclustersnapshotcopy",
            "DBClusterIdentifier": "mydbcluster",
            "SnapshotCreateTime": "2019-06-04T09:16:42.649Z",
            "Engine": "aurora-mysql",
            "AllocatedStorage": 0,
            "Status": "available",
            "Port": 0,
            "VpcId": "vpc-6594f31c",
            "ClusterCreateTime": "2019-04-15T14:18:42.785Z",
            "MasterUsername": "myadmin",
            "EngineVersion": "5.7.mysql_aurora.2.04.2",
            "LicenseModel": "aurora-mysql",
            "SnapshotType": "manual",
            "PercentProgress": 100,
            "StorageEncrypted": true,
            "KmsKeyId": "arn:aws:kms:us-east-1:123456789012:key/AKIAIOSFODNN7EXAMPLE",
            "DBClusterSnapshotArn": "arn:aws:rds:us-east-1:814387698303:cluster-snapshot:myclustersnapshotcopy",
            "IAMDatabaseAuthenticationEnabled": false
        },
        {
            "AvailabilityZones": [
                "us-east-1a",
                "us-east-1b",
                "us-east-1e"
            ],
            "DBClusterSnapshotIdentifier": "rds:mydbcluster-2019-06-20-09-16",
            "DBClusterIdentifier": "mydbcluster",
            "SnapshotCreateTime": "2019-06-20T09:16:26.569Z",
            "Engine": "aurora-mysql",
            "AllocatedStorage": 0,
            "Status": "available",
            "Port": 0,
            "VpcId": "vpc-6594f31c",
            "ClusterCreateTime": "2019-04-15T14:18:42.785Z",
            "MasterUsername": "myadmin",
            "EngineVersion": "5.7.mysql_aurora.2.04.2",
            "LicenseModel": "aurora-mysql",
            "SnapshotType": "automated",
            "PercentProgress": 100,
            "StorageEncrypted": true,
            "KmsKeyId": "arn:aws:kms:us-east-1:814387698303:key/AKIAIOSFODNN7EXAMPLE",
            "DBClusterSnapshotArn": "arn:aws:rds:us-east-1:123456789012:cluster-snapshot:rds:mydbcluster-2019-06-20-09-16",
            "IAMDatabaseAuthenticationEnabled": false
        }
    ]
}

Untuk informasi selengkapnya, lihat Membuat Snapshot Cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbClusterSnapshots di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-clusters.

AWS CLI

Contoh 1: Untuk mendeskripsikan cluster DB

describe-db-clustersContoh berikut mengambil rincian cluster DB yang ditentukan.


aws rds describe-db-clusters \
    --db-cluster-identifier mydbcluster

Output:


{
    "DBClusters": [
        {
            "AllocatedStorage": 1,
            "AvailabilityZones": [
                "us-east-1a",
                "us-east-1b",
                "us-east-1e"
            ],
            "BackupRetentionPeriod": 1,
            "DatabaseName": "mydbcluster",
            "DBClusterIdentifier": "mydbcluster",
            "DBClusterParameterGroup": "default.aurora-mysql5.7",
            "DBSubnetGroup": "default",
            "Status": "available",
            "EarliestRestorableTime": "2019-06-19T09:16:28.210Z",
            "Endpoint": "mydbcluster.cluster-cnpexample.us-east-1.rds.amazonaws.com",
            "ReaderEndpoint": "mydbcluster.cluster-ro-cnpexample.us-east-1.rds.amazonaws.com",
            "MultiAZ": true,
            "Engine": "aurora-mysql",
            "EngineVersion": "5.7.mysql_aurora.2.04.2",
            "LatestRestorableTime": "2019-06-20T22:38:14.908Z",
            "Port": 3306,
            "MasterUsername": "myadmin",
            "PreferredBackupWindow": "09:09-09:39",
            "PreferredMaintenanceWindow": "sat:04:09-sat:04:39",
            "ReadReplicaIdentifiers": [],
            "DBClusterMembers": [
                {
                    "DBInstanceIdentifier": "dbinstance3",
                    "IsClusterWriter": false,
                    "DBClusterParameterGroupStatus": "in-sync",
                    "PromotionTier": 1
                },
                {
                    "DBInstanceIdentifier": "dbinstance1",
                    "IsClusterWriter": false,
                    "DBClusterParameterGroupStatus": "in-sync",
                    "PromotionTier": 1
                },
                {
                    "DBInstanceIdentifier": "dbinstance2",
                    "IsClusterWriter": false,
                    "DBClusterParameterGroupStatus": "in-sync",
                    "PromotionTier": 1
                },
                {
                    "DBInstanceIdentifier": "mydbcluster",
                    "IsClusterWriter": false,
                    "DBClusterParameterGroupStatus": "in-sync",
                    "PromotionTier": 1
                },
                {
                    "DBInstanceIdentifier": "mydbcluster-us-east-1b",
                    "IsClusterWriter": false,
                    "DBClusterParameterGroupStatus": "in-sync",
                    "PromotionTier": 1
                },
                {
                    "DBInstanceIdentifier": "mydbcluster",
                    "IsClusterWriter": true,
                    "DBClusterParameterGroupStatus": "in-sync",
                    "PromotionTier": 1
                }
            ],
            "VpcSecurityGroups": [
                {
                    "VpcSecurityGroupId": "sg-0b9130572daf3dc16",
                    "Status": "active"
                }
            ],
            "HostedZoneId": "Z2R2ITUGPM61AM",
            "StorageEncrypted": true,
            "KmsKeyId": "arn:aws:kms:us-east-1:814387698303:key/AKIAIOSFODNN7EXAMPLE",
            "DbClusterResourceId": "cluster-AKIAIOSFODNN7EXAMPLE",
            "DBClusterArn": "arn:aws:rds:us-east-1:123456789012:cluster:mydbcluster",
            "AssociatedRoles": [],
            "IAMDatabaseAuthenticationEnabled": false,
            "ClusterCreateTime": "2019-04-15T14:18:42.785Z",
            "EngineMode": "provisioned",
            "DeletionProtection": false,
            "HttpEndpointEnabled": false
        }
    ]
}

Contoh 2: Untuk membuat daftar atribut tertentu dari semua cluster DB

describe-db-clustersContoh berikut hanya mengambil ReaderEndpoint atributDBClusterIdentifier,Endpoint, dan semua cluster DB Anda di Wil AWS ayah saat ini.


aws rds describe-db-clusters \
    --query 'DBClusters[].{DBClusterIdentifier:DBClusterIdentifier,Endpoint:Endpoint,ReaderEndpoint:ReaderEndpoint}'

Output:


[
    {
        "Endpoint": "cluster-57-2020-05-01-2270.cluster-cnpexample.us-east-1.rds.amazonaws.com",
        "ReaderEndpoint": "cluster-57-2020-05-01-2270.cluster-ro-cnpexample.us-east-1.rds.amazonaws.com",
        "DBClusterIdentifier": "cluster-57-2020-05-01-2270"
    },
    {
        "Endpoint": "cluster-57-2020-05-01-4615.cluster-cnpexample.us-east-1.rds.amazonaws.com",
        "ReaderEndpoint": "cluster-57-2020-05-01-4615.cluster-ro-cnpexample.us-east-1.rds.amazonaws.com",
        "DBClusterIdentifier": "cluster-57-2020-05-01-4615"
    },
    {
        "Endpoint": "pg2-cluster.cluster-cnpexample.us-east-1.rds.amazonaws.com",
        "ReaderEndpoint": "pg2-cluster.cluster-ro-cnpexample.us-east-1.rds.amazonaws.com",
        "DBClusterIdentifier": "pg2-cluster"
    },
    ...output omitted...
    }
]

Contoh 3: Untuk membuat daftar cluster DB dengan atribut tertentu

describe-db-clustersContoh berikut hanya mengambil Engine atribut DBClusterIdentifier dan dari cluster DB Anda yang menggunakan mesin aurora-postgresql DB.


aws rds describe-db-clusters \
    --query 'DBClusters[].{DBClusterIdentifier:DBClusterIdentifier,Engine:Engine} | [?Engine == `aurora-postgresql`]'

Output:


[
    {
        "Engine": "aurora-postgresql",
        "DBClusterIdentifier": "pg2-cluster"
    }
]

Untuk informasi selengkapnya, lihat Amazon Aurora DB Cluster di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbClusters di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-engine-versions.

AWS CLI

Untuk menjelaskan versi mesin DB untuk mesin DB MySQL

describe-db-engine-versionsContoh berikut menampilkan detail tentang masing-masing versi mesin DB untuk mesin DB yang ditentukan.


aws rds describe-db-engine-versions \
    --engine mysql

Output:


{
    "DBEngineVersions": [
        {
            "Engine": "mysql",
            "EngineVersion": "5.5.46",
            "DBParameterGroupFamily": "mysql5.5",
            "DBEngineDescription": "MySQL Community Edition",
            "DBEngineVersionDescription": "MySQL 5.5.46",
            "ValidUpgradeTarget": [
                {
                    "Engine": "mysql",
                    "EngineVersion": "5.5.53",
                    "Description": "MySQL 5.5.53",
                    "AutoUpgrade": false,
                    "IsMajorVersionUpgrade": false
                },
                {
                    "Engine": "mysql",
                    "EngineVersion": "5.5.54",
                    "Description": "MySQL 5.5.54",
                    "AutoUpgrade": false,
                    "IsMajorVersionUpgrade": false
                },
                {
                    "Engine": "mysql",
                    "EngineVersion": "5.5.57",
                    "Description": "MySQL 5.5.57",
                    "AutoUpgrade": false,
                    "IsMajorVersionUpgrade": false
                },
                ...some output truncated...
            ]
        }

Untuk informasi selengkapnya, lihat Apa itu Amazon Relational Database Service (Amazon RDS)? dalam Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeDBEngineVersions di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-instance-automated-backups.

AWS CLI

Untuk menjelaskan backup otomatis untuk instance DB

describe-db-instance-automated-backupsContoh berikut menampilkan rincian tentang backup otomatis untuk instance DB yang ditentukan. Rinciannya termasuk backup otomatis yang direplikasi di Wil AWS ayah lain.


aws rds describe-db-instance-automated-backups \
    --db-instance-identifier new-orcl-db

Output:


{
    "DBInstanceAutomatedBackups": [
        {
            "DBInstanceArn": "arn:aws:rds:us-east-1:123456789012:db:new-orcl-db",
            "DbiResourceId": "db-JKIB2GFQ5RV7REPLZA4EXAMPLE",
            "Region": "us-east-1",
            "DBInstanceIdentifier": "new-orcl-db",
            "RestoreWindow": {
                "EarliestTime": "2020-12-07T21:05:20.939Z",
                "LatestTime": "2020-12-07T21:05:20.939Z"
            },
            "AllocatedStorage": 20,
            "Status": "replicating",
            "Port": 1521,
            "InstanceCreateTime": "2020-12-04T15:28:31Z",
            "MasterUsername": "admin",
            "Engine": "oracle-se2",
            "EngineVersion": "12.1.0.2.v21",
            "LicenseModel": "bring-your-own-license",
            "OptionGroupName": "default:oracle-se2-12-1",
            "Encrypted": false,
            "StorageType": "gp2",
            "IAMDatabaseAuthenticationEnabled": false,
            "BackupRetentionPeriod": 14,
            "DBInstanceAutomatedBackupsArn": "arn:aws:rds:us-west-2:123456789012:auto-backup:ab-jkib2gfq5rv7replzadausbrktni2bn4example"
        }
    ]
}

Untuk informasi selengkapnya, lihat Menemukan informasi tentang cadangan yang direplikasi di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeDbInstanceAutomatedBackups di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-instances.

AWS CLI

Untuk mendeskripsikan instance DB

describe-db-instancesContoh berikut mengambil detail tentang instance DB yang ditentukan.


aws rds describe-db-instances \
    --db-instance-identifier mydbinstancecf

Output:


{
    "DBInstances": [
        {
            "DBInstanceIdentifier": "mydbinstancecf",
            "DBInstanceClass": "db.t3.small",
            "Engine": "mysql",
            "DBInstanceStatus": "available",
            "MasterUsername": "masterawsuser",
            "Endpoint": {
                "Address": "mydbinstancecf.abcexample.us-east-1.rds.amazonaws.com",
                "Port": 3306,
                "HostedZoneId": "Z2R2ITUGPM61AM"
            },
            ...some output truncated...
        }
    ]
}

Untuk detail API, lihat Deskri bInstances di AWS CLI Referensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-log-files.

AWS CLI

Untuk mendeskripsikan file log untuk instance DB

describe-db-log-filesContoh berikut mengambil detail tentang file log untuk instance DB yang ditentukan.


aws rds describe-db-log-files \
    --db-instance-identifier test-instance

Output:


{
    "DescribeDBLogFiles": [
        {
            "Size": 0,
            "LastWritten": 1533060000000,
            "LogFileName": "error/mysql-error-running.log"
        },
        {
            "Size": 2683,
            "LastWritten": 1532994300000,
            "LogFileName": "error/mysql-error-running.log.0"
        },
        {
            "Size": 107,
            "LastWritten": 1533057300000,
            "LogFileName": "error/mysql-error-running.log.18"
        },
        {
            "Size": 13105,
            "LastWritten": 1532991000000,
            "LogFileName": "error/mysql-error-running.log.23"
        },
        {
            "Size": 0,
            "LastWritten": 1533061200000,
            "LogFileName": "error/mysql-error.log"
        },
        {
            "Size": 3519,
            "LastWritten": 1532989252000,
            "LogFileName": "mysqlUpgrade"
        }
    ]
}

Untuk detail API, lihat DescribeDbLogFiles di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-parameter-groups.

AWS CLI

Untuk mendeskripsikan grup parameter DB Anda

describe-db-parameter-groupsContoh berikut mengambil detail tentang grup parameter DB Anda.


aws rds describe-db-parameter-groups

Output:


{
    "DBParameterGroups": [
        {
            "DBParameterGroupName": "default.aurora-mysql5.7",
            "DBParameterGroupFamily": "aurora-mysql5.7",
            "Description": "Default parameter group for aurora-mysql5.7",
            "DBParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:pg:default.aurora-mysql5.7"
        },
        {
            "DBParameterGroupName": "default.aurora-postgresql9.6",
            "DBParameterGroupFamily": "aurora-postgresql9.6",
            "Description": "Default parameter group for aurora-postgresql9.6",
            "DBParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:pg:default.aurora-postgresql9.6"
        },
        {
            "DBParameterGroupName": "default.aurora5.6",
            "DBParameterGroupFamily": "aurora5.6",
            "Description": "Default parameter group for aurora5.6",
            "DBParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:pg:default.aurora5.6"
        },
        {
            "DBParameterGroupName": "default.mariadb10.1",
            "DBParameterGroupFamily": "mariadb10.1",
            "Description": "Default parameter group for mariadb10.1",
            "DBParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:pg:default.mariadb10.1"
        },
        ...some output truncated...
    ]
}

Untuk informasi selengkapnya, lihat Bekerja dengan Grup Parameter DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeDBParameterGroups di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-parameters.

AWS CLI

Untuk mendeskripsikan parameter dalam kelompok parameter DB

describe-db-parametersContoh berikut mengambil rincian dari grup parameter DB yang ditentukan.


aws rds describe-db-parameters \
    --db-parameter-group-name mydbpg

Output:


{
    "Parameters": [
        {
            "ParameterName": "allow-suspicious-udfs",
            "Description": "Controls whether user-defined functions that have only an xxx symbol for the main function can be loaded",
            "Source": "engine-default",
            "ApplyType": "static",
            "DataType": "boolean",
            "AllowedValues": "0,1",
            "IsModifiable": false,
            "ApplyMethod": "pending-reboot"
        },
        {
            "ParameterName": "auto_generate_certs",
            "Description": "Controls whether the server autogenerates SSL key and certificate files in the data directory, if they do not already exist.",
            "Source": "engine-default",
            "ApplyType": "static",
            "DataType": "boolean",
            "AllowedValues": "0,1",
            "IsModifiable": false,
            "ApplyMethod": "pending-reboot"
        },
        ...some output truncated...
    ]
}

Untuk informasi selengkapnya, lihat Bekerja dengan Grup Parameter DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat Des kribDBParameters di AWS CLI Referensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-proxies.

AWS CLI

Untuk mendeskripsikan proxy DB untuk database RDS

describe-db-proxiesContoh berikut mengembalikan informasi tentang proxy DB.


aws rds describe-db-proxies

Output:


{
    "DBProxies": [
        {
            "DBProxyName": "proxyExample1",
            "DBProxyArn": "arn:aws:rds:us-east-1:123456789012:db-proxy:prx-0123a01b12345c0ab",
            "Status": "available",
            "EngineFamily": "PostgreSQL",
            "VpcId": "vpc-1234567",
            "VpcSecurityGroupIds": [
                "sg-1234"
            ],
            "VpcSubnetIds": [
                "subnetgroup1",
                "subnetgroup2"
            ],
            "Auth": "[
                {
                    "Description": "proxydescription1"
                    "AuthScheme": "SECRETS",
                    "SecretArn": "arn:aws:secretsmanager:us-west-2:123456789123:secret:secretName-1234f",
                    "IAMAuth": "DISABLED"
                }
            ]",
            "RoleArn": "arn:aws:iam::12345678912??:role/ProxyPostgreSQLRole",
            "Endpoint": "proxyExample1.proxy-ab0cd1efghij.us-east-1.rds.amazonaws.com",
            "RequireTLS": false,
            "IdleClientTimeout": 1800,
            "DebuggingLogging": false,
            "CreatedDate": "2023-04-05T16:09:33.452000+00:00",
            "UpdatedDate": "2023-04-13T01:49:38.568000+00:00"
        },
        {
            "DBProxyName": "proxyExample2",
            "DBProxyArn": "arn:aws:rds:us-east-1:123456789012:db-proxy:prx-1234a12b23456c1ab",
            "Status": "available",
            "EngineFamily": "PostgreSQL",
            "VpcId": "sg-1234567",
            "VpcSecurityGroupIds": [
                "sg-1234"
            ],
            "VpcSubnetIds": [
                "subnetgroup1",
                "subnetgroup2"
            ],
            "Auth": "[
                {
                    "Description": "proxydescription2"
                    "AuthScheme": "SECRETS",
                    "SecretArn": "aarn:aws:secretsmanager:us-west-2:123456789123:secret:secretName-1234f",
                    "IAMAuth": "DISABLED"
                }
            ]",
            "RoleArn": "arn:aws:iam::12345678912:role/ProxyPostgreSQLRole",
            "Endpoint": "proxyExample2.proxy-ab0cd1efghij.us-east-1.rds.amazonaws.com",
            "RequireTLS": false,
            "IdleClientTimeout": 1800,
            "DebuggingLogging": false,
            "CreatedDate": "2022-01-05T16:19:33.452000+00:00",
            "UpdatedDate": "2023-04-13T01:49:38.568000+00:00"
        }
    ]
}

Untuk informasi selengkapnya, lihat Melihat Proxy RDS di Panduan Pengguna Amazon RDS dan Melihat Proxy RDS di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbProxies di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-proxy-endpoints.

AWS CLI

Untuk mendeskripsikan titik akhir proxy DB

describe-db-proxy-endpointsContoh berikut mengembalikan informasi tentang titik akhir proxy DB.


aws rds describe-db-proxy-endpoints

Output:


{
    "DBProxyEndpoints": [
        {
            "DBProxyEndpointName": "proxyEndpoint1",
            "DBProxyEndpointArn": "arn:aws:rds:us-east-1:123456789012:db-proxy-endpoint:prx-endpoint-0123a01b12345c0ab",
            "DBProxyName": "proxyExample",
            "Status": "available",
            "VpcId": "vpc-1234567",
            "VpcSecurityGroupIds": [
                "sg-1234"
            ],
            "VpcSubnetIds": [
                "subnetgroup1",
                "subnetgroup2"
            ],
            "Endpoint": "proxyEndpoint1.endpoint.proxy-ab0cd1efghij.us-east-1.rds.amazonaws.com",
            "CreatedDate": "2023-04-05T16:09:33.452000+00:00",
            "TargetRole": "READ_WRITE",
            "IsDefault": false
        },
        {
            "DBProxyEndpointName": "proxyEndpoint2",
            "DBProxyEndpointArn": "arn:aws:rds:us-east-1:123456789012:db-proxy-endpoint:prx-endpoint-4567a01b12345c0ab",
            "DBProxyName": "proxyExample2",
            "Status": "available",
            "VpcId": "vpc1234567",
            "VpcSecurityGroupIds": [
                "sg-5678"
            ],
            "VpcSubnetIds": [
                "subnetgroup1",
                "subnetgroup2"
            ],
            "Endpoint": "proxyEndpoint2.endpoint.proxy-cd1ef2klmnop.us-east-1.rds.amazonaws.com",
            "CreatedDate": "2023-04-05T16:09:33.452000+00:00",
            "TargetRole": "READ_WRITE",
            "IsDefault": false
        }
    ]
}

Untuk informasi selengkapnya, lihat Melihat titik akhir proxy di Panduan Pengguna Amazon RDS dan Membuat titik akhir proxy di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbProxyEndpoints di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-proxy-target-groups.

AWS CLI

Untuk mendeskripsikan titik akhir proxy DB

describe-db-proxy-target-groupsContoh berikut mengembalikan informasi tentang kelompok target proxy DB.


aws rds describe-db-proxy-target-groups \
    --db-proxy-name proxyExample

Output:


{
"TargetGroups":
    {
        "DBProxyName": "proxyExample",
        "TargetGroupName": "default",
        "TargetGroupArn": "arn:aws:rds:us-east-1:123456789012:target-group:prx-tg-0123a01b12345c0ab",
        "IsDefault": true,
        "Status": "available",
        "ConnectionPoolConfig": {
            "MaxConnectionsPercent": 100,
            "MaxIdleConnectionsPercent": 50,
            "ConnectionBorrowTimeout": 120,
            "SessionPinningFilters": []
        },
        "CreatedDate": "2023-05-02T18:41:19.495000+00:00",
        "UpdatedDate": "2023-05-02T18:41:21.762000+00:00"
    }
}

Untuk informasi selengkapnya, lihat Melihat Proxy RDS di Panduan Pengguna Amazon RDS dan Melihat Proxy RDS di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbProxyTargetGroups di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-proxy-targets.

AWS CLI

Untuk menjelaskan target proxy DB

describe-db-proxy-targetsContoh berikut mengembalikan informasi tentang target proxy DB.


aws rds describe-db-proxy-targets \
    --db-proxy-name proxyExample

Output:


{
    "Targets": [
        {
            "Endpoint": "database1.ab0cd1efghij.us-east-1.rds.amazonaws.com",
            "TrackedClusterId": "database1",
            "RdsResourceId": "database1-instance-1",
            "Port": 3306,
            "Type": "RDS_INSTANCE",
            "Role": "READ_WRITE",
            "TargetHealth": {
                "State": "UNAVAILABLE",
                "Reason": "PENDING_PROXY_CAPACITY",
                "Description": "DBProxy Target is waiting for proxy to scale to desired capacity"
            }
        }
    ]
}

Untuk informasi selengkapnya, lihat Melihat proxy RDS di Panduan Pengguna Amazon RDS dan Melihat proxy RDS di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbProxyTargets di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-recommendations.

AWS CLI

Contoh 1: Untuk membuat daftar semua rekomendasi DB

describe-db-recommendationsContoh berikut mencantumkan semua rekomendasi DB di AWS akun Anda.


aws rds describe-db-recommendations

Output:


{
    "DBRecommendations": [
        {
            "RecommendationId": "12ab3cde-f456-7g8h-9012-i3j45678k9lm",
            "TypeId": "config_recommendation::old_minor_version",
            "Severity": "informational",
            "ResourceArn": "arn:aws:rds:us-west-2:111122223333:db:database-1",
            "Status": "active",
            "CreatedTime": "2024-02-21T23:14:19.292000+00:00",
            "UpdatedTime": "2024-02-21T23:14:19+00:00",
            "Detection": "**[resource-name]** is not running the latest minor DB engine version",
            "Recommendation": "Upgrade to latest engine version",
            "Description": "Your database resources aren't running the latest minor DB engine version. The latest minor version contains the latest security fixes and other improvements.",
            "RecommendedActions": [
                {
                    "ActionId": "12ab34c5de6fg7h89i0jk1lm234n5678",
                    "Operation": "modifyDbInstance",
                    "Parameters": [
                        {
                            "Key": "EngineVersion",
                            "Value": "5.7.44"
                        },
                        {
                            "Key": "DBInstanceIdentifier",
                            "Value": "database-1"
                        }
                    ],
                    "ApplyModes": [
                        "immediately",
                        "next-maintenance-window"
                    ],
                    "Status": "ready",
                    "ContextAttributes": [
                        {
                            "Key": "Recommended value",
                            "Value": "5.7.44"
                        },
                        {
                            "Key": "Current engine version",
                            "Value": "5.7.42"
                        }
                    ]
                }
            ],
            "Category": "security",
            "Source": "RDS",
            "TypeDetection": "**[resource-count] resources** are not running the latest minor DB engine version",
            "TypeRecommendation": "Upgrade to latest engine version",
            "Impact": "Reduced database performance and data security at risk",
            "AdditionalInfo": "We recommend that you maintain your database with the latest DB engine minor version as this version includes the latest security and functionality fixes. The DB engine minor version upgrades contain only the changes which are backward-compatible with earlier minor versions of the same major version of the DB engine.",
            "Links": [
                {
                    "Text": "Upgrading an RDS DB instance engine version",
                    "Url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html"
                },
                {
                    "Text": "Using Amazon RDS Blue/Green Deployments for database updates for Amazon Aurora",
                    "Url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html"
                },
                {
                    "Text": "Using Amazon RDS Blue/Green Deployments for database updates for Amazon RDS",
                    "Url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html"
                }
            ]
        }
    ]
}

Untuk informasi selengkapnya, lihat Melihat dan menanggapi rekomendasi Amazon RDS di Panduan Pengguna Amazon RDS dan Melihat dan menanggapi rekomendasi Amazon RDS di Panduan Pengguna Amazon Aurora.

Contoh 2: Untuk membuat daftar rekomendasi DB tingkat keparahan tinggi

describe-db-recommendationsContoh berikut mencantumkan rekomendasi DB tingkat keparahan tinggi di AWS akun Anda.


aws rds describe-db-recommendations \
    --filters Name=severity,Values=high

Output:


{
    "DBRecommendations": [
        {
            "RecommendationId": "12ab3cde-f456-7g8h-9012-i3j45678k9lm",
            "TypeId": "config_recommendation::rds_extended_support",
            "Severity": "high",
            "ResourceArn": "arn:aws:rds:us-west-2:111122223333:db:database-1",
            "Status": "active",
            "CreatedTime": "2024-02-21T23:14:19.392000+00:00",
            "UpdatedTime": "2024-02-21T23:14:19+00:00",
            "Detection": "Your databases will be auto-enrolled to RDS Extended Support on February 29",
            "Recommendation": "Upgrade your major version before February 29, 2024 to avoid additional charges",
            "Description": "Your PostgreSQL 11 and MySQL 5.7 databases will be automatically enrolled into RDS Extended Support on February 29, 2024. To avoid the increase in charges due to RDS Extended Support, we recommend upgrading your databases to a newer major engine version before February 29, 2024.\nTo learn more about the RDS Extended Support pricing, refer to the pricing page.",
            "RecommendedActions": [
                {
                    "ActionId": "12ab34c5de6fg7h89i0jk1lm234n5678",
                    "Parameters": [],
                    "ApplyModes": [
                        "manual"
                    ],
                    "Status": "ready",
                    "ContextAttributes": []
                }
            ],
            "Category": "cost optimization",
            "Source": "RDS",
            "TypeDetection": "Your database will be auto-enrolled to RDS Extended Support on February 29",
            "TypeRecommendation": "Upgrade your major version before February 29, 2024 to avoid additional charges",
            "Impact": "Increase in charges due to RDS Extended Support",
            "AdditionalInfo": "With Amazon RDS Extended Support, you can continue running your database on a major engine version past the RDS end of standard support date for an additional cost. This paid feature gives you more time to upgrade to a supported major engine version.\nDuring Extended Support, Amazon RDS will supply critical CVE patches and bug fixes.",
            "Links": [
                {
                    "Text": "Amazon RDS Extended Support pricing for RDS for MySQL",
                    "Url": "https://aws.amazon.com/rds/mysql/pricing/"
                },
                {
                    "Text": "Amazon RDS Extended Support for RDS for MySQL and PostgreSQL databases",
                    "Url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support.html"
                },
                {
                    "Text": "Amazon RDS Extended Support pricing for Amazon Aurora PostgreSQL",
                    "Url": "https://aws.amazon.com/rds/aurora/pricing/"
                },
                {
                    "Text": "Amazon RDS Extended Support for Aurora PostgreSQL databases",
                    "Url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support.html"
                },
                {
                    "Text": "Amazon RDS Extended Support pricing for RDS for PostgreSQL",
                    "Url": "https://aws.amazon.com/rds/postgresql/pricing/"
                }
            ]
        }
    ]
}

Contoh 3: Untuk mencantumkan rekomendasi DB untuk instance DB tertentu

describe-db-recommendationsContoh berikut mencantumkan semua rekomendasi DB untuk instance DB tertentu.


aws rds describe-db-recommendations \
    --filters Name=dbi-resource-id,Values=database-1

Output:


{
    "DBRecommendations": [
        {
            "RecommendationId": "12ab3cde-f456-7g8h-9012-i3j45678k9lm",
            "TypeId": "config_recommendation::old_minor_version",
            "Severity": "informational",
            "ResourceArn": "arn:aws:rds:us-west-2:111122223333:db:database-1",
            "Status": "active",
            "CreatedTime": "2024-02-21T23:14:19.292000+00:00",
            "UpdatedTime": "2024-02-21T23:14:19+00:00",
            "Detection": "**[resource-name]** is not running the latest minor DB engine version",
            "Recommendation": "Upgrade to latest engine version",
            "Description": "Your database resources aren't running the latest minor DB engine version. The latest minor version contains the latest security fixes and other improvements.",
            "RecommendedActions": [
                {
                    "ActionId": "12ab34c5de6fg7h89i0jk1lm234n5678",
                    "Operation": "modifyDbInstance",
                    "Parameters": [
                        {
                            "Key": "EngineVersion",
                            "Value": "5.7.44"
                        },
                        {
                            "Key": "DBInstanceIdentifier",
                            "Value": "database-1"
                        }
                    ],
                    "ApplyModes": [
                        "immediately",
                        "next-maintenance-window"
                    ],
                    "Status": "ready",
                    "ContextAttributes": [
                        {
                            "Key": "Recommended value",
                            "Value": "5.7.44"
                        },
                        {
                            "Key": "Current engine version",
                            "Value": "5.7.42"
                        }
                    ]
                }
            ],
            "Category": "security",
            "Source": "RDS",
            "TypeDetection": "**[resource-count] resources** are not running the latest minor DB engine version",
            "TypeRecommendation": "Upgrade to latest engine version",
            "Impact": "Reduced database performance and data security at risk",
            "AdditionalInfo": "We recommend that you maintain your database with the latest DB engine minor version as this version includes the latest security and functionality fixes. The DB engine minor version upgrades contain only the changes which are backward-compatible with earlier minor versions of the same major version of the DB engine.",
            "Links": [
                {
                    "Text": "Upgrading an RDS DB instance engine version",
                    "Url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html"
                },
                {
                    "Text": "Using Amazon RDS Blue/Green Deployments for database updates for Amazon Aurora",
                    "Url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html"
                },
                {
                    "Text": "Using Amazon RDS Blue/Green Deployments for database updates for Amazon RDS",
                    "Url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html"
                }
            ]
        }
    ]
}

Contoh 4: Untuk membuat daftar semua rekomendasi DB aktif

describe-db-recommendationsContoh berikut mencantumkan semua rekomendasi DB aktif di AWS akun Anda.


aws rds describe-db-recommendations \
    --filters Name=status,Values=active

Output:


{
    "DBRecommendations": [
        {
            "RecommendationId": "12ab3cde-f456-7g8h-9012-i3j45678k9lm",
            "TypeId": "config_recommendation::old_minor_version",
            "Severity": "informational",
            "ResourceArn": "arn:aws:rds:us-west-2:111122223333:db:database-1",
            "Status": "active",
            "CreatedTime": "2024-02-21T23:14:19.292000+00:00",
            "UpdatedTime": "2024-02-21T23:14:19+00:00",
            "Detection": "**[resource-name]** is not running the latest minor DB engine version",
            "Recommendation": "Upgrade to latest engine version",
            "Description": "Your database resources aren't running the latest minor DB engine version. The latest minor version contains the latest security fixes and other improvements.",
            "RecommendedActions": [
                {
                    "ActionId": "12ab34c5de6fg7h89i0jk1lm234n5678",
                    "Operation": "modifyDbInstance",
                    "Parameters": [
                        {
                            "Key": "EngineVersion",
                            "Value": "5.7.44"
                        },
                        {
                            "Key": "DBInstanceIdentifier",
                            "Value": "database-1"
                        }
                    ],
                    "ApplyModes": [
                        "immediately",
                        "next-maintenance-window"
                    ],
                    "Status": "ready",
                    "ContextAttributes": [
                        {
                            "Key": "Recommended value",
                            "Value": "5.7.44"
                        },
                        {
                            "Key": "Current engine version",
                            "Value": "5.7.42"
                        }
                    ]
                }
            ],
            "Category": "security",
            "Source": "RDS",
            "TypeDetection": "**[resource-count] resources** are not running the latest minor DB engine version",
            "TypeRecommendation": "Upgrade to latest engine version",
            "Impact": "Reduced database performance and data security at risk",
            "AdditionalInfo": "We recommend that you maintain your database with the latest DB engine minor version as this version includes the latest security and functionality fixes. The DB engine minor version upgrades contain only the changes which are backward-compatible with earlier minor versions of the same major version of the DB engine.",
            "Links": [
                {
                    "Text": "Upgrading an RDS DB instance engine version",
                    "Url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html"
                },
                {
                    "Text": "Using Amazon RDS Blue/Green Deployments for database updates for Amazon Aurora",
                    "Url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html"
                },
                {
                    "Text": "Using Amazon RDS Blue/Green Deployments for database updates for Amazon RDS",
                    "Url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html"
                }
            ]
        }
    ]
}

Untuk detail API, lihat DescribeDbRecommendations di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-security-groups.

AWS CLI

Untuk membuat daftar grup keamanan DB

describe-db-security-groupsContoh berikut mencantumkan grup keamanan DB.


aws rds describe-db-security-groups

Output:


{
    "DBSecurityGroups": [
        {
            "OwnerId": "123456789012",
            "DBSecurityGroupName": "default",
            "DBSecurityGroupDescription": "default",
            "EC2SecurityGroups": [],
            "IPRanges": [],
            "DBSecurityGroupArn": "arn:aws:rds:us-west-1:111122223333:secgrp:default"
        },
        {
            "OwnerId": "123456789012",
            "DBSecurityGroupName": "mysecgroup",
            "DBSecurityGroupDescription": "My Test Security Group",
            "VpcId": "vpc-1234567f",
            "EC2SecurityGroups": [],
            "IPRanges": [],
            "DBSecurityGroupArn": "arn:aws:rds:us-west-1:111122223333:secgrp:mysecgroup"
        }
    ]
}

Untuk informasi selengkapnya, lihat Daftar Grup Keamanan DB yang Tersedia di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeDbSecurityGroups di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-shard-groups.

AWS CLI

Contoh 1: Untuk menggambarkan kelompok pecahan DB

describe-db-shard-groupsContoh berikut mengambil rincian grup pecahan DB Anda.


aws rds describe-db-shard-groups

Output:


{
    "DBShardGroups": [
        {
            "DBShardGroupResourceId": "shardgroup-7bb446329da94788b3f957746example",
            "DBShardGroupIdentifier": "limitless-test-shard-grp",
            "DBClusterIdentifier": "limitless-test-cluster",
            "MaxACU": 768.0,
            "ComputeRedundancy": 0,
            "Status": "available",
            "PubliclyAccessible": true,
            "Endpoint": "limitless-test-cluster.limitless-cekycexample.us-east-2.rds.amazonaws.com"
        },
        {
            "DBShardGroupResourceId": "shardgroup-a6e3a0226aa243e2ac6c7a1234567890",
            "DBShardGroupIdentifier": "my-db-shard-group",
            "DBClusterIdentifier": "my-sv2-cluster",
            "MaxACU": 768.0,
            "ComputeRedundancy": 0,
            "Status": "available",
            "PubliclyAccessible": false,
            "Endpoint": "my-sv2-cluster.limitless-cekycexample.us-east-2.rds.amazonaws.com"
        }
    ]
}

Untuk informasi selengkapnya, lihat Amazon Aurora DB Cluster di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeDbShardGroups di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-snapshot-attributes.

AWS CLI

Untuk menjelaskan nama atribut dan nilai untuk snapshot DB

describe-db-snapshot-attributesContoh berikut menjelaskan nama atribut dan nilai untuk snapshot DB.


aws rds describe-db-snapshot-attributes \
    --db-snapshot-identifier mydbsnapshot

Output:


{
    "DBSnapshotAttributesResult": {
        "DBSnapshotIdentifier": "mydbsnapshot",
        "DBSnapshotAttributes": [
            {
                "AttributeName": "restore",
                "AttributeValues": [
                    "123456789012",
                    "210987654321"
                ]
            }
        ]
    }
}

Untuk informasi selengkapnya, lihat Berbagi Snapshot DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeDbSnapshotAttributes di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-db-snapshots.

AWS CLI

Contoh 1: Untuk mendeskripsikan snapshot DB untuk instance DB

describe-db-snapshotsContoh berikut mengambil rincian snapshot DB untuk instance DB.


aws rds describe-db-snapshots \
    --db-snapshot-identifier mydbsnapshot

Output:


{
    "DBSnapshots": [
        {
            "DBSnapshotIdentifier": "mydbsnapshot",
            "DBInstanceIdentifier": "mysqldb",
            "SnapshotCreateTime": "2018-02-08T22:28:08.598Z",
            "Engine": "mysql",
            "AllocatedStorage": 20,
            "Status": "available",
            "Port": 3306,
            "AvailabilityZone": "us-east-1f",
            "VpcId": "vpc-6594f31c",
            "InstanceCreateTime": "2018-02-08T22:24:55.973Z",
            "MasterUsername": "mysqladmin",
            "EngineVersion": "5.6.37",
            "LicenseModel": "general-public-license",
            "SnapshotType": "manual",
            "OptionGroupName": "default:mysql-5-6",
            "PercentProgress": 100,
            "StorageType": "gp2",
            "Encrypted": false,
            "DBSnapshotArn": "arn:aws:rds:us-east-1:123456789012:snapshot:mydbsnapshot",
            "IAMDatabaseAuthenticationEnabled": false,
            "ProcessorFeatures": [],
            "DbiResourceId": "db-AKIAIOSFODNN7EXAMPLE"
        }
    ]
}

Untuk informasi selengkapnya, lihat Membuat Snapshot DB di Panduan Pengguna Amazon RDS.

Contoh 2: Untuk menemukan jumlah snapshot manual yang diambil

describe-db-snapshotsContoh berikut menggunakan length operator dalam --query opsi untuk mengembalikan jumlah snapshot manual yang telah diambil di Wil AWS ayah tertentu.


aws rds describe-db-snapshots \
    --snapshot-type manual \
    --query "length(*[].{DBSnapshots:SnapshotType})" \
    --region eu-central-1

Output:

Untuk informasi selengkapnya, lihat Membuat Snapshot DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat Des kripsiBDSnapshots di Referensi Perintah. AWS CLI

Contoh kode berikut menunjukkan cara menggunakandescribe-db-subnet-groups.

AWS CLI

Untuk mendeskripsikan grup subnet DB

describe-db-subnet-groupsContoh berikut mengambil rincian grup subnet DB yang ditentukan.


aws rds describe-db-subnet-groups

Output:


{
    "DBSubnetGroups": [
        {
            "DBSubnetGroupName": "mydbsubnetgroup",
            "DBSubnetGroupDescription": "My DB Subnet Group",
            "VpcId": "vpc-971c12ee",
            "SubnetGroupStatus": "Complete",
            "Subnets": [
                {
                    "SubnetIdentifier": "subnet-d8c8e7f4",
                    "SubnetAvailabilityZone": {
                        "Name": "us-east-1a"
                    },
                    "SubnetStatus": "Active"
                },
                {
                    "SubnetIdentifier": "subnet-718fdc7d",
                    "SubnetAvailabilityZone": {
                        "Name": "us-east-1f"
                    },
                    "SubnetStatus": "Active"
                },
                {
                    "SubnetIdentifier": "subnet-cbc8e7e7",
                    "SubnetAvailabilityZone": {
                        "Name": "us-east-1a"
                    },
                    "SubnetStatus": "Active"
                },
                {
                    "SubnetIdentifier": "subnet-0ccde220",
                    "SubnetAvailabilityZone": {
                        "Name": "us-east-1a"
                    },
                    "SubnetStatus": "Active"
                }
            ],
            "DBSubnetGroupArn": "arn:aws:rds:us-east-1:123456789012:subgrp:mydbsubnetgroup"
        }
    ]
}

Untuk informasi selengkapnya, lihat Amazon Virtual Private Cloud VPC dan Amazon RDS di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeDbSubnetGroups di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-engine-default-cluster-parameters.

AWS CLI

Untuk menjelaskan mesin default dan informasi parameter sistem untuk mesin database Aurora

describe-engine-default-cluster-parametersContoh berikut mengambil rincian mesin default dan informasi parameter sistem untuk cluster Aurora DB dengan kompatibilitas MySQL 5.7.


aws rds describe-engine-default-cluster-parameters \
    --db-parameter-group-family aurora-mysql5.7

Output:


{
    "EngineDefaults": {
        "Parameters": [
            {
                "ParameterName": "aurora_load_from_s3_role",
                "Description": "IAM role ARN used to load data from AWS S3",
                "Source": "engine-default",
                "ApplyType": "dynamic",
                "DataType": "string",
                "IsModifiable": true,
                "SupportedEngineModes": [
                    "provisioned"
                ]
            },
            ...some output truncated...
        ]
    }
}

Untuk informasi selengkapnya, lihat Bek erja dengan Grup Parameter DB dan Grup Parameter Cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeEngineDefaultClusterParameters di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-engine-default-parameters.

AWS CLI

Untuk menjelaskan mesin default dan informasi parameter sistem untuk mesin database

describe-engine-default-parametersContoh berikut mengambil detail untuk mesin default dan informasi parameter sistem untuk instance MySQL 5.7 DB.


aws rds describe-engine-default-parameters \
    --db-parameter-group-family mysql5.7

Output:


{
    "EngineDefaults": {
        "Parameters": [
            {
                "ParameterName": "allow-suspicious-udfs",
                "Description": "Controls whether user-defined functions that have only an xxx symbol for the main function can be loaded",
                "Source": "engine-default",
                "ApplyType": "static",
                "DataType": "boolean",
                "AllowedValues": "0,1",
                "IsModifiable": false
            },
            ...some output truncated...
        ]
    }
}

Untuk informasi selengkapnya, lihat Bekerja dengan Grup Parameter DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeEngineDefaultParameters di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-event-categories.

AWS CLI

Untuk mendeskripsikan kategori acara

describe-event-categoriesContoh berikut mengambil detail tentang kategori acara untuk semua sumber acara yang tersedia.


aws rds describe-event-categories

Output:


{
    "EventCategoriesMapList": [
        {
            "SourceType": "db-instance",
            "EventCategories": [
                "deletion",
                "read replica",
                "failover",
                "restoration",
                "maintenance",
                "low storage",
                "configuration change",
                "backup",
                "creation",
                "availability",
                "recovery",
                "failure",
                "backtrack",
                "notification"
            ]
        },
        {
            "SourceType": "db-security-group",
            "EventCategories": [
                "configuration change",
                "failure"
            ]
        },
        {
            "SourceType": "db-parameter-group",
            "EventCategories": [
                "configuration change"
            ]
        },
        {
            "SourceType": "db-snapshot",
            "EventCategories": [
                "deletion",
                "creation",
                "restoration",
                "notification"
            ]
        },
        {
            "SourceType": "db-cluster",
            "EventCategories": [
                "failover",
                "failure",
                "notification"
            ]
        },
        {
            "SourceType": "db-cluster-snapshot",
            "EventCategories": [
                "backup"
            ]
        }
    ]
}

Untuk detail API, lihat DescribeEventCategories di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-event-subscriptions.

AWS CLI

Untuk menjelaskan langganan acara

Contoh ini menjelaskan semua langganan acara Amazon RDS untuk AWS akun saat ini.


aws rds describe-event-subscriptions

Output:


{
    "EventSubscriptionsList": [
        {
            "EventCategoriesList": [
                "backup",
                "recovery"
            ],
            "Enabled": true,
            "EventSubscriptionArn": "arn:aws:rds:us-east-1:123456789012:es:my-instance-events",
            "Status": "creating",
            "SourceType": "db-instance",
            "CustomerAwsId": "123456789012",
            "SubscriptionCreationTime": "2018-07-31 23:22:01.893",
            "CustSubscriptionId": "my-instance-events",
            "SnsTopicArn": "arn:aws:sns:us-east-1:123456789012:interesting-events"
        },
        ...some output truncated...
    ]
}

Untuk detail API, lihat DescribeEventSubscriptions di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-events.

AWS CLI

Untuk menggambarkan peristiwa

describe-eventsContoh berikut mengambil detail untuk peristiwa yang telah terjadi untuk instance DB yang ditentukan.


aws rds describe-events \
    --source-identifier test-instance \
    --source-type db-instance

Output:


{
    "Events": [
        {
            "SourceType": "db-instance",
            "SourceIdentifier": "test-instance",
            "EventCategories": [
                "backup"
            ],
            "Message": "Backing up DB instance",
            "Date": "2018-07-31T23:09:23.983Z",
            "SourceArn": "arn:aws:rds:us-east-1:123456789012:db:test-instance"
        },
        {
            "SourceType": "db-instance",
            "SourceIdentifier": "test-instance",
            "EventCategories": [
                "backup"
            ],
            "Message": "Finished DB Instance backup",
            "Date": "2018-07-31T23:15:13.049Z",
            "SourceArn": "arn:aws:rds:us-east-1:123456789012:db:test-instance"
        }
    ]
}

Untuk detail API, lihat DescribeEvents di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-export-tasks.

AWS CLI

Untuk mendeskripsikan tugas ekspor snapshot

describe-export-tasksContoh berikut mengembalikan informasi tentang ekspor snapshot ke Amazon S3.


aws rds describe-export-tasks

Output:


{
    "ExportTasks": [
        {
            "ExportTaskIdentifier": "test-snapshot-export",
            "SourceArn": "arn:aws:rds:us-west-2:123456789012:snapshot:test-snapshot",
            "SnapshotTime": "2020-03-02T18:26:28.163Z",
            "TaskStartTime": "2020-03-02T18:57:56.896Z",
            "TaskEndTime": "2020-03-02T19:10:31.985Z",
            "S3Bucket": "amzn-s3-demo-bucket",
            "S3Prefix": "",
            "IamRoleArn": "arn:aws:iam::123456789012:role/service-role/ExportRole",
            "KmsKeyId": "arn:aws:kms:us-west-2:123456789012:key/abcd0000-7fca-4128-82f2-aabbccddeeff",
            "Status": "COMPLETE",
            "PercentProgress": 100,
            "TotalExtractedDataInGB": 0
        },
        {
            "ExportTaskIdentifier": "my-s3-export",
            "SourceArn": "arn:aws:rds:us-west-2:123456789012:snapshot:db5-snapshot-test",
            "SnapshotTime": "2020-03-27T20:48:42.023Z",
            "S3Bucket": "amzn-s3-demo-bucket",
            "S3Prefix": "",
            "IamRoleArn": "arn:aws:iam::123456789012:role/service-role/ExportRole",
            "KmsKeyId": "arn:aws:kms:us-west-2:123456789012:key/abcd0000-7fca-4128-82f2-aabbccddeeff",
            "Status": "STARTING",
            "PercentProgress": 0,
            "TotalExtractedDataInGB": 0
        }
    ]
}

Untuk informasi selengkapnya, lihat Memantau Ek spor Snapshot di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeExportTasks di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-global-clusters.

AWS CLI

Untuk mendeskripsikan cluster DB global

describe-global-clustersContoh berikut mencantumkan cluster DB global Aurora di Wil AWS ayah saat ini.


aws rds describe-global-clusters

Output:


{
    "GlobalClusters": [
        {
            "GlobalClusterIdentifier": "myglobalcluster",
            "GlobalClusterResourceId": "cluster-f5982077e3b5aabb",
            "GlobalClusterArn": "arn:aws:rds::123456789012:global-cluster:myglobalcluster",
            "Status": "available",
            "Engine": "aurora-mysql",
            "EngineVersion": "5.7.mysql_aurora.2.07.2",
            "StorageEncrypted": false,
            "DeletionProtection": false,
            "GlobalClusterMembers": []
        }
    ]
}

Untuk informasi selengkapnya, lihat M engelola database global Aurora di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat DescribeGlobalClusters di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-option-group-options.

AWS CLI

Untuk menjelaskan semua opsi yang tersedia

describe-option-group-optionsContoh berikut mencantumkan dua opsi untuk instance Oracle Database 19c.


aws rds describe-option-group-options \
    --engine-name oracle-ee \
    --major-engine-version 19 \
    --max-items 2

Output:


{
    "OptionGroupOptions": [
        {
            "Name": "APEX",
            "Description": "Oracle Application Express Runtime Environment",
            "EngineName": "oracle-ee",
            "MajorEngineVersion": "19",
            "MinimumRequiredMinorEngineVersion": "0.0.0.ru-2019-07.rur-2019-07.r1",
            "PortRequired": false,
            "OptionsDependedOn": [],
            "OptionsConflictsWith": [],
            "Persistent": false,
            "Permanent": false,
            "RequiresAutoMinorEngineVersionUpgrade": false,
            "VpcOnly": false,
            "SupportsOptionVersionDowngrade": false,
            "OptionGroupOptionSettings": [],
            "OptionGroupOptionVersions": [
                {
                    "Version": "19.1.v1",
                    "IsDefault": true
                },
                {
                    "Version": "19.2.v1",
                    "IsDefault": false
                }
            ]
        },
        {
            "Name": "APEX-DEV",
            "Description": "Oracle Application Express Development Environment",
            "EngineName": "oracle-ee",
            "MajorEngineVersion": "19",
            "MinimumRequiredMinorEngineVersion": "0.0.0.ru-2019-07.rur-2019-07.r1",
            "PortRequired": false,
            "OptionsDependedOn": [
                "APEX"
            ],
            "OptionsConflictsWith": [],
            "Persistent": false,
            "Permanent": false,
            "RequiresAutoMinorEngineVersionUpgrade": false,
            "VpcOnly": false,
            "OptionGroupOptionSettings": []
        }
    ],
    "NextToken": "eyJNYXJrZXIiOiBudWxsLCAiYm90b190cnVuY2F0ZV9hbW91bnQiOiAyfQ=="
}

Untuk informasi selengkapnya, lihat Daftar Opsi dan Pengaturan Opsi untuk Grup Opsi di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeOptionGroupOptions di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-option-groups.

AWS CLI

Untuk menjelaskan grup opsi yang tersedia

describe-option-groupsContoh berikut mencantumkan grup opsi untuk instance Oracle Database 19c.


aws rds describe-option-groups \
    --engine-name oracle-ee \
    --major-engine-version 19

Output:


{
    "OptionGroupsList": [
        {
            "OptionGroupName": "default:oracle-ee-19",
            "OptionGroupDescription": "Default option group for oracle-ee 19",
            "EngineName": "oracle-ee",
            "MajorEngineVersion": "19",
            "Options": [],
            "AllowsVpcAndNonVpcInstanceMemberships": true,
            "OptionGroupArn": "arn:aws:rds:us-west-1:111122223333:og:default:oracle-ee-19"
        }
    ]
}

Untuk informasi selengkapnya, lihat Daftar Opsi dan Pengaturan Opsi untuk Grup Opsi di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeOptionGroups di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-orderable-db-instance-options.

AWS CLI

Untuk menjelaskan opsi instans DB yang dapat diurutkan

describe-orderable-db-instance-optionsContoh berikut mengambil detail tentang opsi yang dapat diurutkan untuk instance DB yang menjalankan mesin DB MySQL.


aws rds describe-orderable-db-instance-options \
    --engine mysql

Output:


{
    "OrderableDBInstanceOptions": [
        {
            "MinStorageSize": 5,
            "ReadReplicaCapable": true,
            "MaxStorageSize": 6144,
            "AvailabilityZones": [
                {
                    "Name": "us-east-1a"
                },
                {
                    "Name": "us-east-1b"
                },
                {
                    "Name": "us-east-1c"
                },
                {
                    "Name": "us-east-1d"
                }
            ],
            "SupportsIops": false,
            "AvailableProcessorFeatures": [],
            "MultiAZCapable": true,
            "DBInstanceClass": "db.m1.large",
            "Vpc": true,
            "StorageType": "gp2",
            "LicenseModel": "general-public-license",
            "EngineVersion": "5.5.46",
            "SupportsStorageEncryption": false,
            "SupportsEnhancedMonitoring": true,
            "Engine": "mysql",
            "SupportsIAMDatabaseAuthentication": false,
            "SupportsPerformanceInsights": false
        }
    ]
    ...some output truncated...
}

Untuk detail API, lihat DescribeOrderableDBInstanceOptions di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-pending-maintenance-actions.

AWS CLI

Untuk membuat daftar sumber daya dengan setidaknya satu tindakan pemeliharaan yang tertunda

describe-pending-maintenance-actionsContoh berikut mencantumkan tindakan pemeliharaan yang tertunda untuk instance DB.


aws rds describe-pending-maintenance-actions

Output:


{
    "PendingMaintenanceActions": [
        {
            "ResourceIdentifier": "arn:aws:rds:us-west-2:123456789012:cluster:global-db1-cl1",
            "PendingMaintenanceActionDetails": [
                {
                    "Action": "system-update",
                    "Description": "Upgrade to Aurora PostgreSQL 2.4.2"
                }
            ]
        }
    ]
}

Untuk informasi selengkapnya, lihat Memelihara Instans DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribePendingMaintenanceActions di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-reserved-db-instances-offerings.

AWS CLI

Untuk menjelaskan penawaran instans DB yang dicadangkan

describe-reserved-db-instances-offeringsContoh berikut mengambil detail tentang opsi instance DB yang dicadangkan untukoracle.


aws rds describe-reserved-db-instances-offerings \
    --product-description oracle

Output:


{
    "ReservedDBInstancesOfferings": [
        {
            "CurrencyCode": "USD",
            "UsagePrice": 0.0,
            "ProductDescription": "oracle-se2(li)",
            "ReservedDBInstancesOfferingId": "005bdee3-9ef4-4182-aa0c-58ef7cb6c2f8",
            "MultiAZ": true,
            "DBInstanceClass": "db.m4.xlarge",
            "OfferingType": "Partial Upfront",
            "RecurringCharges": [
                {
                    "RecurringChargeAmount": 0.594,
                    "RecurringChargeFrequency": "Hourly"
                }
            ],
            "FixedPrice": 4089.0,
            "Duration": 31536000
        },
    ...some output truncated...
}

Untuk detail API, lihat DescribeReservedDbInstancesOfferings di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-reserved-db-instances.

AWS CLI

Untuk mendeskripsikan instans DB yang dicadangkan

describe-reserved-db-instancesContoh berikut mengambil detail tentang instans DB yang dicadangkan di AWS akun saat ini.


aws rds describe-reserved-db-instances

Output:


{
    "ReservedDBInstances": [
        {
            "ReservedDBInstanceId": "myreservedinstance",
            "ReservedDBInstancesOfferingId": "12ab34cd-59af-4b2c-a660-1abcdef23456",
            "DBInstanceClass": "db.t3.micro",
            "StartTime": "2020-06-01T13:44:21.436Z",
            "Duration": 31536000,
            "FixedPrice": 0.0,
            "UsagePrice": 0.0,
            "CurrencyCode": "USD",
            "DBInstanceCount": 1,
            "ProductDescription": "sqlserver-ex(li)",
            "OfferingType": "No Upfront",
            "MultiAZ": false,
            "State": "payment-pending",
            "RecurringCharges": [
                {
                    "RecurringChargeAmount": 0.014,
                    "RecurringChargeFrequency": "Hourly"
                }
            ],
            "ReservedDBInstanceArn": "arn:aws:rds:us-west-2:123456789012:ri:myreservedinstance",
            "LeaseId": "a1b2c3d4-6b69-4a59-be89-5e11aa446666"
        }
    ]
}

Untuk informasi selengkapnya, lihat Instans DB Cadangan untuk Amazon RDS di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeReservedDbInstances di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-source-regions.

AWS CLI

Untuk mendeskripsikan Wilayah sumber

describe-source-regionsContoh berikut mengambil detail tentang semua Wil AWS ayah sumber. Ini juga menunjukkan bahwa backup otomatis hanya dapat direplikasi dari AS Barat (Oregon) ke Wil AWS ayah tujuan, AS Timur (Virginia Utara).


aws rds describe-source-regions \
    --region us-east-1

Output:


{
    "SourceRegions": [
        {
            "RegionName": "af-south-1",
            "Endpoint": "https://rds.af-south-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": false
        },
        {
            "RegionName": "ap-east-1",
            "Endpoint": "https://rds.ap-east-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": false
        },
        {
            "RegionName": "ap-northeast-1",
            "Endpoint": "https://rds.ap-northeast-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "ap-northeast-2",
            "Endpoint": "https://rds.ap-northeast-2.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "ap-northeast-3",
            "Endpoint": "https://rds.ap-northeast-3.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": false
        },
        {
            "RegionName": "ap-south-1",
            "Endpoint": "https://rds.ap-south-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "ap-southeast-1",
            "Endpoint": "https://rds.ap-southeast-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "ap-southeast-2",
            "Endpoint": "https://rds.ap-southeast-2.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "ap-southeast-3",
            "Endpoint": "https://rds.ap-southeast-3.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": false
        },
        {
            "RegionName": "ca-central-1",
            "Endpoint": "https://rds.ca-central-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "eu-north-1",
            "Endpoint": "https://rds.eu-north-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "eu-south-1",
            "Endpoint": "https://rds.eu-south-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": false
        },
        {
            "RegionName": "eu-west-1",
            "Endpoint": "https://rds.eu-west-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "eu-west-2",
            "Endpoint": "https://rds.eu-west-2.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "eu-west-3",
            "Endpoint": "https://rds.eu-west-3.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "me-central-1",
             "Endpoint": "https://rds.me-central-1.amazonaws.com",
             "Status": "available",
             "SupportsDBInstanceAutomatedBackupsReplication": false
        },
        {
            "RegionName": "me-south-1",
            "Endpoint": "https://rds.me-south-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": false
        },
        {
            "RegionName": "sa-east-1",
            "Endpoint": "https://rds.sa-east-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "us-east-2",
            "Endpoint": "https://rds.us-east-2.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "us-west-1",
            "Endpoint": "https://rds.us-west-1.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        },
        {
            "RegionName": "us-west-2",
           "Endpoint": "https://rds.us-west-2.amazonaws.com",
            "Status": "available",
            "SupportsDBInstanceAutomatedBackupsReplication": true
        }
    ]
}

Untuk informasi selengkapnya, lihat Menemukan informasi tentang cadangan yang direplikasi di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat DescribeSourceRegions di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandescribe-valid-db-instance-modifications.

AWS CLI

Untuk menjelaskan modifikasi yang valid untuk instance DB

describe-valid-db-instance-modificationsContoh berikut mengambil rincian tentang modifikasi yang valid untuk instance DB yang ditentukan.


aws rds describe-valid-db-instance-modifications \
    --db-instance-identifier test-instance

Output:


{
    "ValidDBInstanceModificationsMessage": {
        "ValidProcessorFeatures": [],
        "Storage": [
            {
                "StorageSize": [
                    {
                        "Step": 1,
                        "To": 20,
                        "From": 20
                    },
                    {
                        "Step": 1,
                        "To": 6144,
                        "From": 22
                    }
                ],
                "ProvisionedIops": [
                    {
                        "Step": 1,
                        "To": 0,
                        "From": 0
                    }
                ],
                "IopsToStorageRatio": [
                    {
                        "To": 0.0,
                        "From": 0.0
                    }
                ],
                "StorageType": "gp2"
            },
            {
                "StorageSize": [
                    {
                        "Step": 1,
                        "To": 6144,
                        "From": 100
                    }
                ],
                "ProvisionedIops": [
                    {
                        "Step": 1,
                        "To": 40000,
                        "From": 1000
                    }
                ],
                "IopsToStorageRatio": [
                    {
                        "To": 50.0,
                        "From": 1.0
                    }
                ],
                "StorageType": "io1"
            },
            {
                "StorageSize": [
                    {
                        "Step": 1,
                        "To": 20,
                        "From": 20
                    },
                    {
                        "Step": 1,
                        "To": 3072,
                        "From": 22
                    }
                ],
                "ProvisionedIops": [
                    {
                        "Step": 1,
                        "To": 0,
                        "From": 0
                    }
                ],
                "IopsToStorageRatio": [
                    {
                        "To": 0.0,
                        "From": 0.0
                    }
                ],
                "StorageType": "magnetic"
            }
        ]
    }
}

Untuk detail API, lihat DescribeValidDbInstanceModifications di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakandownload-db-log-file-portion.

AWS CLI

Contoh 1: Untuk mengunduh bagian terbaru dari file log DB

download-db-log-file-portionContoh berikut hanya mengunduh bagian terbaru dari file log Anda, menyimpannya ke file lokal bernamatail.txt.


aws rds download-db-log-file-portion \
    --db-instance-identifier test-instance \
    --log-file-name log.txt \
    --output text > tail.txt

File yang disimpan mungkin berisi baris kosong. Mereka muncul di akhir setiap bagian dari file log saat diunduh.

Contoh 2: Untuk mengunduh seluruh file log DB

download-db-log-file-portionContoh berikut mengunduh seluruh file log, menggunakan --starting-token 0 parameter, dan menyimpan output ke file lokal bernamafull.txt.


aws rds download-db-log-file-portion \
    --db-instance-identifier test-instance \
    --log-file-name log.txt \
    --starting-token 0 \
    --output text > full.txt

File yang disimpan mungkin berisi baris kosong. Mereka muncul di akhir setiap bagian dari file log saat diunduh.

Untuk detail API, lihat DownloadDbLogFilePortion di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakangenerate-auth-token.

AWS CLI

Untuk menghasilkan token otentikasi

generate-db-auth-tokenContoh berikut menghasilkan token otentikasi untuk digunakan dengan otentikasi database IAM.


aws rds generate-db-auth-token \
    --hostname aurmysql-test.cdgmuqiadpid.us-west-2.rds.amazonaws.com \
    --port 3306 \
    --region us-east-1 \
    --username jane_doe

Output:


aurmysql-test.cdgmuqiadpid.us-west-2.rds.amazonaws.com:3306/?Action=connect&DBUser=jane_doe&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIESZCNJ3OEXAMPLE%2F20180731%2Fus-east-1%2Frds-db%2Faws4_request&X-Amz-Date=20180731T235209Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=5a8753ebEXAMPLEa2c724e5667797EXAMPLE9d6ec6e3f427191fa41aeEXAMPLE

Untuk detail API, lihat GenerateAuthToken di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakangenerate-db-auth-token.

AWS CLI

Untuk menghasilkan token otentikasi IAM

generate-db-auth-tokenContoh berikut menghasilkan token otentikasi IAM untuk terhubung ke database.


aws rds generate-db-auth-token \
    --hostname mydb.123456789012.us-east-1.rds.amazonaws.com \
    --port 3306 \
    --region us-east-1 \
    --username db_user

Output:


mydb.123456789012.us-east-1.rds.amazonaws.com:3306/?Action=connect&DBUser=db_user&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIEXAMPLE%2Fus-east-1%2Frds-db%2Faws4_request&X-Amz-Date=20210123T011543Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=88987EXAMPLE1EXAMPLE2EXAMPLE3EXAMPLE4EXAMPLE5EXAMPLE6

Untuk informasi selengkapnya, lihat Menghubungkan ke instans DB menggunakan otentikasi IAM di Panduan Pengguna Amazon RDS dan Mengh ubungkan ke cluster DB menggunakan otentikasi IAM di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat GenerateDbAuthToken di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanlist-tags-for-resource.

AWS CLI

Untuk mencantumkan tag pada sumber daya Amazon RDS

list-tags-for-resourceContoh berikut mencantumkan semua tag pada instance DB.


aws rds list-tags-for-resource \
    --resource-name arn:aws:rds:us-east-1:123456789012:db:orcl1

Output:


{
    "TagList": [
        {
            "Key": "Environment",
            "Value": "test"
        },
        {
            "Key": "Name",
            "Value": "MyDatabase"
        }
    ]
}

Untuk informasi selengkapnya, lihat Menandai Sumber Daya Amazon RDS di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat ListTagsForResource di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-certificates.

AWS CLI

Untuk mengganti sementara SSL/TLS sertifikat default sistem untuk instans DB baru

modify-certificatesContoh berikut untuk sementara mengganti SSL/TLS sertifikat default sistem untuk instans DB baru.


aws rds modify-certificates \
    --certificate-identifier rds-ca-2019

Output:


{
    "Certificate": {
        "CertificateIdentifier": "rds-ca-2019",
        "CertificateType": "CA",
        "Thumbprint": "EXAMPLE123456789012",
        "ValidFrom": "2019-09-19T18:16:53Z",
        "ValidTill": "2024-08-22T17:08:50Z",
        "CertificateArn": "arn:aws:rds:us-east-1::cert:rds-ca-2019",
        "CustomerOverride": true,
        "CustomerOverrideValidTill": "2024-08-22T17:08:50Z"
    }
}

Untuk informasi selengkapnya, lihat Memut SSL/TLS ar sertifikat Anda di Panduan Pengguna Amazon RDS dan Memutar SSL/TLS sertifikat Anda di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ModifyCertificates di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-current-db-cluster-capacity.

AWS CLI

Untuk meningkatkan kapasitas cluster Aurora Serverless DB

modify-current-db-cluster-capacityContoh berikut menskalakan kapasitas cluster Aurora Serverless DB menjadi 8.


aws rds modify-current-db-cluster-capacity \
    --db-cluster-identifier mydbcluster \
    --capacity 8

Output:


{
    "DBClusterIdentifier": "mydbcluster",
    "PendingCapacity": 8,
    "CurrentCapacity": 1,
    "SecondsBeforeTimeout": 300,
    "TimeoutAction": "ForceApplyCapacityChange"
}

Untuk informasi selengkapnya, lihat Menskalakan kapasitas cluster Aurora Serverless v1 DB secara manual di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ModifyCurrentDbClusterCapacity di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-cluster-endpoint.

AWS CLI

Untuk memodifikasi titik akhir cluster DB kustom

modify-db-cluster-endpointContoh berikut memodifikasi titik akhir cluster DB kustom yang ditentukan.


aws rds modify-db-cluster-endpoint \
    --db-cluster-endpoint-identifier mycustomendpoint \
    --static-members dbinstance1 dbinstance2 dbinstance3

Output:


{
    "DBClusterEndpointIdentifier": "mycustomendpoint",
    "DBClusterIdentifier": "mydbcluster",
    "DBClusterEndpointResourceIdentifier": "cluster-endpoint-ANPAJ4AE5446DAEXAMPLE",
    "Endpoint": "mycustomendpoint.cluster-custom-cnpexample.us-east-1.rds.amazonaws.com",
    "Status": "modifying",
    "EndpointType": "CUSTOM",
    "CustomEndpointType": "READER",
    "StaticMembers": [
        "dbinstance1",
        "dbinstance2",
        "dbinstance3"
    ],
    "ExcludedMembers": [],
    "DBClusterEndpointArn": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:mycustomendpoint"
}

Untuk informasi selengkapnya, lihat Manajemen Koneksi Amazon Aurora di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ModifyDbClusterEndpoint di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-cluster-parameter-group.

AWS CLI

Untuk memodifikasi parameter dalam grup parameter cluster DB

modify-db-cluster-parameter-groupContoh berikut memodifikasi nilai-nilai parameter dalam kelompok parameter cluster DB.


aws rds modify-db-cluster-parameter-group \
    --db-cluster-parameter-group-name mydbclusterpg \
    --parameters "ParameterName=server_audit_logging,ParameterValue=1,ApplyMethod=immediate" \
                 "ParameterName=server_audit_logs_upload,ParameterValue=1,ApplyMethod=immediate"

Output:


{
    "DBClusterParameterGroupName": "mydbclusterpg"
}

Untuk informasi selengkapnya, lihat Bek erja dengan grup parameter DB dan grup parameter cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ModifyDbClusterParameterGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-cluster-snapshot-attribute.

AWS CLI

Untuk memodifikasi atribut snapshot cluster DB

modify-db-cluster-snapshot-attributeContoh berikut membuat perubahan pada atribut snapshot cluster DB yang ditentukan.


aws rds modify-db-cluster-snapshot-attribute \
    --db-cluster-snapshot-identifier myclustersnapshot \
    --attribute-name restore \
    --values-to-add 123456789012

Output:


{
    "DBClusterSnapshotAttributesResult": {
        "DBClusterSnapshotIdentifier": "myclustersnapshot",
        "DBClusterSnapshotAttributes": [
            {
                "AttributeName": "restore",
                "AttributeValues": [
                    "123456789012"
                ]
            }
        ]
    }
}

Untuk informasi selengkapnya, lihat Memulihkan dari Snapshot Cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ModifyDbClusterSnapshotAttribute di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-cluster.

AWS CLI

Contoh 1: Untuk memodifikasi cluster DB

modify-db-clusterContoh berikut mengubah kata sandi pengguna utama untuk cluster DB bernama cluster-2 dan menetapkan periode retensi cadangan menjadi 14 hari. --apply-immediatelyParameter menyebabkan perubahan dilakukan segera, alih-alih menunggu sampai jendela pemeliharaan berikutnya.


aws rds modify-db-cluster \
    --db-cluster-identifier cluster-2 \
    --backup-retention-period 14 \
    --master-user-password newpassword99 \
    --apply-immediately

Output:


{
    "DBCluster": {
        "AllocatedStorage": 1,
        "AvailabilityZones": [
            "eu-central-1b",
            "eu-central-1c",
            "eu-central-1a"
        ],
        "BackupRetentionPeriod": 14,
        "DatabaseName": "",
        "DBClusterIdentifier": "cluster-2",
        "DBClusterParameterGroup": "default.aurora5.6",
        "DBSubnetGroup": "default-vpc-2305ca49",
        "Status": "available",
        "EarliestRestorableTime": "2020-06-03T02:07:29.637Z",
        "Endpoint": "cluster-2.cluster-############.eu-central-1.rds.amazonaws.com",
        "ReaderEndpoint": "cluster-2.cluster-ro-############.eu-central-1.rds.amazonaws.com",
        "MultiAZ": false,
        "Engine": "aurora",
        "EngineVersion": "5.6.10a",
        "LatestRestorableTime": "2020-06-04T15:11:25.748Z",
        "Port": 3306,
        "MasterUsername": "admin",
        "PreferredBackupWindow": "01:55-02:25",
        "PreferredMaintenanceWindow": "thu:21:14-thu:21:44",
        "ReadReplicaIdentifiers": [],
        "DBClusterMembers": [
            {
                "DBInstanceIdentifier": "cluster-2-instance-1",
                "IsClusterWriter": true,
                "DBClusterParameterGroupStatus": "in-sync",
                "PromotionTier": 1
            }
        ],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sg-20a5c047",
                "Status": "active"
            }
        ],
        "HostedZoneId": "Z1RLNU0EXAMPLE",
        "StorageEncrypted": true,
        "KmsKeyId": "arn:aws:kms:eu-central-1:123456789012:key/d1bd7c8f-5cdb-49ca-8a62-a1b2c3d4e5f6",
        "DbClusterResourceId": "cluster-AGJ7XI77XVIS6FUXHU1EXAMPLE",
        "DBClusterArn": "arn:aws:rds:eu-central-1:123456789012:cluster:cluster-2",
        "AssociatedRoles": [],
        "IAMDatabaseAuthenticationEnabled": false,
        "ClusterCreateTime": "2020-04-03T14:44:02.764Z",
        "EngineMode": "provisioned",
        "DeletionProtection": false,
        "HttpEndpointEnabled": false,
        "CopyTagsToSnapshot": true,
        "CrossAccountClone": false,
        "DomainMemberships": []
    }
}

Untuk informasi selengkapnya, lihat Memo difikasi Cluster DB Amazon Aurora di Panduan Pengguna Amazon Aurora.

Contoh 2: Untuk mengaitkan grup keamanan VPC dengan cluster DB

modify-db-instanceContoh berikut mengaitkan grup keamanan VPC tertentu dan menghapus grup keamanan DB dari cluster DB.


aws rds modify-db-cluster \
    --db-cluster-identifier dbName \
    --vpc-security-group-ids sg-ID

Output:


{
    "DBCluster": {
        "AllocatedStorage": 1,
        "AvailabilityZones": [
            "us-west-2c",
            "us-west-2b",
            "us-west-2a"
        ],
        "BackupRetentionPeriod": 1,
        "DBClusterIdentifier": "dbName",
        "DBClusterParameterGroup": "default.aurora-mysql8.0",
        "DBSubnetGroup": "default",
        "Status": "available",
        "EarliestRestorableTime": "2024-02-15T01:12:13.966000+00:00",
        "Endpoint": "dbName.cluster-abcdefghji.us-west-2.rds.amazonaws.com",
        "ReaderEndpoint": "dbName.cluster-ro-abcdefghji.us-west-2.rds.amazonaws.com",
        "MultiAZ": false,
        "Engine": "aurora-mysql",
        "EngineVersion": "8.0.mysql_aurora.3.04.1",
        "LatestRestorableTime": "2024-02-15T02:25:33.696000+00:00",
        "Port": 3306,
        "MasterUsername": "admin",
        "PreferredBackupWindow": "10:59-11:29",
        "PreferredMaintenanceWindow": "thu:08:54-thu:09:24",
        "ReadReplicaIdentifiers": [],
        "DBClusterMembers": [
            {
                "DBInstanceIdentifier": "dbName-instance-1",
                "IsClusterWriter": true,
                "DBClusterParameterGroupStatus": "in-sync",
                "PromotionTier": 1
            }
        ],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sg-ID",
                "Status": "active"
            }
        ],
        ...output omitted...
    }
}

Untuk informasi selengkapnya, lihat Mengon trol akses dengan grup Keamanan di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ModifyDbCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-instance.

AWS CLI

Contoh 1: Untuk memodifikasi instance DB

modify-db-instanceContoh berikut mengaitkan grup opsi dan grup parameter dengan instance Microsoft SQL Server DB yang kompatibel. --apply-immediatelyParameter menyebabkan opsi dan grup parameter segera dikaitkan, alih-alih menunggu sampai jendela pemeliharaan berikutnya.


aws rds modify-db-instance \
    --db-instance-identifier database-2 \
    --option-group-name test-se-2017 \
    --db-parameter-group-name test-sqlserver-se-2017 \
    --apply-immediately

Output:


{
    "DBInstance": {
        "DBInstanceIdentifier": "database-2",
        "DBInstanceClass": "db.r4.large",
        "Engine": "sqlserver-se",
        "DBInstanceStatus": "available",

        ...output omitted...

        "DBParameterGroups": [
            {
                "DBParameterGroupName": "test-sqlserver-se-2017",
                "ParameterApplyStatus": "applying"
            }
        ],
        "AvailabilityZone": "us-west-2d",

        ...output omitted...

        "MultiAZ": true,
        "EngineVersion": "14.00.3281.6.v1",
        "AutoMinorVersionUpgrade": false,
        "ReadReplicaDBInstanceIdentifiers": [],
        "LicenseModel": "license-included",
        "OptionGroupMemberships": [
            {
                "OptionGroupName": "test-se-2017",
                "Status": "pending-apply"
            }
        ],
        "CharacterSetName": "SQL_Latin1_General_CP1_CI_AS",
        "SecondaryAvailabilityZone": "us-west-2c",
        "PubliclyAccessible": true,
        "StorageType": "gp2",

        ...output omitted...

        "DeletionProtection": false,
        "AssociatedRoles": [],
        "MaxAllocatedStorage": 1000
    }
}

Untuk informasi selengkapnya, lihat Memodifikasi Instans DB Amazon RDS di Panduan Pengguna Amazon RDS.

Contoh 2: Untuk mengaitkan grup keamanan VPC dengan instance DB

modify-db-instanceContoh berikut mengaitkan grup keamanan VPC tertentu dan menghapus grup keamanan DB dari instance DB:


aws rds modify-db-instance \
    --db-instance-identifier dbName \
    --vpc-security-group-ids sg-ID

Output:


{
"DBInstance": {
    "DBInstanceIdentifier": "dbName",
    "DBInstanceClass": "db.t3.micro",
    "Engine": "mysql",
    "DBInstanceStatus": "available",
    "MasterUsername": "admin",
    "Endpoint": {
        "Address": "dbName.abcdefghijk.us-west-2.rds.amazonaws.com",
        "Port": 3306,
        "HostedZoneId": "ABCDEFGHIJK1234"
    },
    "AllocatedStorage": 20,
    "InstanceCreateTime": "2024-02-15T00:37:58.793000+00:00",
    "PreferredBackupWindow": "11:57-12:27",
    "BackupRetentionPeriod": 7,
    "DBSecurityGroups": [],
    "VpcSecurityGroups": [
        {
            "VpcSecurityGroupId": "sg-ID",
            "Status": "active"
        }
    ],
    ... output omitted ...
    "MultiAZ": false,
    "EngineVersion": "8.0.35",
    "AutoMinorVersionUpgrade": true,
    "ReadReplicaDBInstanceIdentifiers": [],
    "LicenseModel": "general-public-license",

    ... output omitted ...
    }
}

Untuk informasi selengkapnya, lihat Mengontrol akses dengan grup Keamanan di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat ModifyDBInstance di Referensi Perintah. AWS CLI

Contoh kode berikut menunjukkan cara menggunakanmodify-db-parameter-group.

AWS CLI

Untuk memodifikasi grup parameter DB

modify-db-parameter-groupContoh berikut mengubah nilai clr enabled parameter dalam kelompok parameter DB. --apply-immediatelyParameter menyebabkan grup parameter DB segera dimodifikasi, alih-alih menunggu sampai jendela pemeliharaan berikutnya.


aws rds modify-db-parameter-group \
    --db-parameter-group-name test-sqlserver-se-2017 \
    --parameters "ParameterName='clr enabled',ParameterValue=1,ApplyMethod=immediate"

Output:


{
    "DBParameterGroupName": "test-sqlserver-se-2017"
}

Untuk informasi selengkapnya, lihat Memodifikasi Parameter dalam Grup Parameter DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat ModifyDBParameterGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-proxy-endpoint.

AWS CLI

Untuk memodifikasi titik akhir proxy DB untuk database RDS

modify-db-proxy-endpointContoh berikut memodifikasi titik akhir proxy DB proxyEndpoint untuk mengatur batas waktu baca menjadi 65 detik.


aws rds modify-db-proxy-endpoint \
    --db-proxy-endpoint-name proxyEndpoint \
    --cli-read-timeout 65

Output:


{
"DBProxyEndpoint":
    {
        "DBProxyEndpointName": "proxyEndpoint",
        "DBProxyEndpointArn": "arn:aws:rds:us-east-1:123456789012:db-proxy-endpoint:prx-endpoint-0123a01b12345c0ab",
        "DBProxyName": "proxyExample",
        "Status": "available",
        "VpcId": "vpc-1234567",
        "VpcSecurityGroupIds": [
            "sg-1234"
        ],
        "VpcSubnetIds": [
            "subnetgroup1",
            "subnetgroup2"
        ],
        "Endpoint": "proxyEndpoint.endpoint.proxyExample-ab0cd1efghij.us-east-1.rds.amazonaws.com",
        "CreatedDate": "2023-04-05T16:09:33.452000+00:00",
        "TargetRole": "READ_WRITE",
        "IsDefault": "false"
    }
}

Untuk informasi selengkapnya, lihat Memodifikasi titik akhir proxy di Panduan Pengguna Amazon RDS dan M emodifikasi titik akhir proxy di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ModifyDbProxyEndpoint di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-proxy-target-group.

AWS CLI

Untuk memodifikasi titik akhir proxy DB

modify-db-proxy-target-groupContoh berikut memodifikasi grup target proxy DB untuk mengatur koneksi maksimum ke 80 persen dan koneksi idle maksimum ke 10 persen.


aws rds modify-db-proxy-target-group \
    --target-group-name default \
    --db-proxy-name proxyExample \
    --connection-pool-config MaxConnectionsPercent=80,MaxIdleConnectionsPercent=10

Output:


{
"DBProxyTargetGroup":
    {
        "DBProxyName": "proxyExample",
        "TargetGroupName": "default",
        "TargetGroupArn": "arn:aws:rds:us-east-1:123456789012:target-group:prx-tg-0123a01b12345c0ab",
        "IsDefault": true,
        "Status": "available",
        "ConnectionPoolConfig": {
            "MaxConnectionsPercent": 80,
            "MaxIdleConnectionsPercent": 10,
            "ConnectionBorrowTimeout": 120,
            "SessionPinningFilters": []
        },
        "CreatedDate": "2023-05-02T18:41:19.495000+00:00",
        "UpdatedDate": "2023-05-02T18:41:21.762000+00:00"
    }
}

Untuk informasi selengkapnya, lihat Memodifikasi Proxy RDS di Panduan Pengguna Amazon RDS dan Memo difikasi Proksi RDS di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ModifyDbProxyTargetGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-proxy.

AWS CLI

Untuk memodifikasi proxy DB untuk database RDS

modify-db-proxyContoh berikut memodifikasi proxy DB bernama proxyExample untuk memerlukan SSL untuk koneksinya.


aws rds modify-db-proxy \
    --db-proxy-name proxyExample \
    --require-tls

Output:


{
"DBProxy":
    {
        "DBProxyName": "proxyExample",
        "DBProxyArn": "arn:aws:rds:us-east-1:123456789012:db-proxy:prx-0123a01b12345c0ab",
        "Status": "modifying"
        "EngineFamily": "PostgreSQL",
        "VpcId": "sg-1234567",
        "VpcSecurityGroupIds": [
            "sg-1234"
        ],
        "VpcSubnetIds": [
            "subnetgroup1",
            "subnetgroup2"
        ],
        "Auth": "[
            {
                "Description": "proxydescription1",
                "AuthScheme": "SECRETS",
                "SecretArn": "arn:aws:secretsmanager:us-west-2:123456789123:secret:proxysecret1-Abcd1e",
                "IAMAuth": "DISABLED"
            }
        ]",
        "RoleArn": "arn:aws:iam::12345678912:role/ProxyPostgreSQLRole",
        "Endpoint": "proxyExample.proxy-ab0cd1efghij.us-east-1.rds.amazonaws.com",
        "RequireTLS": true,
        "IdleClientTimeout": 1800,
        "DebuggingLogging": false,
        "CreatedDate": "2023-04-05T16:09:33.452000+00:00",
        "UpdatedDate": "2023-04-13T01:49:38.568000+00:00"
    }
}

Untuk informasi selengkapnya, lihat Memodi fikasi Proxy RDS di Panduan Pengguna Amazon RDS dan Membuat Proksi RDS di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ModifyDbProxy di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-shard-group.

AWS CLI

Contoh 1: Untuk memodifikasi grup pecahan DB

modify-db-shard-groupContoh berikut mengubah kapasitas maksimum grup pecahan DB.


aws rds modify-db-shard-group \
    --db-shard-group-identifier my-db-shard-group \
    --max-acu 1000

Output:


{
    "DBShardGroups": [
        {
            "DBShardGroupResourceId": "shardgroup-a6e3a0226aa243e2ac6c7a1234567890",
            "DBShardGroupIdentifier": "my-db-shard-group",
            "DBClusterIdentifier": "my-sv2-cluster",
            "MaxACU": 768.0,
            "ComputeRedundancy": 0,
            "Status": "available",
            "PubliclyAccessible": false,
            "Endpoint": "my-sv2-cluster.limitless-cekycexample.us-east-2.rds.amazonaws.com"
        }
    ]
}

Untuk informasi selengkapnya, lihat Amazon Aurora DB Cluster di Panduan Pengguna Amazon Aurora.

Contoh 2: Untuk menggambarkan grup pecahan DB Anda

describe-db-shard-groupsContoh berikut mengambil rincian grup pecahan DB Anda setelah Anda menjalankan perintahmodify-db-shard-group. Kapasitas maksimum kelompok pecahan DB sekarang my-db-shard-group adalah 1000 unit kapasitas Aurora (ACU).


aws rds describe-db-shard-groups

Output:


{
    "DBShardGroups": [
        {
            "DBShardGroupResourceId": "shardgroup-7bb446329da94788b3f957746example",
            "DBShardGroupIdentifier": "limitless-test-shard-grp",
            "DBClusterIdentifier": "limitless-test-cluster",
            "MaxACU": 768.0,
            "ComputeRedundancy": 0,
            "Status": "available",
            "PubliclyAccessible": true,
            "Endpoint": "limitless-test-cluster.limitless-cekycexample.us-east-2.rds.amazonaws.com"
        },
        {
            "DBShardGroupResourceId": "shardgroup-a6e3a0226aa243e2ac6c7a1234567890",
            "DBShardGroupIdentifier": "my-db-shard-group",
            "DBClusterIdentifier": "my-sv2-cluster",
            "MaxACU": 1000.0,
            "ComputeRedundancy": 0,
            "Status": "available",
            "PubliclyAccessible": false,
            "Endpoint": "my-sv2-cluster.limitless-cekycexample.us-east-2.rds.amazonaws.com"
        }
    ]
}

Untuk informasi selengkapnya, lihat Amazon Aurora DB Cluster di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ModifyDbShardGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-snapshot-attribute.

AWS CLI

Contoh 1: Untuk mengaktifkan dua AWS akun untuk memulihkan snapshot DB

modify-db-snapshot-attributeContoh berikut memberikan izin ke dua AWS akun, dengan pengidentifikasi 111122223333 dan444455556666, untuk memulihkan snapshot DB bernamamydbsnapshot.


aws rds modify-db-snapshot-attribute \
    --db-snapshot-identifier mydbsnapshot \
    --attribute-name restore \
    --values-to-add {"111122223333","444455556666"}

Output:


{
    "DBSnapshotAttributesResult": {
        "DBSnapshotIdentifier": "mydbsnapshot",
        "DBSnapshotAttributes": [
            {
                "AttributeName": "restore",
                "AttributeValues": [
                    "111122223333",
                    "444455556666"
                ]
            }
        ]
    }
}

Untuk informasi selengkapnya, lihat Berbagi Snapshot di Panduan Pengguna Amazon RDS.

Contoh 2: Untuk mencegah AWS akun memulihkan snapshot DB

modify-db-snapshot-attributeContoh berikut menghapus izin dari AWS akun tertentu untuk memulihkan snapshot DB bernamamydbsnapshot. Saat menentukan satu akun, pengenal akun tidak dapat dikelilingi oleh tanda kutip atau tanda kurung.


aws rds modify-db-snapshot-attribute \
    --db-snapshot-identifier mydbsnapshot \
    --attribute-name restore \
    --values-to-remove 444455556666

Output:


{
    "DBSnapshotAttributesResult": {
        "DBSnapshotIdentifier": "mydbsnapshot",
        "DBSnapshotAttributes": [
            {
                "AttributeName": "restore",
                "AttributeValues": [
                    "111122223333"
                ]
            }
        ]
    }
}

Untuk informasi selengkapnya, lihat Berbagi Snapshot di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat ModifyDbSnapshotAttribute di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-snapshot-attributes.

AWS CLI

Untuk mengubah atribut snapshot DB

modify-db-snapshot-attributeContoh berikut mengizinkan dua pengenal AWS akun444455556666, 111122223333 dan, untuk mengembalikan snapshot DB bernamamydbsnapshot.


aws rds modify-db-snapshot-attribute \
    --db-snapshot-identifier mydbsnapshot \
    --attribute-name restore \
    --values-to-add '["111122223333","444455556666"]'

Output:


{
    "DBSnapshotAttributesResult": {
        "DBSnapshotIdentifier": "mydbsnapshot",
        "DBSnapshotAttributes": [
            {
                "AttributeName": "restore",
                "AttributeValues": [
                    "111122223333",
                    "444455556666"
                ]
            }
        ]
    }
}

Untuk informasi selengkapnya, lihat Berbagi Snapshot di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat ModifyDbSnapshotAttributes di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-snapshot.

AWS CLI

Untuk memodifikasi snapshot DB

modify-db-snapshotContoh berikut meningkatkan snapshot PostgeSQL 10.6 bernama db5-snapshot-upg-test PostgreSQL 11.7. Versi mesin DB baru ditampilkan setelah snapshot selesai ditingkatkan dan statusnya tersedia.


aws rds modify-db-snapshot \
    --db-snapshot-identifier db5-snapshot-upg-test \
    --engine-version 11.7

Output:


{
    "DBSnapshot": {
        "DBSnapshotIdentifier": "db5-snapshot-upg-test",
        "DBInstanceIdentifier": "database-5",
        "SnapshotCreateTime": "2020-03-27T20:49:17.092Z",
        "Engine": "postgres",
        "AllocatedStorage": 20,
        "Status": "upgrading",
        "Port": 5432,
        "AvailabilityZone": "us-west-2a",
        "VpcId": "vpc-2ff27557",
        "InstanceCreateTime": "2020-03-27T19:59:04.735Z",
        "MasterUsername": "postgres",
        "EngineVersion": "10.6",
        "LicenseModel": "postgresql-license",
        "SnapshotType": "manual",
        "OptionGroupName": "default:postgres-11",
        "PercentProgress": 100,
        "StorageType": "gp2",
        "Encrypted": false,
        "DBSnapshotArn": "arn:aws:rds:us-west-2:123456789012:snapshot:db5-snapshot-upg-test",
        "IAMDatabaseAuthenticationEnabled": false,
        "ProcessorFeatures": [],
        "DbiResourceId": "db-GJMF75LM42IL6BTFRE4UZJ5YM4"
    }
}

Untuk informasi selengkapnya, lihat Mengupgrade Snapshot DB PostgreSQL di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat ModifyDbSnapshot di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-db-subnet-group.

AWS CLI

Untuk memodifikasi grup subnet DB

modify-db-subnet-groupContoh berikut menambahkan subnet dengan ID subnet-08e41f9e230222222 ke grup subnet DB bernama. mysubnetgroup Untuk menjaga subnet yang ada di grup subnet, sertakan ID mereka sebagai nilai dalam opsi. --subnet-ids Pastikan untuk memiliki subnet dengan setidaknya dua Zona Ketersediaan yang berbeda dalam grup subnet DB.


aws rds modify-db-subnet-group \
    --db-subnet-group-name mysubnetgroup \
    --subnet-ids '["subnet-0a1dc4e1a6f123456","subnet-070dd7ecb3aaaaaaa","subnet-00f5b198bc0abcdef","subnet-08e41f9e230222222"]'

Output:


{
    "DBSubnetGroup": {
        "DBSubnetGroupName": "mysubnetgroup",
        "DBSubnetGroupDescription": "test DB subnet group",
        "VpcId": "vpc-0f08e7610a1b2c3d4",
        "SubnetGroupStatus": "Complete",
        "Subnets": [
            {
                "SubnetIdentifier": "subnet-08e41f9e230222222",
                "SubnetAvailabilityZone": {
                    "Name": "us-west-2a"
                },
                "SubnetStatus": "Active"
            },
            {
                "SubnetIdentifier": "subnet-070dd7ecb3aaaaaaa",
                "SubnetAvailabilityZone": {
                    "Name": "us-west-2b"
                },
                "SubnetStatus": "Active"
            },
            {
                "SubnetIdentifier": "subnet-00f5b198bc0abcdef",
                "SubnetAvailabilityZone": {
                    "Name": "us-west-2d"
                },
                "SubnetStatus": "Active"
            },
            {
                "SubnetIdentifier": "subnet-0a1dc4e1a6f123456",
                "SubnetAvailabilityZone": {
                    "Name": "us-west-2b"
                },
                "SubnetStatus": "Active"
            }
        ],
        "DBSubnetGroupArn": "arn:aws:rds:us-west-2:534026745191:subgrp:mysubnetgroup"
    }
}

Untuk informasi selengkapnya, lihat Langkah 3: Membuat Grup Subnet DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat ModifyDbSubnetGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-event-subscription.

AWS CLI

Untuk mengubah langganan acara

modify-event-subscriptionContoh berikut menonaktifkan langganan acara yang ditentukan, sehingga tidak lagi menerbitkan notifikasi ke topik Layanan Pemberitahuan Sederhana Amazon yang ditentukan.


aws rds modify-event-subscription \
    --subscription-name my-instance-events \
    --no-enabled

Output:


{
    "EventSubscription": {
        "EventCategoriesList": [
            "backup",
            "recovery"
        ],
        "CustomerAwsId": "123456789012",
        "SourceType": "db-instance",
        "SubscriptionCreationTime": "Tue Jul 31 23:22:01 UTC 2018",
        "EventSubscriptionArn": "arn:aws:rds:us-east-1:123456789012:es:my-instance-events",
        "SnsTopicArn": "arn:aws:sns:us-east-1:123456789012:interesting-events",
        "CustSubscriptionId": "my-instance-events",
        "Status": "modifying",
        "Enabled": false
    }
}

Untuk detail API, lihat ModifyEventSubscription di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanmodify-global-cluster.

AWS CLI

Untuk memodifikasi cluster DB global

modify-global-clusterContoh berikut memungkinkan perlindungan penghapusan untuk cluster DB MySQL-compatible global Aurora.


aws rds modify-global-cluster \
    --global-cluster-identifier myglobalcluster \
    --deletion-protection

Output:


{
    "GlobalCluster": {
        "GlobalClusterIdentifier": "myglobalcluster",
        "GlobalClusterResourceId": "cluster-f0e523bfe07aabb",
        "GlobalClusterArn": "arn:aws:rds::123456789012:global-cluster:myglobalcluster",
        "Status": "available",
        "Engine": "aurora-mysql",
        "EngineVersion": "5.7.mysql_aurora.2.07.2",
        "StorageEncrypted": false,
        "DeletionProtection": true,
        "GlobalClusterMembers": []
    }
}

Untuk informasi selengkapnya, lihat M engelola database global Aurora di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ModifyGlobalCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanpromote-read-replica-db-cluster.

AWS CLI

Untuk mempromosikan cluster DB baca replika

promote-read-replica-db-clusterContoh berikut mempromosikan replika baca yang ditentukan untuk menjadi cluster DB mandiri.


aws rds promote-read-replica-db-cluster \
    --db-cluster-identifier mydbcluster-1

Output:


{
    "DBCluster": {
        "AllocatedStorage": 1,
        "AvailabilityZones": [
            "us-east-1a",
            "us-east-1b",
            "us-east-1c"
        ],
        "BackupRetentionPeriod": 1,
        "DatabaseName": "",
        "DBClusterIdentifier": "mydbcluster-1",
        ...some output truncated...
    }
}

Untuk informasi selengkapnya, lihat Mem promosikan replika baca menjadi cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat PromoteReadReplicaDbCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanpromote-read-replica.

AWS CLI

Untuk mempromosikan replika baca

promote-read-replicaContoh berikut mempromosikan replika baca yang ditentukan untuk menjadi instance DB mandiri.


aws rds promote-read-replica \
    --db-instance-identifier test-instance-repl

Output:


{
    "DBInstance": {
        "DBInstanceArn": "arn:aws:rds:us-east-1:123456789012:db:test-instance-repl",
        "StorageType": "standard",
        "ReadReplicaSourceDBInstanceIdentifier": "test-instance",
        "DBInstanceStatus": "modifying",
        ...some output truncated...
    }
}

Untuk detail API, lihat PromoteReadReplica di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanpurchase-reserved-db-instance.

AWS CLI

Untuk membeli penawaran instans DB yang dicadangkan

purchase-reserved-db-instances-offeringContoh berikut membeli penawaran instans DB yang dicadangkan. Harus reserved-db-instances-offering-id berupa ID penawaran yang valid, seperti yang dikembalikan oleh describe-reserved-db-instances-offering perintah.

aws rds pembelian-cadangan-db-instances-penawaran --reserved-instances-db-instances-offering-id 438012d3-4a52-4cc7-b2e3-8dff72e0e706

Untuk detail API, lihat PurchaseReservedDbInstance di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanpurchase-reserved-db-instances-offerings.

AWS CLI

Contoh 1: Untuk menemukan instans DB yang dicadangkan untuk dibeli

describe-reserved-db-instances-offeringsContoh berikut mencantumkan instance MySQL DB cadangan yang tersedia dengan kelas instance db.t2.micro dan durasi satu tahun. ID penawaran diperlukan untuk membeli instans DB yang dicadangkan.


aws rds describe-reserved-db-instances-offerings \
    --product-description mysql \
    --db-instance-class db.t2.micro \
    --duration 1

Output:


{
    "ReservedDBInstancesOfferings": [
        {
            "ReservedDBInstancesOfferingId": "8ba30be1-b9ec-447f-8f23-6114e3f4c7b4",
            "DBInstanceClass": "db.t2.micro",
            "Duration": 31536000,
            "FixedPrice": 51.0,
            "UsagePrice": 0.0,
            "CurrencyCode": "USD",
            "ProductDescription": "mysql",
            "OfferingType": "Partial Upfront",
            "MultiAZ": false,
            "RecurringCharges": [
                {
                    "RecurringChargeAmount": 0.006,
                    "RecurringChargeFrequency": "Hourly"
                }
            ]
        },
    ... some output truncated ...
    ]
}

Untuk informasi selengkapnya, lihat Instans DB Cadangan untuk Amazon RDS di Panduan Pengguna Amazon RDS.

Contoh 2: Untuk membeli instans DB yang dicadangkan

purchase-reserved-db-instances-offeringContoh berikut menunjukkan cara membeli penawaran instans DB yang dicadangkan dari contoh sebelumnya.

aws rds pembelian-cadangan-db-instances-penawaran --reserved-instances-db-instances-offering-id 8ba30be1-b9ec-447f-8f23-6114e3f4c7b4

Output:


{
    "ReservedDBInstance": {
        "ReservedDBInstanceId": "ri-2020-06-29-16-54-57-670",
        "ReservedDBInstancesOfferingId": "8ba30be1-b9ec-447f-8f23-6114e3f4c7b4",
        "DBInstanceClass": "db.t2.micro",
        "StartTime": "2020-06-29T16:54:57.670Z",
        "Duration": 31536000,
        "FixedPrice": 51.0,
        "UsagePrice": 0.0,
        "CurrencyCode": "USD",
        "DBInstanceCount": 1,
        "ProductDescription": "mysql",
        "OfferingType": "Partial Upfront",
        "MultiAZ": false,
        "State": "payment-pending",
        "RecurringCharges": [
            {
                "RecurringChargeAmount": 0.006,
                "RecurringChargeFrequency": "Hourly"
            }
        ],
        "ReservedDBInstanceArn": "arn:aws:rds:us-west-2:123456789012:ri:ri-2020-06-29-16-54-57-670"
    }
}

Untuk informasi selengkapnya, lihat Instans DB Cadangan untuk Amazon RDS di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat PurchaseReservedDbInstancesOfferings di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanreboot-db-instance.

AWS CLI

Untuk me-reboot instance DB

reboot-db-instanceContoh berikut memulai reboot dari instance DB yang ditentukan.


aws rds reboot-db-instance \
    --db-instance-identifier test-mysql-instance

Output:


{
    "DBInstance": {
        "DBInstanceIdentifier": "test-mysql-instance",
        "DBInstanceClass": "db.t3.micro",
        "Engine": "mysql",
        "DBInstanceStatus": "rebooting",
        "MasterUsername": "admin",
        "Endpoint": {
            "Address": "test-mysql-instance.############.us-west-2.rds.amazonaws.com",
            "Port": 3306,
            "HostedZoneId": "Z1PVIF0EXAMPLE"
        },

    ... output omitted...

    }
}

Untuk informasi selengkapnya, lihat Mem-boot ulang Instans DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat RebootDbInstance di AWS CLI Referensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanreboot-db-shard-group.

AWS CLI

Contoh 1: Untuk me-reboot grup pecahan DB

reboot-db-shard-groupContoh berikut me-reboot grup pecahan DB.


aws rds reboot-db-shard-group \
    --db-shard-group-identifier my-db-shard-group

Output:


{
    "DBShardGroups": [
        {
            "DBShardGroupResourceId": "shardgroup-a6e3a0226aa243e2ac6c7a1234567890",
            "DBShardGroupIdentifier": "my-db-shard-group",
            "DBClusterIdentifier": "my-sv2-cluster",
            "MaxACU": 1000.0,
            "ComputeRedundancy": 0,
            "Status": "available",
            "PubliclyAccessible": false,
            "Endpoint": "my-sv2-cluster.limitless-cekycexample.us-east-2.rds.amazonaws.com"
        }
    ]
}

Untuk informasi selengkapnya, lihat Mem-boot ulang cluster Amazon Aurora DB atau instans Amazon Aurora DB di Panduan Pengguna Amazon Aurora.

Contoh 2: Untuk menggambarkan grup pecahan DB Anda

describe-db-shard-groupsContoh berikut mengambil rincian grup pecahan DB Anda setelah Anda menjalankan perintahreboot-db-shard-group. Grup pecahan DB my-db-shard-group sekarang di-reboot.


aws rds describe-db-shard-groups

Output:


{
    "DBShardGroups": [
        {
            "DBShardGroupResourceId": "shardgroup-7bb446329da94788b3f957746example",
            "DBShardGroupIdentifier": "limitless-test-shard-grp",
            "DBClusterIdentifier": "limitless-test-cluster",
            "MaxACU": 768.0,
            "ComputeRedundancy": 0,
            "Status": "available",
            "PubliclyAccessible": true,
            "Endpoint": "limitless-test-cluster.limitless-cekycexample.us-east-2.rds.amazonaws.com"
        },
        {
            "DBShardGroupResourceId": "shardgroup-a6e3a0226aa243e2ac6c7a1234567890",
            "DBShardGroupIdentifier": "my-db-shard-group",
            "DBClusterIdentifier": "my-sv2-cluster",
            "MaxACU": 1000.0,
            "ComputeRedundancy": 0,
            "Status": "rebooting",
            "PubliclyAccessible": false,
            "Endpoint": "my-sv2-cluster.limitless-cekycexample.us-east-2.rds.amazonaws.com"
        }
    ]
}

Untuk informasi selengkapnya, lihat Mem-boot ulang cluster Amazon Aurora DB atau instans Amazon Aurora DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat RebootDbShardGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanregister-db-proxy-targets.

AWS CLI

Untuk mendaftarkan proxy DB dengan database

register-db-proxy-targetsContoh berikut menciptakan hubungan antara database dan proxy.


aws rds register-db-proxy-targets \
    --db-proxy-name proxyExample \
    --db-cluster-identifiers database-5

Output:


{
    "DBProxyTargets": [
        {
            "RdsResourceId": "database-5",
            "Port": 3306,
            "Type": "TRACKED_CLUSTER",
            "TargetHealth": {
                "State": "REGISTERING"
            }
        },
        {
            "Endpoint": "database-5instance-1.ab0cd1efghij.us-east-1.rds.amazonaws.com",
            "RdsResourceId": "database-5",
            "Port": 3306,
            "Type": "RDS_INSTANCE",
            "TargetHealth": {
                "State": "REGISTERING"
            }
        }
    ]
}

Untuk informasi selengkapnya, lihat Membuat proxy RDS di Panduan Pengguna Amazon RDS dan Membuat proxy RDS di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat RegisterDbProxyTargets di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanremove-from-global-cluster.

AWS CLI

Untuk melepaskan cluster sekunder Aurora dari cluster database global Aurora

remove-from-global-clusterContoh berikut melepaskan cluster sekunder Aurora dari cluster database global Aurora. Cluster berubah dari read-only menjadi cluster mandiri dengan kemampuan baca-tulis.


aws rds remove-from-global-cluster \
    --region us-west-2 \
    --global-cluster-identifier myglobalcluster \
    --db-cluster-identifier arn:aws:rds:us-west-2:123456789012:cluster:DB-1

Output:


{
    "GlobalCluster": {
        "GlobalClusterIdentifier": "myglobalcluster",
        "GlobalClusterResourceId": "cluster-abc123def456gh",
        "GlobalClusterArn": "arn:aws:rds::123456789012:global-cluster:myglobalcluster",
        "Status": "available",
        "Engine": "aurora-postgresql",
        "EngineVersion": "10.11",
        "StorageEncrypted": true,
        "DeletionProtection": false,
        "GlobalClusterMembers": [
            {
                "DBClusterArn": "arn:aws:rds:us-east-1:123456789012:cluster:js-global-cluster",
                "Readers": [
                    "arn:aws:rds:us-west-2:123456789012:cluster:DB-1"
                ],
                "IsWriter": true
            },
            {
                "DBClusterArn": "arn:aws:rds:us-west-2:123456789012:cluster:DB-1",
                "Readers": [],
                "IsWriter": false,
                "GlobalWriteForwardingStatus": "disabled"
            }
        ]
    }
}

Untuk informasi selengkapnya, lihat Menghapus cluster dari database global Amazon Aurora di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat RemoveFromGlobalCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanremove-option-from-option-group.

AWS CLI

Untuk menghapus opsi dari grup opsi

remove-option-from-option-groupContoh berikut menghapus OEM opsi darimyoptiongroup.


aws rds remove-option-from-option-group \
    --option-group-name myoptiongroup \
    --options OEM \
    --apply-immediately

Output:


{
    "OptionGroup": {
        "OptionGroupName": "myoptiongroup",
        "OptionGroupDescription": "Test",
        "EngineName": "oracle-ee",
        "MajorEngineVersion": "19",
        "Options": [],
        "AllowsVpcAndNonVpcInstanceMemberships": true,
        "OptionGroupArn": "arn:aws:rds:us-east-1:123456789012:og:myoptiongroup"
    }
}

Untuk informasi selengkapnya, lihat Menghapus Opsi dari Grup Opsi di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat RemoveOptionFromOptionGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanremove-role-from-db-cluster.

AWS CLI

Untuk memisahkan peran AWS Identitas dan Manajemen Akses (IAM) dari cluster DB

remove-role-from-db-clusterContoh berikut menghapus peran dari cluster DB.


aws rds remove-role-from-db-cluster \
    --db-cluster-identifier mydbcluster \
    --role-arn arn:aws:iam::123456789012:role/RDSLoadFromS3

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Mengaitkan peran IAM dengan cluster DB Amazon Aurora MySQL di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat RemoveRoleFromDbCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanremove-role-from-db-instance.

AWS CLI

Untuk memisahkan peran AWS Identitas dan Manajemen Akses (IAM) dari instans DB

remove-role-from-db-instanceContoh berikut menghapus peran bernama rds-s3-integration-role dari instance Oracle DB bernamatest-instance.


aws rds remove-role-from-db-instance \
    --db-instance-identifier test-instance \
    --feature-name S3_INTEGRATION \
    --role-arn arn:aws:iam::111122223333:role/rds-s3-integration-role

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Menonaktifkan Integrasi RDS SQL Server dengan S3 di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat RemoveRoleFromDbInstance di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanremove-source-identifier-from-subscription.

AWS CLI

Untuk menghapus pengidentifikasi sumber dari langganan

remove-source-identifierContoh berikut menghapus pengidentifikasi sumber yang ditentukan dari langganan yang ada.


aws rds remove-source-identifier-from-subscription \
    --subscription-name my-instance-events \
    --source-identifier test-instance-repl

Output:


{
    "EventSubscription": {
        "EventSubscriptionArn": "arn:aws:rds:us-east-1:123456789012:es:my-instance-events",
        "SubscriptionCreationTime": "Tue Jul 31 23:22:01 UTC 2018",
        "EventCategoriesList": [
            "backup",
            "recovery"
        ],
        "SnsTopicArn": "arn:aws:sns:us-east-1:123456789012:interesting-events",
        "Status": "modifying",
        "CustSubscriptionId": "my-instance-events",
        "CustomerAwsId": "123456789012",
        "SourceIdsList": [
            "test-instance"
        ],
        "SourceType": "db-instance",
        "Enabled": false
    }
}

Untuk detail API, lihat RemoveSourceIdentifierFromSubscription di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanremove-tags-from-resource.

AWS CLI

Untuk menghapus tag dari sumber daya

remove-tags-from-resourceContoh berikut menghapus tag dari sumber daya.


aws rds remove-tags-from-resource \
    --resource-name arn:aws:rds:us-east-1:123456789012:db:mydbinstance \
    --tag-keys Name Environment

Perintah ini tidak menghasilkan output.

Untuk informasi selengkapnya, lihat Menandai sumber daya Amazon RDS di Panduan Pengguna Amazon RDS dan Men andai sumber daya Amazon RDS di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat RemoveTagsFromResource di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanreset-db-cluster-parameter-group.

AWS CLI

Contoh 1: Untuk mengatur ulang semua parameter ke nilai defaultnya

reset-db-cluster-parameter-groupContoh berikut mengatur ulang semua nilai parameter dalam grup parameter cluster DB yang dibuat pelanggan ke nilai defaultnya.


aws rds reset-db-cluster-parameter-group \
    --db-cluster-parameter-group-name mydbclpg \
    --reset-all-parameters

Output:


{
    "DBClusterParameterGroupName": "mydbclpg"
}

Untuk informasi selengkapnya, lihat Bek erja dengan grup parameter DB dan grup parameter cluster DB di Panduan Pengguna Amazon Aurora.

Contoh 2: Untuk mengatur ulang parameter tertentu ke nilai defaultnya

reset-db-cluster-parameter-groupContoh berikut mengatur ulang nilai parameter untuk parameter tertentu ke nilai defaultnya dalam grup parameter cluster DB yang dibuat pelanggan.


aws rds reset-db-cluster-parameter-group \
    --db-cluster-parameter-group-name mydbclpgy \
    --parameters "ParameterName=max_connections,ApplyMethod=immediate" \
                 "ParameterName=max_allowed_packet,ApplyMethod=immediate"

Output:


{
    "DBClusterParameterGroupName": "mydbclpg"
}

Untuk informasi selengkapnya, lihat Bek erja dengan grup parameter DB dan grup parameter cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat ResetDbClusterParameterGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanreset-db-parameter-group.

AWS CLI

Contoh 1: Untuk mengatur ulang semua parameter ke nilai defaultnya

reset-db-parameter-groupContoh berikut mengatur ulang semua nilai parameter dalam grup parameter DB yang dibuat pelanggan ke nilai defaultnya.


aws rds reset-db-parameter-group \
    --db-parameter-group-name mypg \
    --reset-all-parameters

Output:


{
    "DBParameterGroupName": "mypg"
}

Untuk informasi selengkapnya, lihat Bek erja dengan grup parameter DB di Panduan Pengguna Amazon RDS dan Bekerja dengan grup parameter DB dan grup parameter cluster DB di Panduan Pengguna Amazon Aurora.

Contoh 2: Untuk mengatur ulang parameter tertentu ke nilai defaultnya

reset-db-parameter-groupContoh berikut mengatur ulang nilai parameter untuk parameter tertentu ke nilai defaultnya dalam grup parameter DB yang dibuat pelanggan.


aws rds reset-db-parameter-group \
    --db-parameter-group-name mypg \
    --parameters "ParameterName=max_connections,ApplyMethod=immediate" \
                 "ParameterName=max_allowed_packet,ApplyMethod=immediate"

Output:


{
    "DBParameterGroupName": "mypg"
}

Untuk detail API, lihat ResetDbParameterGroup di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanrestore-db-cluster-from-s3.

AWS CLI

Untuk memulihkan cluster Amazon Aurora DB dari Amazon S3

restore-db-cluster-from-s3Contoh berikut mengembalikan cluster DB yang kompatibel dengan Amazon Aurora MySQL versi 5.7 dari file cadangan MySQL 5.7 DB di Amazon S3.


aws rds restore-db-cluster-from-s3 \
    --db-cluster-identifier cluster-s3-restore \
    --engine aurora-mysql \
    --master-username admin \
    --master-user-password mypassword \
    --s3-bucket-name amzn-s3-demo-bucket \
    --s3-prefix test-backup \
    --s3-ingestion-role-arn arn:aws:iam::123456789012:role/service-role/TestBackup \
    --source-engine mysql \
    --source-engine-version 5.7.28

Output:


{
    "DBCluster": {
        "AllocatedStorage": 1,
        "AvailabilityZones": [
            "us-west-2c",
            "us-west-2a",
            "us-west-2b"
        ],
        "BackupRetentionPeriod": 1,
        "DBClusterIdentifier": "cluster-s3-restore",
        "DBClusterParameterGroup": "default.aurora-mysql5.7",
        "DBSubnetGroup": "default",
        "Status": "creating",
        "Endpoint": "cluster-s3-restore.cluster-co3xyzabc123.us-west-2.rds.amazonaws.com",
        "ReaderEndpoint": "cluster-s3-restore.cluster-ro-co3xyzabc123.us-west-2.rds.amazonaws.com",
        "MultiAZ": false,
        "Engine": "aurora-mysql",
        "EngineVersion": "5.7.12",
        "Port": 3306,
        "MasterUsername": "admin",
        "PreferredBackupWindow": "11:15-11:45",
        "PreferredMaintenanceWindow": "thu:12:19-thu:12:49",
        "ReadReplicaIdentifiers": [],
        "DBClusterMembers": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sg-########",
                "Status": "active"
            }
        ],
        "HostedZoneId": "Z1PVIF0EXAMPLE",
        "StorageEncrypted": false,
        "DbClusterResourceId": "cluster-SU5THYQQHOWCXZZDGXREXAMPLE",
        "DBClusterArn": "arn:aws:rds:us-west-2:123456789012:cluster:cluster-s3-restore",
        "AssociatedRoles": [],
        "IAMDatabaseAuthenticationEnabled": false,
        "ClusterCreateTime": "2020-07-27T14:22:08.095Z",
        "EngineMode": "provisioned",
        "DeletionProtection": false,
        "HttpEndpointEnabled": false,
        "CopyTagsToSnapshot": false,
        "CrossAccountClone": false,
        "DomainMemberships": []
    }
}

Untuk informasi selengkapnya, lihat Migrasi Data dari MySQL dengan Menggunakan Bucket Amazon S3 di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat RestoreDbClusterFromS3 di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanrestore-db-cluster-from-snapshot.

AWS CLI

Untuk memulihkan cluster DB dari snapshot

Berikut ini restore-db-cluster-from-snapshot mengembalikan cluster DB Aurora PostgreSQL yang kompatibel dengan PostgreSQL versi 10.7 dari snapshot cluster DB bernama. test-instance-snapshot


aws rds restore-db-cluster-from-snapshot \
    --db-cluster-identifier newdbcluster \
    --snapshot-identifier test-instance-snapshot \
    --engine aurora-postgresql \
    --engine-version 10.7

Output:


{
    "DBCluster": {
        "AllocatedStorage": 1,
        "AvailabilityZones": [
            "us-west-2c",
            "us-west-2a",
            "us-west-2b"
        ],
        "BackupRetentionPeriod": 7,
        "DatabaseName": "",
        "DBClusterIdentifier": "newdbcluster",
        "DBClusterParameterGroup": "default.aurora-postgresql10",
        "DBSubnetGroup": "default",
        "Status": "creating",
        "Endpoint": "newdbcluster.cluster-############.us-west-2.rds.amazonaws.com",
        "ReaderEndpoint": "newdbcluster.cluster-ro-############.us-west-2.rds.amazonaws.com",
        "MultiAZ": false,
        "Engine": "aurora-postgresql",
        "EngineVersion": "10.7",
        "Port": 5432,
        "MasterUsername": "postgres",
        "PreferredBackupWindow": "09:33-10:03",
        "PreferredMaintenanceWindow": "sun:12:22-sun:12:52",
        "ReadReplicaIdentifiers": [],
        "DBClusterMembers": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sg-########",
                "Status": "active"
            }
        ],
        "HostedZoneId": "Z1PVIF0EXAMPLE",
        "StorageEncrypted": true,
        "KmsKeyId": "arn:aws:kms:us-west-2:123456789012:key/287364e4-33e3-4755-a3b0-a1b2c3d4e5f6",
        "DbClusterResourceId": "cluster-5DSB5IFQDDUVAWOUWM1EXAMPLE",
        "DBClusterArn": "arn:aws:rds:us-west-2:123456789012:cluster:newdbcluster",
        "AssociatedRoles": [],
        "IAMDatabaseAuthenticationEnabled": false,
        "ClusterCreateTime": "2020-06-05T15:06:58.634Z",
        "EngineMode": "provisioned",
        "DeletionProtection": false,
        "HttpEndpointEnabled": false,
        "CopyTagsToSnapshot": false,
        "CrossAccountClone": false,
        "DomainMemberships": []
    }
}

Untuk informasi selengkapnya, lihat Memulihkan dari Snapshot Cluster DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat RestoreDbClusterFromSnapshot di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanrestore-db-cluster-to-point-in-time.

AWS CLI

Untuk mengembalikan cluster DB ke waktu yang ditentukan

restore-db-cluster-to-point-in-timeContoh berikut mengembalikan cluster DB bernama database-4 ke waktu terakhir yang mungkin. Menggunakan copy-on-write sebagai tipe pemulihan mengembalikan cluster DB baru sebagai klon dari cluster DB sumber.


aws rds restore-db-cluster-to-point-in-time \
    --source-db-cluster-identifier database-4 \
    --db-cluster-identifier sample-cluster-clone \
    --restore-type copy-on-write \
    --use-latest-restorable-time

Output:


{
    "DBCluster": {
        "AllocatedStorage": 1,
        "AvailabilityZones": [
            "us-west-2c",
            "us-west-2a",
            "us-west-2b"
        ],
        "BackupRetentionPeriod": 7,
        "DatabaseName": "",
        "DBClusterIdentifier": "sample-cluster-clone",
        "DBClusterParameterGroup": "default.aurora-postgresql10",
        "DBSubnetGroup": "default",
        "Status": "creating",
        "Endpoint": "sample-cluster-clone.cluster-############.us-west-2.rds.amazonaws.com",
        "ReaderEndpoint": "sample-cluster-clone.cluster-ro-############.us-west-2.rds.amazonaws.com",
        "MultiAZ": false,
        "Engine": "aurora-postgresql",
        "EngineVersion": "10.7",
        "Port": 5432,
        "MasterUsername": "postgres",
        "PreferredBackupWindow": "09:33-10:03",
        "PreferredMaintenanceWindow": "sun:12:22-sun:12:52",
        "ReadReplicaIdentifiers": [],
        "DBClusterMembers": [],
        "VpcSecurityGroups": [
            {
                "VpcSecurityGroupId": "sg-########",
                "Status": "active"
            }
        ],
        "HostedZoneId": "Z1PVIF0EXAMPLE",
        "StorageEncrypted": true,
        "KmsKeyId": "arn:aws:kms:us-west-2:123456789012:key/287364e4-33e3-4755-a3b0-a1b2c3d4e5f6",
        "DbClusterResourceId": "cluster-BIZ77GDSA2XBSTNPFW1EXAMPLE",
        "DBClusterArn": "arn:aws:rds:us-west-2:123456789012:cluster:sample-cluster-clone",
        "AssociatedRoles": [],
        "IAMDatabaseAuthenticationEnabled": false,
        "CloneGroupId": "8d19331a-099a-45a4-b4aa-11aa22bb33cc44dd",
        "ClusterCreateTime": "2020-03-10T19:57:38.967Z",
        "EngineMode": "provisioned",
        "DeletionProtection": false,
        "HttpEndpointEnabled": false,
        "CopyTagsToSnapshot": false,
        "CrossAccountClone": false
    }
}

Untuk informasi selengkapnya, lihat Memulihkan Cluster DB ke Waktu yang Ditentukan di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat RestoreDbClusterToPointInTime di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanrestore-db-instance-from-db-snapshot.

AWS CLI

Untuk memulihkan instance DB dari snapshot DB

restore-db-instance-from-db-snapshotContoh berikut membuat instance DB baru bernama db7-new-instance dengan kelas instance db.t3.small DB dari snapshot DB yang ditentukan. Instans DB sumber tempat snapshot diambil menggunakan kelas instance DB yang tidak digunakan lagi, jadi Anda tidak dapat memutakhirkannya.


aws rds restore-db-instance-from-db-snapshot \
    --db-instance-identifier db7-new-instance \
    --db-snapshot-identifier db7-test-snapshot \
    --db-instance-class db.t3.small

Output:


{
    "DBInstance": {
        "DBInstanceIdentifier": "db7-new-instance",
        "DBInstanceClass": "db.t3.small",
        "Engine": "mysql",
        "DBInstanceStatus": "creating",

        ...output omitted...

        "PreferredMaintenanceWindow": "mon:07:37-mon:08:07",
        "PendingModifiedValues": {},
        "MultiAZ": false,
        "EngineVersion": "5.7.22",
        "AutoMinorVersionUpgrade": true,
        "ReadReplicaDBInstanceIdentifiers": [],
        "LicenseModel": "general-public-license",

        ...output omitted...

        "DBInstanceArn": "arn:aws:rds:us-west-2:123456789012:db:db7-new-instance",
        "IAMDatabaseAuthenticationEnabled": false,
        "PerformanceInsightsEnabled": false,
        "DeletionProtection": false,
        "AssociatedRoles": []
    }
}

Untuk informasi selengkapnya, lihat Memulihkan dari Snapshot DB di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat RestoreDbInstanceFromDbSnapshot di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanrestore-db-instance-from-s3.

AWS CLI

Untuk memulihkan instans DB dari cadangan di Amazon S3

restore-db-instance-from-s3Contoh berikut membuat instance DB baru bernama restored-test-instance dari cadangan yang ada di bucket my-backups S3.


aws rds restore-db-instance-from-s3 \
    --db-instance-identifier restored-test-instance \
    --allocated-storage 250 --db-instance-class db.m4.large --engine mysql \
    --master-username master --master-user-password secret99 \
    --s3-bucket-name my-backups --s3-ingestion-role-arn arn:aws:iam::123456789012:role/my-role \
    --source-engine mysql --source-engine-version 5.6.27

Untuk detail API, lihat RestoreDbInstanceFromS3 di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanrestore-db-instance-to-point-in-time.

AWS CLI

Contoh 1: Untuk mengembalikan instance DB ke titik waktu

restore-db-instance-to-point-in-timeContoh berikut mengembalikan test-instance ke instance DB baru bernamarestored-test-instance, pada waktu yang ditentukan.


aws rds restore-db-instance-to-point-in-time \
    --source-db-instance-identifier test-instance \
    --target-db-instance restored-test-instance \
    --restore-time 2018-07-30T23:45:00.000Z

Output:


{
    "DBInstance": {
        "AllocatedStorage": 20,
        "DBInstanceArn": "arn:aws:rds:us-east-1:123456789012:db:restored-test-instance",
        "DBInstanceStatus": "creating",
        "DBInstanceIdentifier": "restored-test-instance",
        ...some output omitted...
    }
}

Untuk informasi selengkapnya, lihat Memulihkan instance DB ke waktu tertentu di Panduan Pengguna Amazon RDS.

Contoh 2: Untuk mengembalikan instance DB ke waktu tertentu dari cadangan yang direplikasi

restore-db-instance-to-point-in-timeContoh berikut mengembalikan instance Oracle DB ke waktu yang ditentukan dari cadangan otomatis yang direplikasi.


aws rds restore-db-instance-to-point-in-time \
    --source-db-instance-automated-backups-arn "arn:aws:rds:us-west-2:123456789012:auto-backup:ab-jkib2gfq5rv7replzadausbrktni2bn4example" \
    --target-db-instance-identifier myorclinstance-from-replicated-backup \
    --restore-time 2020-12-08T18:45:00.000Z

Output:


{
    "DBInstance": {
        "DBInstanceIdentifier": "myorclinstance-from-replicated-backup",
        "DBInstanceClass": "db.t3.micro",
        "Engine": "oracle-se2",
        "DBInstanceStatus": "creating",
        "MasterUsername": "admin",
        "DBName": "ORCL",
        "AllocatedStorage": 20,
        "PreferredBackupWindow": "07:45-08:15",
        "BackupRetentionPeriod": 14,
        ... some output omitted ...
        "DbiResourceId": "db-KGLXG75BGVIWKQT7NQ4EXAMPLE",
        "CACertificateIdentifier": "rds-ca-2019",
        "DomainMemberships": [],
        "CopyTagsToSnapshot": false,
        "MonitoringInterval": 0,
        "DBInstanceArn": "arn:aws:rds:us-west-2:123456789012:db:myorclinstance-from-replicated-backup",
        "IAMDatabaseAuthenticationEnabled": false,
        "PerformanceInsightsEnabled": false,
        "DeletionProtection": false,
        "AssociatedRoles": [],
        "TagList": []
    }
}

Untuk informasi selengkapnya, lihat Memulihkan ke waktu tertentu dari cadangan yang direplikasi di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat RestoreDbInstanceToPointInTime di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanstart-activity-stream.

AWS CLI

Untuk memulai aliran aktivitas database

start-activity-streamContoh berikut memulai aliran aktivitas asinkron untuk memantau cluster Aurora bernama my-pg-cluster.


aws rds start-activity-stream \
    --region us-east-1 \
    --mode async \
    --kms-key-id arn:aws:kms:us-east-1:1234567890123:key/a12c345d-6ef7-890g-h123-456i789jk0l1 \
    --resource-arn arn:aws:rds:us-east-1:1234567890123:cluster:my-pg-cluster \
    --apply-immediately

Output:


{
    "KmsKeyId": "arn:aws:kms:us-east-1:1234567890123:key/a12c345d-6ef7-890g-h123-456i789jk0l1",
    "KinesisStreamName": "aws-rds-das-cluster-0ABCDEFGHI1JKLM2NOPQ3R4S",
    "Status": "starting",
    "Mode": "async",
    "ApplyImmediately": true
}

Untuk informasi selengkapnya, lihat Mem ulai aliran aktivitas database di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat StartActivityStream di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanstart-db-cluster.

AWS CLI

Untuk memulai cluster DB

start-db-clusterContoh berikut memulai cluster DB dan instance DB-nya.


aws rds start-db-cluster \
    --db-cluster-identifier mydbcluster

Output:


{
    "DBCluster": {
        "AllocatedStorage": 1,
        "AvailabilityZones": [
            "us-east-1a",
            "us-east-1e",
            "us-east-1b"
        ],
        "BackupRetentionPeriod": 1,
        "DatabaseName": "mydb",
        "DBClusterIdentifier": "mydbcluster",
        ...some output truncated...
    }
}

Untuk informasi selengkapnya, lihat Menghentikan dan memulai cluster Amazon Aurora DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat StartDbCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanstart-db-instance-automated-backups-replication.

AWS CLI

Untuk mengaktifkan pencadangan otomatis lintas wilayah

start-db-instance-automated-backups-replicationContoh berikut mereplikasi pencadangan otomatis dari instance DB di Wilayah AS Timur (Virginia Utara) ke AS Barat (Oregon). Periode retensi cadangan adalah 14 hari.


aws rds start-db-instance-automated-backups-replication \
    --region us-west-2 \
    --source-db-instance-arn "arn:aws:rds:us-east-1:123456789012:db:new-orcl-db" \
    --backup-retention-period 14

Output:


{
    "DBInstanceAutomatedBackup": {
        "DBInstanceArn": "arn:aws:rds:us-east-1:123456789012:db:new-orcl-db",
        "DbiResourceId": "db-JKIB2GFQ5RV7REPLZA4EXAMPLE",
        "Region": "us-east-1",
        "DBInstanceIdentifier": "new-orcl-db",
        "RestoreWindow": {},
        "AllocatedStorage": 20,
        "Status": "pending",
        "Port": 1521,
        "InstanceCreateTime": "2020-12-04T15:28:31Z",
        "MasterUsername": "admin",
        "Engine": "oracle-se2",
        "EngineVersion": "12.1.0.2.v21",
        "LicenseModel": "bring-your-own-license",
        "OptionGroupName": "default:oracle-se2-12-1",
        "Encrypted": false,
        "StorageType": "gp2",
        "IAMDatabaseAuthenticationEnabled": false,
        "BackupRetentionPeriod": 14,
        "DBInstanceAutomatedBackupsArn": "arn:aws:rds:us-west-2:123456789012:auto-backup:ab-jkib2gfq5rv7replzadausbrktni2bn4example"
    }
}

Untuk informasi selengkapnya, lihat Mengaktifkan pencadangan otomatis lintas wilayah di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat StartDbInstanceAutomatedBackupsReplication di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanstart-db-instance.

AWS CLI

Untuk memulai instance DB

start-db-instanceContoh berikut memulai instance DB yang ditentukan.


aws rds start-db-instance \
    --db-instance-identifier test-instance

Output:


{
    "DBInstance": {
        "DBInstanceStatus": "starting",
        ...some output truncated...
    }
}

Untuk detail API, lihat StartDbInstance di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanstart-export-task.

AWS CLI

Untuk mengekspor snapshot ke Amazon S3

start-export-taskContoh berikut mengekspor snapshot DB bernama db5-snapshot-test ke bucket Amazon S3 bernamaamzn-s3-demo-bucket.


aws rds start-export-task \
    --export-task-identifier my-s3-export \
    --source-arn arn:aws:rds:us-west-2:123456789012:snapshot:db5-snapshot-test \
    --s3-bucket-name amzn-s3-demo-bucket \
    --iam-role-arn arn:aws:iam::123456789012:role/service-role/ExportRole \
    --kms-key-id arn:aws:kms:us-west-2:123456789012:key/abcd0000-7fca-4128-82f2-aabbccddeeff

Output:


{
    "ExportTaskIdentifier": "my-s3-export",
    "SourceArn": "arn:aws:rds:us-west-2:123456789012:snapshot:db5-snapshot-test",
    "SnapshotTime": "2020-03-27T20:48:42.023Z",
    "S3Bucket": "amzn-s3-demo-bucket",
    "IamRoleArn": "arn:aws:iam::123456789012:role/service-role/ExportRole",
    "KmsKeyId": "arn:aws:kms:us-west-2:123456789012:key/abcd0000-7fca-4128-82f2-aabbccddeeff",
    "Status": "STARTING",
    "PercentProgress": 0,
    "TotalExtractedDataInGB": 0
}

Untuk informasi selengkapnya, lihat Meng ekspor Snapshot ke Bucket Amazon S3 di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat StartExportTask di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanstop-activity-stream.

AWS CLI

Untuk menghentikan aliran aktivitas database

stop-activity-streamContoh berikut menghentikan aliran aktivitas di cluster Aurora bernama my-pg-cluster.


aws rds stop-activity-stream \
    --region us-east-1 \
    --resource-arn arn:aws:rds:us-east-1:1234567890123:cluster:my-pg-cluster \
    --apply-immediately

Output:


{
    "KmsKeyId": "arn:aws:kms:us-east-1:1234567890123:key/a12c345d-6ef7-890g-h123-456i789jk0l1",
    "KinesisStreamName": "aws-rds-das-cluster-0ABCDEFGHI1JKLM2NOPQ3R4S",
    "Status": "stopping"
}

Untuk informasi selengkapnya, lihat Menghentikan aliran aktivitas di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat StopActivityStream di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanstop-db-cluster.

AWS CLI

Untuk menghentikan cluster DB

stop-db-clusterContoh berikut menghentikan cluster DB dan instance DB-nya.


aws rds stop-db-cluster \
    --db-cluster-identifier mydbcluster

Output:


{
    "DBCluster": {
        "AllocatedStorage": 1,
        "AvailabilityZones": [
            "us-east-1a",
            "us-east-1e",
            "us-east-1b"
        ],
        "BackupRetentionPeriod": 1,
        "DatabaseName": "mydb",
        "DBClusterIdentifier": "mydbcluster",
        ...some output truncated...
    }
}

Untuk informasi selengkapnya, lihat Menghentikan dan memulai cluster Amazon Aurora DB di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat StopDbCluster di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanstop-db-instance-automated-backups-replication.

AWS CLI

Untuk berhenti mereplikasi pencadangan otomatis

Berikut ini stop-db-instance-automated-backups-replication mengakhiri replikasi cadangan otomatis ke Wilayah AS Barat (Oregon). Cadangan yang direplikasi dipertahankan sesuai dengan periode retensi cadangan yang ditetapkan.


aws rds stop-db-instance-automated-backups-replication \
    --region us-west-2 \
    --source-db-instance-arn "arn:aws:rds:us-east-1:123456789012:db:new-orcl-db"

Output:


{
    "DBInstanceAutomatedBackup": {
        "DBInstanceArn": "arn:aws:rds:us-east-1:123456789012:db:new-orcl-db",
        "DbiResourceId": "db-JKIB2GFQ5RV7REPLZA4EXAMPLE",
        "Region": "us-east-1",
        "DBInstanceIdentifier": "new-orcl-db",
        "RestoreWindow": {
            "EarliestTime": "2020-12-04T23:13:21.030Z",
            "LatestTime": "2020-12-07T19:59:57Z"
        },
        "AllocatedStorage": 20,
        "Status": "replicating",
        "Port": 1521,
        "InstanceCreateTime": "2020-12-04T15:28:31Z",
        "MasterUsername": "admin",
        "Engine": "oracle-se2",
        "EngineVersion": "12.1.0.2.v21",
        "LicenseModel": "bring-your-own-license",
        "OptionGroupName": "default:oracle-se2-12-1",
        "Encrypted": false,
        "StorageType": "gp2",
        "IAMDatabaseAuthenticationEnabled": false,
        "BackupRetentionPeriod": 7,
        "DBInstanceAutomatedBackupsArn": "arn:aws:rds:us-west-2:123456789012:auto-backup:ab-jkib2gfq5rv7replzadausbrktni2bn4example"
    }
}

Untuk informasi selengkapnya, lihat Menghentikan replikasi cadangan otomatis di Panduan Pengguna Amazon RDS.

Untuk detail API, lihat StopDbInstanceAutomatedBackupsReplication di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanstop-db-instance.

AWS CLI

Untuk menghentikan instans DB

stop-db-instanceContoh berikut menghentikan instance DB yang ditentukan.


aws rds stop-db-instance \
    --db-instance-identifier test-instance

Output:


{
    "DBInstance": {
        "DBInstanceStatus": "stopping",
        ...some output truncated...
    }
}

Untuk detail API, lihat StopDbInstance di Refer AWS CLI ensi Perintah.

Contoh kode berikut menunjukkan cara menggunakanswitchover-blue-green-deployment.

AWS CLI

Contoh 1: Untuk mengalihkan blue/green penerapan untuk instans DB RDS

switchover-blue-green-deploymentContoh berikut mempromosikan lingkungan hijau yang ditentukan sebagai lingkungan produksi baru.


aws rds switchover-blue-green-deployment \
    --blue-green-deployment-identifier bgd-wi89nwzglccsfake \
    --switchover-timeout 300

Output:


{
    "BlueGreenDeployment": {
        "BlueGreenDeploymentIdentifier": "bgd-v53303651eexfake",
        "BlueGreenDeploymentName": "bgd-cli-test-instance",
        "Source": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance",
        "Target": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-green-blhi1e",
        "SwitchoverDetails": [
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-green-blhi1e",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-1",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-1-green-k5fv7u",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-2",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-2-green-ggsh8m",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-3",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance-replica-3-green-o2vwm0",
                "Status": "AVAILABLE"
            }
        ],
        "Tasks": [
            {
                "Name": "CREATING_READ_REPLICA_OF_SOURCE",
                "Status": "COMPLETED"
            },
            {
                "Name": "DB_ENGINE_VERSION_UPGRADE",
                "Status": "COMPLETED"
            },
            {
                "Name": "CONFIGURE_BACKUPS",
                "Status": "COMPLETED"
            },
            {
                "Name": "CREATING_TOPOLOGY_OF_SOURCE",
                "Status": "COMPLETED"
            }
        ],
        "Status": "SWITCHOVER_IN_PROGRESS",
        "CreateTime": "2022-02-25T22:33:22.225000+00:00"
    }
}

Untuk informasi selengkapnya, lihat Mengal blue/green ihkan pener apan di Panduan Pengguna Amazon RDS.

Contoh 2: Untuk mempromosikan blue/green penerapan untuk cluster Aurora MySQL DB

switchover-blue-green-deploymentContoh berikut mempromosikan lingkungan hijau yang ditentukan sebagai lingkungan produksi baru.


aws rds switchover-blue-green-deployment \
    --blue-green-deployment-identifier bgd-wi89nwzglccsfake \
    --switchover-timeout 300

Output:


{
    "BlueGreenDeployment": {
        "BlueGreenDeploymentIdentifier": "bgd-wi89nwzglccsfake",
        "BlueGreenDeploymentName": "my-blue-green-deployment",
        "Source": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
        "Target": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster-green-3ud8z6",
        "SwitchoverDetails": [
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster-green-3ud8z6",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-1",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-1-green-bvxc73",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-2",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-2-green-7wc4ie",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-3",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:db:my-aurora-mysql-cluster-3-green-p4xxkz",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-excluded-member-endpoint",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-excluded-member-endpoint-green-np1ikl",
                "Status": "AVAILABLE"
            },
            {
                "SourceMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-reader-endpoint",
                "TargetMember": "arn:aws:rds:us-east-1:123456789012:cluster-endpoint:my-reader-endpoint-green-miszlf",
                "Status": "AVAILABLE"
            }
        ],
        "Tasks": [
            {
                "Name": "CREATING_READ_REPLICA_OF_SOURCE",
                "Status": "COMPLETED"
            },
            {
                "Name": "DB_ENGINE_VERSION_UPGRADE",
                "Status": "COMPLETED"
            },
            {
                "Name": "CREATE_DB_INSTANCES_FOR_CLUSTER",
                "Status": "COMPLETED"
            },
            {
                "Name": "CREATE_CUSTOM_ENDPOINTS",
                "Status": "COMPLETED"
            }
        ],
        "Status": "SWITCHOVER_IN_PROGRESS",
        "CreateTime": "2022-02-25T22:38:49.522000+00:00"
    }
}

Untuk informasi selengkapnya, lihat Mengal blue/green ihkan penerapan di Panduan Pengguna Amazon Aurora.

Untuk detail API, lihat SwitchoverBlueGreenDeployment di Refer AWS CLI ensi Perintah.

Awas Javascript dinonaktifkan atau tidak tersedia di browser Anda.

Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk.

Konvensi Dokumen

AWS Proton

Layanan Data Amazon RDS