本文档仅适用于 AWS CLI 版本 1。有关 AWS CLI 版本 2 的相关文档,请参阅版本 2 用户指南。
使用AWS CLI的 Amazon RDS 示例
以下代码示例展示了如何通过将 AWS Command Line Interface与 Amazon RDS 结合使用,来执行操作和实现常见场景。
操作是大型程序的代码摘录,必须在上下文中运行。您可以通过操作了解如何调用单个服务函数,还可以通过函数相关场景的上下文查看操作。
每个示例都包含一个指向完整源代码的链接,您可以从中找到有关如何在上下文中设置和运行代码的说明。
主题
操作
以下代码示例演示了如何使用 add-option-to-option-group
。
- AWS CLI
-
向选项组添加选项
以下
add-option-to-option-group
示例向选项组添加了选项。aws rds add-option-to-option-group \ --option-group-name
myoptiongroup
\ --optionsOptionName=OEM,Port=5500,DBSecurityGroupMemberships=default
\ --apply-immediately输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的向选项组添加选项。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 AddOptionToOptionGroup
。
-
以下代码示例演示了如何使用 add-role-to-db-cluster
。
- AWS CLI
-
将 AWS Identity and Access Management(IAM)角色与数据库集群相关联
以下
add-role-to-db-cluster
示例将角色与数据库集群相关联。aws rds add-role-to-db-cluster \ --db-cluster-identifier
mydbcluster
\ --role-arnarn:aws:iam::123456789012:role/RDSLoadFromS3
此命令不生成任何输出。
有关更多信息,请参阅《Amazon Aurora 用户指南》中的将 IAM 角色与 Amazon Aurora MySQL 数据库集群相关联。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 AddRoleToDbCluster
。
-
以下代码示例演示了如何使用 add-role-to-db-instance
。
- AWS CLI
-
将 AWS Identity and Access Management(IAM)角色与数据库实例相关联
以下
add-role-to-db-instance
示例向名为test-instance
的 Oracle 数据库实例添加了角色。aws rds add-role-to-db-instance \ --db-instance-identifier
test-instance
\ --feature-nameS3_INTEGRATION
\ --role-arnarn:aws:iam::111122223333:role/rds-s3-integration-role
此命令不生成任何输出。
有关更多信息,请参阅《Amazon RDS 用户指南》中的 Amazon RDS Oracle 与 Amazon S3 集成的先决条件。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 AddRoleToDbInstance
。
-
以下代码示例演示了如何使用 add-source-identifier-to-subscription
。
- AWS CLI
-
向订阅添加源标识符
以下
add-source-identifier
示例向现有订阅添加了另一个源标识符。aws rds add-source-identifier-to-subscription \ --subscription-name
my-instance-events
\ --source-identifiertest-instance-repl
输出:
{ "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" ] } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 AddSourceIdentifierToSubscription
。
-
以下代码示例演示了如何使用 add-tags-to-resource
。
- AWS CLI
-
为资源添加标签
以下
add-tags-to-resource
示例向 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\"}]"此命令不生成任何输出。
有关更多信息,请参阅《Amazon RDS 用户指南》中的为 Amazon RDS 资源添加标签。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 AddTagsToResource
。
-
以下代码示例演示了如何使用 apply-pending-maintenance-action
。
- AWS CLI
-
应用待执行的维护操作
以下
apply-pending-maintenance-action
示例应用数据库集群的待处理维护操作。aws rds apply-pending-maintenance-action \ --resource-identifier
arn:aws:rds:us-east-1:123456789012:cluster:my-db-cluster
\ --apply-actionsystem-update
\ --opt-in-typeimmediate
输出:
{ "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" } ] } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的维护数据库实例和《Amazon Aurora 用户指南》中的维护 Amazon Aurora 数据库集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ApplyPendingMaintenanceAction
。
-
以下代码示例演示了如何使用 authorize-db-security-group-ingress
。
- AWS CLI
-
将 AWS Identity and Access Management(IAM)角色与数据库实例相关联
以下
authorize-db-security-group-ingress
示例使用 CIDR IP 范围 192.0.2.0/24 的入口规则配置默认安全组。aws rds authorize-db-security-group-ingress \ --db-security-group-name
default
\ --cidrip192.0.2.0/24
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的从 IP 范围向数据库安全组授予网络访问权限。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 AuthorizeDbSecurityGroupIngress
。
-
以下代码示例演示了如何使用 backtrack-db-cluster
。
- AWS CLI
-
回溯 Aurora 数据库集群
以下
backtrack-db-cluster
示例将指定的数据库集群 sample-cluster 回溯到 2018 年 3 月 19 日上午 10 点。aws rds backtrack-db-cluster --db-cluster-identifier
sample-cluster
--backtrack-to2018-03-19T10:00:00+00:00
此命令输出一个 JSON 块,用于确认对 RDS 资源的更改。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 BacktrackDbCluster
。
-
以下代码示例演示了如何使用 cancel-export-task
。
- AWS CLI
-
取消将快照导出到 Amazon S3
以下
cancel-export-task
示例取消了正在进行的将快照导出到 Amazon S3 的导出任务。aws rds cancel-export-task \ --export-task-identifier
my-s3-export-1
输出:
{ "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": "mybucket", "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 }
有关更多信息,请参阅《Amazon RDS 用户指南》中的取消快照导出任务或《Amazon Aurora 用户指南》中的取消快照导出任务。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CancelExportTask
。
-
以下代码示例演示了如何使用 copy-db-cluster-parameter-group
。
- AWS CLI
-
复制数据库集群参数组
以下
copy-db-cluster-parameter-group
示例复制了数据库集群参数组。aws rds copy-db-cluster-parameter-group \ --source-db-cluster-parameter-group-identifier
mydbclusterpg
\ --target-db-cluster-parameter-group-identifiermydbclusterpgcopy
\ --target-db-cluster-parameter-group-description"Copy of mydbclusterpg parameter group"
输出:
{ "DBClusterParameterGroup": { "DBClusterParameterGroupName": "mydbclusterpgcopy", "DBClusterParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:cluster-pg:mydbclusterpgcopy", "DBParameterGroupFamily": "aurora-mysql5.7", "Description": "Copy of mydbclusterpg parameter group" } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的复制数据库集群参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CopyDbClusterParameterGroup
。
-
以下代码示例演示了如何使用 copy-db-cluster-snapshot
。
- AWS CLI
-
复制数据库集群快照
以下
copy-db-cluster-snapshot
示例创建数据库集群快照的副本,包括其标签。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-identifiermyclustersnapshotcopy
\ --copy-tags输出:
{ "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 } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的复制快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CopyDbClusterSnapshot
。
-
以下代码示例演示了如何使用 copy-db-parameter-group
。
- AWS CLI
-
复制数据库集群参数组
以下
copy-db-parameter-group
示例创建了数据库参数组的副本。aws rds copy-db-parameter-group \ --source-db-parameter-group-identifier
mydbpg
\ --target-db-parameter-group-identifiermydbpgcopy
\ --target-db-parameter-group-description"Copy of mydbpg parameter group"
输出:
{ "DBParameterGroup": { "DBParameterGroupName": "mydbpgcopy", "DBParameterGroupArn": "arn:aws:rds:us-east-1:814387698303:pg:mydbpgcopy", "DBParameterGroupFamily": "mysql5.7", "Description": "Copy of mydbpg parameter group" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的复制数据库参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CopyDbParameterGroup
。
-
以下代码示例演示了如何使用 copy-db-snapshot
。
- AWS CLI
-
复制数据库快照
以下
copy-db-snapshot
示例创建了数据库快照副本。aws rds copy-db-snapshot \ --source-db-snapshot-identifier
rds:database-mysql-2019-06-06-08-38
--target-db-snapshot-identifiermydbsnapshotcopy
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的复制快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CopyDbSnapshot
。
-
以下代码示例演示了如何使用 copy-option-group
。
- AWS CLI
-
复制选项组
以下
copy-option-group
示例创建了选项组的副本。aws rds copy-option-group \ --source-option-group-identifier
myoptiongroup
\ --target-option-group-identifiernew-option-group
\ --target-option-group-description"My option group copy"
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的为选项组创建副本。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CopyOptionGroup
。
-
以下代码示例演示了如何使用 create-blue-green-deployment
。
- AWS CLI
-
示例 1:为 RDS for MySQL 数据库实例创建蓝绿部署
以下
create-blue-green-deployment
示例为 MySQL 数据库实例创建了蓝绿部署。aws rds create-blue-green-deployment \ --blue-green-deployment-name
bgd-cli-test-instance
\ --sourcearn:aws:rds:us-east-1:123456789012:db:my-db-instance
\ --target-engine-version8.0
\ --target-db-parameter-group-namemysql-80-group
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的创建蓝绿部署。
示例 2:为 Aurora MySQL 数据库集群创建蓝绿部署
以下
create-blue-green-deployment
示例为 Aurora MySQL 数据库集群创建了蓝绿部署。aws rds create-blue-green-deployment \ --blue-green-deployment-name
my-blue-green-deployment
\ --sourcearn:aws:rds:us-east-1:123456789012:cluster:my-aurora-mysql-cluster
\ --target-engine-version8.0
\ --target-db-cluster-parameter-group-nameams-80-binlog-enabled
\ --target-db-parameter-group-namemysql-80-cluster-group
输出:
{ "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" } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的创建蓝绿部署。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateBlueGreenDeployment
。
-
以下代码示例演示了如何使用 create-db-cluster-endpoint
。
- AWS CLI
-
创建自定义数据库集群端点
以下
create-db-cluster-endpoint
示例创建了自定义数据库集群端点并将其与指定的 Aurora 数据库集群相关联。aws rds create-db-cluster-endpoint \ --db-cluster-endpoint-identifier
mycustomendpoint
\ --endpoint-typereader
\ --db-cluster-identifiermydbcluster
\ --static-membersdbinstance1
dbinstance2
输出:
{ "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" }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的 Amazon Aurora 连接管理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDbClusterEndpoint
。
-
以下代码示例演示了如何使用 create-db-cluster-parameter-group
。
- AWS CLI
-
创建数据库集群参数组
以下
create-db-cluster-parameter-group
示例创建了一个数据库集群参数组。aws rds create-db-cluster-parameter-group \ --db-cluster-parameter-group-name
mydbclusterparametergroup
\ --db-parameter-group-familyaurora5.6
\ --description"My new cluster parameter group"
输出:
{ "DBClusterParameterGroup": { "DBClusterParameterGroupName": "mydbclusterparametergroup", "DBParameterGroupFamily": "aurora5.6", "Description": "My new cluster parameter group", "DBClusterParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:cluster-pg:mydbclusterparametergroup" } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的创建数据库集群参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDbClusterParameterGroup
。
-
以下代码示例演示了如何使用 create-db-cluster-snapshot
。
- AWS CLI
-
创建数据库集群快照
以下
create-db-cluster-snapshot
示例创建了数据库集群快照。aws rds create-db-cluster-snapshot \ --db-cluster-identifier
mydbcluster
\ --db-cluster-snapshot-identifiermydbclustersnapshot
输出:
{ "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 } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的创建数据库集群快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDbClusterSnapshot
。
-
以下代码示例演示了如何使用 create-db-cluster
。
- AWS CLI
-
示例 1:创建与 MySQL 5.7 兼容的数据库集群
以下
create-db-cluster
示例使用默认引擎版本创建与 MySQL 5.7 兼容的数据库集群。然后,将示例密码secret99
替换为安全密码。在使用控制台创建数据库集群时,Amazon RDS 会为您的数据库集群自动创建写入器数据库实例。但是,使用 AWS CLI 创建数据库集群时,必须使用create-db-instance
AWS CLI 命令显式为数据库集群创建写入器数据库实例。aws rds create-db-cluster \ --db-cluster-identifier
sample-cluster
\ --engineaurora-mysql
\ --engine-version5.7
\ --master-usernameadmin
\ --master-user-passwordsecret99
\ --db-subnet-group-namedefault
\ --vpc-security-group-idssg-0b9130572daf3dc16
输出:
{ "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 } }
示例 2:创建与 PostgreSQL 兼容的数据库集群
以下
create-db-cluster
示例使用默认引擎版本创建与 PostgreSQL 兼容的数据库集群。然后,将示例密码secret99
替换为安全密码。在使用控制台创建数据库集群时,Amazon RDS 会为您的数据库集群自动创建写入器数据库实例。但是,使用 AWS CLI 创建数据库集群时,必须使用create-db-instance
AWS CLI 命令显式为数据库集群创建写入器数据库实例。aws rds create-db-cluster \ --db-cluster-identifier
sample-pg-cluster
\ --engineaurora-postgresql
\ --master
-username master \ --master-user-passwordsecret99
\ --db-subnet-group-namedefault
\ --vpc-security-group-idssg-0b9130572daf3dc16
输出:
{ "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" } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的创建 Amazon Aurora 数据库集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDbCluster
。
-
以下代码示例演示了如何使用 create-db-instance-read-replica
。
- AWS CLI
-
创建数据库实例只读副本
此示例为名为
test-instance
的现有数据库实例创建只读副本。只读副本名为test-instance-repl
。aws rds create-db-instance-read-replica \ --db-instance-identifier
test-instance-repl
\ --source-db-instance-identifiertest-instance
输出:
{ "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... } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDbInstanceReadReplica
。
-
以下代码示例演示了如何使用 create-db-instance
。
- AWS CLI
-
创建数据库实例
以下
create-db-instance
示例使用所需的选项启动新的数据库实例。aws rds create-db-instance \ --db-instance-identifier
test-mysql-instance
\ --db-instance-classdb.t3.micro
\ --enginemysql
\ --master-usernameadmin
\ --master-user-passwordsecret99
\ --allocated-storage20
输出:
{ "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": [] } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的创建 Amazon RDS 数据库实例。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDBInstance
。
-
以下代码示例演示了如何使用 create-db-parameter-group
。
- AWS CLI
-
创建数据库参数组
以下
create-db-parameter-group
示例创建一个数据库参数组。aws rds create-db-parameter-group \ --db-parameter-group-name
mydbparametergroup
\ --db-parameter-group-familyMySQL5.6
\ --description"My new parameter group"
输出:
{ "DBParameterGroup": { "DBParameterGroupName": "mydbparametergroup", "DBParameterGroupFamily": "mysql5.6", "Description": "My new parameter group", "DBParameterGroupArn": "arn:aws:rds:us-east-1:123456789012:pg:mydbparametergroup" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的创建数据库参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDBParameterGroup
。
-
以下代码示例演示了如何使用 create-db-proxy-endpoint
。
- AWS CLI
-
为 RDS 数据库创建数据库代理端点
以下
create-db-proxy-endpoint
示例创建了一个数据库代理端点。aws rds create-db-proxy-endpoint \ --db-proxy-name
proxyExample
\ --db-proxy-endpoint-name"proxyep1"
\ --vpc-subnet-idssubnetgroup1
subnetgroup2
输出:
{ "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 } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的创建代理端点和《Amazon Aurora 用户指南》中的创建代理端点。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDbProxyEndpoint
。
-
以下代码示例演示了如何使用 create-db-proxy
。
- AWS CLI
-
为 RDS 数据库创建数据库代理
以下
create-db-proxy
示例创建了一个数据库代理。aws rds create-db-proxy \ --db-proxy-name
proxyExample
\ --engine-familyMYSQL
\ --auth Description="proxydescription1",AuthScheme="SECRETS",SecretArn="arn:aws:secretsmanager:us-west-2:123456789123:secret:secretName-1234f",IAMAuth="DISABLED",ClientPasswordAuthType="MYSQL_NATIVE_PASSWORD" \ --role-arnarn:aws:iam::123456789123:role/ProxyRole
\ --vpc-subnet-idssubnetgroup1
subnetgroup2
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的创建 RDS 代理和《Amazon Aurora 用户指南》中的创建 RDS 代理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDbProxy
。
-
以下代码示例演示了如何使用 create-db-security-group
。
- AWS CLI
-
创建 Amazon RDS 数据库安全组
以下
create-db-security-group
命令创建了一个新的 Amazon RDS 数据库安全组:aws rds create-db-security-group --db-security-group-name
mysecgroup
--db-security-group-description"My Test Security Group"
在此示例中,新的数据库安全组被命名为
mysecgroup
并带有描述。输出:
{ "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" } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDbSecurityGroup
。
-
以下代码示例演示了如何使用 create-db-shard-group
。
- AWS CLI
-
示例 1:创建 Aurora PostgreSQL 主数据库集群
以下
create-db-cluster
示例创建了一个与 Aurora Serverless v2 和 Aurora Limitless 数据库兼容的 Aurora PostgreSQL SQL 主数据库集群。aws rds create-db-cluster \ --db-cluster-identifier
my-sv2-cluster
\ --engineaurora-postgresql
\ --engine-version15.2-limitless
\ --storage-typeaurora-iopt1
\ --serverless-v2-scaling-configurationMinCapacity=2,MaxCapacity=16
\ --enable-limitless-database \ --master-usernamemyuser
\ --master-user-passwordmypassword
\ --enable-cloudwatch-logs-exportspostgresql
输出:
{ "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 } } }
示例 2:创建主(写入器)数据库实例
以下
create-db-instance
示例创建了一个 Aurora Serverless v2 主(写入器)数据库实例。在使用控制台创建数据库集群时,Amazon RDS 会为您的数据库集群自动创建写入器数据库实例。但是,使用 AWS CLI 创建数据库集群时,必须使用create-db-instance
AWS CLI 命令显式为数据库集群创建写入器数据库实例。aws rds create-db-instance \ --db-instance-identifier
my-sv2-instance
\ --db-cluster-identifiermy-sv2-cluster
\ --engineaurora-postgresql
\ --db-instance-classdb.serverless
输出:
{ "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 } }
示例 3:创建数据库分片组
以下
create-db-shard-group
示例在您的 Aurora PostgreSQL 主数据库集群中创建了一个数据库分片组。aws rds create-db-shard-group \ --db-shard-group-identifier
my-db-shard-group
\ --db-cluster-identifiermy-sv2-cluster
\ --max-acu768
输出:
{ "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" }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的使用 Aurora Serverless v2。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDbShardGroup
。
-
以下代码示例演示了如何使用 create-db-snapshot
。
- AWS CLI
-
创建数据库快照
以下
create-db-snapshot
示例创建数据库快照。aws rds create-db-snapshot \ --db-instance-identifier
database-mysql
\ --db-snapshot-identifiermydbsnapshot
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的创建数据库快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDBSnapshot
。
-
以下代码示例演示了如何使用 create-db-subnet-group
。
- AWS CLI
-
创建数据库子网组
以下
create-db-subnet-group
示例使用现有子网创建了名为mysubnetgroup
的数据库子网组。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"]
'输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的在 VPC 中创建数据库实例。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateDbSubnetGroup
。
-
以下代码示例演示了如何使用 create-event-subscription
。
- AWS CLI
-
创建事件订阅
以下
create-event-subscription
示例为当前 AWS 账户中的数据库实例创建了备份和恢复事件的订阅。您也可以将通知发送到--sns-topic-arn
指定的 Amazon Simple Notification Service 主题。aws rds create-event-subscription \ --subscription-name
my-instance-events
\ --source-typedb-instance
\ --event-categories '["backup","recovery"]
' \ --sns-topic-arnarn:aws:sns:us-east-1:123456789012:interesting-events
输出:
{ "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 } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateEventSubscription
。
-
以下代码示例演示了如何使用 create-global-cluster
。
- AWS CLI
-
创建全局数据库集群
以下
create-global-cluster
示例新建一个与 Aurora MySQL 兼容的全局数据库集群。aws rds create-global-cluster \ --global-cluster-identifier
myglobalcluster
\ --engineaurora-mysql
输出:
{ "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": [] } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的创建 Aurora 全局数据库。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateGlobalCluster
。
-
以下代码示例演示了如何使用 create-option-group
。
- AWS CLI
-
创建 Amazon RDS 选项组
以下
create-option-group
命令为Oracle Enterprise Edition
版本11.2`, is named ``MyOptionGroup
创建新的 Amazon RDS 选项组并包含了描述。aws rds create-option-group \ --option-group-name
MyOptionGroup
\ --engine-nameoracle-ee
\ --major-engine-version11.2
\ --option-group-description"Oracle Database Manager Database Control"
输出:
{ "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" } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 CreateOptionGroup
。
-
以下代码示例演示了如何使用 delete-blue-green-deployment
。
- AWS CLI
-
示例 1:在绿色环境中删除 RDS for MySQL 数据库实例的资源
以下
delete-blue-green-deployment
示例在绿色环境中删除了 RDS for MySQL 数据库实例的资源。aws rds delete-blue-green-deployment \ --blue-green-deployment-identifier
bgd-v53303651eexfake
\ --delete-target输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的删除蓝绿部署。
示例 2:在绿色环境中删除 Aurora MySQL 数据库集群的资源
以下
delete-blue-green-deployment
示例在绿色环境中删除了 Aurora MySQL 数据库集群的资源。aws rds delete-blue-green-deployment \ --blue-green-deployment-identifier
bgd-wi89nwzglccsfake
\ --delete-target输出:
{ "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" } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的删除蓝绿部署。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteBlueGreenDeployment
。
-
以下代码示例演示了如何使用 delete-db-cluster-endpoint
。
- AWS CLI
-
删除自定义数据库集群端点
以下
delete-db-cluster-endpoint
示例删除指定的自定义数据库集群端点。aws rds delete-db-cluster-endpoint \ --db-cluster-endpoint-identifier
mycustomendpoint
输出:
{ "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" }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的 Amazon Aurora 连接管理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDbClusterEndpoint
。
-
以下代码示例演示了如何使用 delete-db-cluster-parameter-group
。
- AWS CLI
-
删除数据库集群参数组
以下
delete-db-cluster-parameter-group
示例删除指定的数据库集群参数组。aws rds delete-db-cluster-parameter-group \ --db-cluster-parameter-group-name
mydbclusterparametergroup
此命令不生成任何输出。
有关更多信息,请参阅《Amazon Aurora 用户指南》中的使用数据库参数组和数据库集群参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDbClusterParameterGroup
。
-
以下代码示例演示了如何使用 delete-db-cluster-snapshot
。
- AWS CLI
-
删除数据库集群快照
以下
delete-db-cluster-snapshot
示例删除了指定的数据库集群快照。aws rds delete-db-cluster-snapshot \ --db-cluster-snapshot-identifier
mydbclustersnapshot
输出:
{ "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 } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的删除快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDbClusterSnapshot
。
-
以下代码示例演示了如何使用 delete-db-cluster
。
- AWS CLI
-
示例 1:删除数据库集群中的数据库实例
以下
delete-db-instance
示例删除了数据库集群中的最后一个数据库实例。如果数据库集群包含不处于正在删除状态的数据库实例,则无法将其删除。删除数据库集群中的数据库实例时,无法拍摄最终快照。aws rds delete-db-instance \ --db-instance-identifier
database-3
输出:
{ "DBInstance": { "DBInstanceIdentifier": "database-3", "DBInstanceClass": "db.r4.large", "Engine": "aurora-postgresql", "DBInstanceStatus": "deleting", ...output omitted... } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的删除 Aurora 数据库集群中的数据库实例。
示例 2:删除数据库集群
以下
delete-db-cluster
示例删除了名为mycluster
的数据库集群并拍摄了名为mycluster-final-snapshot
的最终快照。拍摄快照时,数据库集群的状态为可用。要跟踪删除进度,请使用describe-db-clusters
CLI 命令。aws rds delete-db-cluster \ --db-cluster-identifier
mycluster
\ --no-skip-final-snapshot \ --final-db-snapshot-identifiermycluster-final-snapshot
输出:
{ "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... } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的具有单个数据库实例的 Aurora 集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDbCluster
。
-
以下代码示例演示了如何使用 delete-db-instance-automated-backup
。
- AWS CLI
-
从区域中删除已复制的自动备份
以下
delete-db-instance-automated-backup
示例删除了具有指定 Amazon 资源名称(ARN)的自动备份。aws rds delete-db-instance-automated-backup \ --db-instance-automated-backups-arn
"arn:aws:rds:us-west-2:123456789012:auto-backup:ab-jkib2gfq5rv7replzadausbrktni2bn4example"
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的删除复制备份。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDbInstanceAutomatedBackup
。
-
以下代码示例演示了如何使用 delete-db-instance
。
- AWS CLI
-
删除数据库实例
以下
delete-db-instance
示例在创建名为test-instance-final-snap
的最终数据库快照后删除指定的数据库实例。aws rds delete-db-instance \ --db-instance-identifier
test-instance
\ --final-db-snapshot-identifiertest-instance-final-snap
输出:
{ "DBInstance": { "DBInstanceIdentifier": "test-instance", "DBInstanceStatus": "deleting", ...some output truncated... } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDBInstance
。
-
以下代码示例演示了如何使用 delete-db-parameter-group
。
- AWS CLI
-
删除数据库参数组
以下
command
示例删除一个数据库参数组。aws rds delete-db-parameter-group \ --db-parameter-group-name
mydbparametergroup
此命令不生成任何输出。
有关更多信息,请参阅《Amazon RDS 用户指南》中的使用数据库参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDBParameterGroup
。
-
以下代码示例演示了如何使用 delete-db-proxy-endpoint
。
- AWS CLI
-
删除 RDS 数据库的数据库代理端点
以下
delete-db-proxy-endpoint
示例删除了目标数据库的数据库代理端点。aws rds delete-db-proxy-endpoint \ --db-proxy-endpoint-name
proxyEP1
输出:
{ "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 } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的删除代理端点和《Amazon Aurora 用户指南》中的删除代理端点。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDbProxyEndpoint
。
-
以下代码示例演示了如何使用 delete-db-proxy
。
- AWS CLI
-
删除 RDS 数据库的数据库代理
以下
delete-db-proxy
示例删除了数据库代理。aws rds delete-db-proxy \ --db-proxy-name
proxyExample
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的删除 RDS 代理和《Amazon Aurora 用户指南》中的删除 RDS 代理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDbProxy
。
-
以下代码示例演示了如何使用 delete-db-security-group
。
- AWS CLI
-
删除数据库安全组
以下
delete-db-security-group
示例删除了名为mysecuritygroup
的数据库安全组。aws rds delete-db-security-group \ --db-security-group-name
mysecuritygroup
此命令不生成任何输出。
有关更多信息,请参阅《Amazon RDS 用户指南》中的使用数据库安全组(EC2-Classic 平台)。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDbSecurityGroup
。
-
以下代码示例演示了如何使用 delete-db-shard-group
。
- AWS CLI
-
示例 1:删除数据库分片组失败
以下
delete-db-shard-group
示例显示了在删除所有数据库和架构之前尝试删除数据库分片组时发生的错误。aws rds delete-db-shard-group \ --db-shard-group-identifier
limitless-test-shard-grp
输出:
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.
示例 2:成功删除数据库分片组
以下
delete-db-shard-group
示例在您删除所有数据库和架构(包括public
架构)后删除了数据库分片组。aws rds delete-db-shard-group \ --db-shard-group-identifier
limitless-test-shard-grp
输出:
{ "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" }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的删除 Aurora 数据库集群和数据库实例。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDbShardGroup
。
-
以下代码示例演示了如何使用 delete-db-snapshot
。
- AWS CLI
-
删除数据库快照
以下
delete-db-snapshot
示例删除了指定的数据库快照。aws rds delete-db-snapshot \ --db-snapshot-identifier
mydbsnapshot
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的删除快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDbSnapshot
。
-
以下代码示例演示了如何使用 delete-db-subnet-group
。
- AWS CLI
-
删除数据库子网组
以下
delete-db-subnet-group
示例删除了名为mysubnetgroup
的数据库子网组。aws rds delete-db-subnet-group --db-subnet-group-name
mysubnetgroup
此命令不生成任何输出。
有关更多信息,请参阅《Amazon RDS 用户指南》中的在 VPC 中使用数据库实例。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteDbSubnetGroup
。
-
以下代码示例演示了如何使用 delete-event-subscription
。
- AWS CLI
-
删除事件订阅
以下
delete-event-subscription
示例删除了指定的事件订阅。aws rds delete-event-subscription --subscription-name
my-instance-events
输出:
{ "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" } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteEventSubscription
。
-
以下代码示例演示了如何使用 delete-global-cluster
。
- AWS CLI
-
删除全局数据库集群
以下
delete-global-cluster
示例删除了与 Aurora MySQL 兼容的全局数据库集群。输出显示了您要删除的集群,但后续describe-global-clusters
命令并未列出该数据库集群。aws rds delete-global-cluster \ --global-cluster-identifier
myglobalcluster
输出:
{ "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": [] } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的删除 Aurora 全局数据库。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteGlobalCluster
。
-
以下代码示例演示了如何使用 delete-option-group
。
- AWS CLI
-
删除选项组
以下
delete-option-group
示例删除指定的选项组。aws rds delete-option-group \ --option-group-name
myoptiongroup
此命令不生成任何输出。
有关更多信息,请参阅《Amazon RDS 用户指南》中的删除选项组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeleteOptionGroup
。
-
以下代码示例演示了如何使用 deregister-db-proxy-targets
。
- AWS CLI
-
从数据库目标组中取消注册数据库代理目标
以下
deregister-db-proxy-targets
示例删除了代理proxyExample
与其目标之间的关联。aws rds deregister-db-proxy-targets \ --db-proxy-name
proxyExample
\ --db-instance-identifiersdatabase-1
此命令不生成任何输出。
有关更多信息,请参阅《Amazon RDS 用户指南》中的删除 RDS 代理和《Amazon Aurora 用户指南》中的删除 RDS 代理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DeregisterDbProxyTargets
。
-
以下代码示例演示了如何使用 describe-account-attributes
。
- AWS CLI
-
描述账户属性
以下
describe-account-attributes
示例将检索当前 AWS 账户的属性。aws rds describe-account-attributes
输出:
{ "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" } ] }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeAccountAttributes
。
-
以下代码示例演示了如何使用 describe-blue-green-deployments
。
- AWS CLI
-
示例 1:描述 RDS 数据库实例在创建完成后的蓝绿部署
以下
describe-blue-green-deployment
示例在创建完成后检索蓝绿部署的详细信息。aws rds describe-blue-green-deployments \ --blue-green-deployment-identifier
bgd-v53303651eexfake
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查看蓝绿部署。
示例 2:描述 Aurora MySQL 数据库集群的蓝绿部署
以下
describe-blue-green-deployment
示例检索蓝绿部署的详细信息。aws rds describe-blue-green-deployments \ --blue-green-deployment-identifier
bgd-wi89nwzglccsfake
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的查看蓝绿部署。
示例 3:描述 Aurora MySQL 集群在切换后的蓝绿部署
在绿色环境升级为生产环境之后,以下
describe-blue-green-deployment
示例检索有关蓝绿部署的详细信息。aws rds describe-blue-green-deployments \ --blue-green-deployment-identifier
bgd-wi89nwzglccsfake
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的查看蓝绿部署。
示例 4:描述组合蓝绿部署
以下
describe-blue-green-deployment
示例检索组合蓝绿部署的详细信息。aws rds describe-blue-green-deployments
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查看蓝绿部署和《Amazon Aurora 用户指南》中的查看蓝绿部署。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeBlueGreenDeployments
。
-
以下代码示例演示了如何使用 describe-certificates
。
- AWS CLI
-
描述证书
以下
describe-certificates
示例检索与用户默认区域关联的证书的详细信息。aws rds describe-certificates
输出:
{ "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" }
有关更多信息,请参阅《Amazon RDS 用户指南》中的使用 SSL/TLS 加密与数据库实例的连接和《Amazon Aurora 用户指南》中的使用 SSL/TLS 加密与数据库集群的连接。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeCertificates
。
-
以下代码示例演示了如何使用 describe-db-cluster-backtracks
。
- AWS CLI
-
描述数据库集群的回溯
以下
describe-db-cluster-backtracks
示例将检索指定数据库集群的详细信息。aws rds describe-db-cluster-backtracks \ --db-cluster-identifier
mydbcluster
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的回溯 Aurora 数据库集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbClusterBacktracks
。
-
以下代码示例演示了如何使用 describe-db-cluster-endpoints
。
- AWS CLI
-
示例 1:描述数据库集群端点
以下
describe-db-cluster-endpoints
示例检索数据库集群端点的详细信息。最常见的 Aurora 集群有两个端点。一个端点为WRITER
类型。您可以将此端点用于所有 SQL 语句。另一个端点为READER
类型。此端点只能用于 SELECT 和其他只读 SQL 语句。aws rds describe-db-cluster-endpoints
输出:
{ "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" } ] }
示例 2:描述单个数据库集群的数据库集群端点
以下
describe-db-cluster-endpoints
示例将检索单个指定数据库集群的数据库集群端点的详细信息。Aurora Serverless 集群只有一个类型为WRITER
的端点。aws rds describe-db-cluster-endpoints \ --db-cluster-identifier
serverless-cluster
输出:
{ "DBClusterEndpoints": [ { "Status": "available", "Endpoint": "serverless-cluster.cluster-cnpexample.us-east-1.rds.amazonaws.com", "DBClusterIdentifier": "serverless-cluster", "EndpointType": "WRITER" } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的 Amazon Aurora 连接管理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbClusterEndpoints
。
-
以下代码示例演示了如何使用 describe-db-cluster-parameter-groups
。
- AWS CLI
-
描述数据库集群参数组
以下
describe-db-cluster-parameter-groups
示例将检索有关数据库集群参数组的详细信息。aws rds describe-db-cluster-parameter-groups
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的使用数据库参数组和数据库集群参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbClusterParameterGroups
。
-
以下代码示例演示了如何使用 describe-db-cluster-parameters
。
- AWS CLI
-
示例 1:描述数据库集群参数组中的参数
以下
describe-db-cluster-parameters
示例将检索有关数据库集群参数组中参数的详细信息。aws rds describe-db-cluster-parameters \ --db-cluster-parameter-group-name
mydbclusterpg
输出:
{ "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... ] }
示例 2:仅列出数据库集群参数组中的参数名称
以下
describe-db-cluster-parameters
示例将仅检索数据库集群参数组中参数的名称。aws rds describe-db-cluster-parameters \ --db-cluster-parameter-group-name
default.aurora-mysql5.7
\ --query 'Parameters[].{ParameterName:ParameterName}
'输出:
[ { "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... } ]
示例 3:仅描述数据库集群参数组中的可修改参数
以下
describe-db-cluster-parameters
示例将仅检索可在数据库集群参数组中修改的参数的名称。aws rds describe-db-cluster-parameters \ --db-cluster-parameter-group-name
default.aurora-mysql5.7
\ --query 'Parameters[].{ParameterName:ParameterName,IsModifiable:IsModifiable} | [?IsModifiable == `true`]
'输出:
[ { "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... } ]
示例 4:仅描述数据库集群参数组中可修改的布尔参数
以下
describe-db-cluster-parameters
示例将仅检索可在数据库集群参数组中修改且包含布尔数据类型的参数的名称。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`]
'输出:
[ { "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... } ]
有关更多信息,请参阅《Amazon Aurora 用户指南》中的使用数据库参数组和数据库集群参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbClusterParameters
。
-
以下代码示例演示了如何使用 describe-db-cluster-snapshot-attributes
。
- AWS CLI
-
描述数据库集群快照的属性名称和值
以下
describe-db-cluster-snapshot-attributes
示例将检索指定数据库集群快照的属性名称和值的详细信息。aws rds describe-db-cluster-snapshot-attributes \ --db-cluster-snapshot-identifier
myclustersnapshot
输出:
{ "DBClusterSnapshotAttributesResult": { "DBClusterSnapshotIdentifier": "myclustersnapshot", "DBClusterSnapshotAttributes": [ { "AttributeName": "restore", "AttributeValues": [ "123456789012" ] } ] } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的共享数据库集群快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbClusterSnapshotAttributes
。
-
以下代码示例演示了如何使用 describe-db-cluster-snapshots
。
- AWS CLI
-
描述数据库集群的数据库集群快照
以下
describe-db-cluster-snapshots
示例将检索指定数据库集群的数据库集群快照的详细信息。aws rds describe-db-cluster-snapshots \ --db-cluster-identifier
mydbcluster
输出:
{ "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 } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的创建数据库集群快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbClusterSnapshots
。
-
以下代码示例演示了如何使用 describe-db-clusters
。
- AWS CLI
-
示例 1:描述数据库集群
以下
describe-db-clusters
示例将检索指定数据库集群的详细信息。aws rds describe-db-clusters \ --db-cluster-identifier
mydbcluster
输出:
{ "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 } ] }
示例 2:列出所有数据库集群的某些属性
以下
describe-db-clusters
示例仅检索当前 AWS 区域中所有数据库集群的DBClusterIdentifier
、Endpoint
和ReaderEndpoint
属性。aws rds describe-db-clusters \ --query '
DBClusters[].{DBClusterIdentifier:DBClusterIdentifier,Endpoint:Endpoint,ReaderEndpoint:ReaderEndpoint}
'输出:
[ { "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... } ]
示例 3:列出具有特定属性的数据库集群
以下
describe-db-clusters
示例仅检索使用aurora-postgresql
数据库引擎的数据库集群的DBClusterIdentifier
和Engine
属性。aws rds describe-db-clusters \ --query '
DBClusters[].{DBClusterIdentifier:DBClusterIdentifier,Engine:Engine} | [?Engine == `aurora-postgresql`]
'输出:
[ { "Engine": "aurora-postgresql", "DBClusterIdentifier": "pg2-cluster" } ]
有关更多信息,请参阅《Amazon Aurora 用户指南》中的 Amazon Aurora 数据库集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbClusters
。
-
以下代码示例演示了如何使用 describe-db-engine-versions
。
- AWS CLI
-
描述 MySQL 数据库引擎的数据库引擎版本
以下
describe-db-engine-versions
示例显示了有关指定数据库引擎的每个数据库引擎版本的详细信息。aws rds describe-db-engine-versions \ --engine
mysql
输出:
{ "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... ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的什么是 Amazon Relational Database Service(Amazon RDS)?。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDBEngineVersions
。
-
以下代码示例演示了如何使用 describe-db-instance-automated-backups
。
- AWS CLI
-
描述数据库实例的自动备份
以下
describe-db-instance-automated-backups
示例显示了指定数据库实例的自动备份的详细信息。详细信息包括在其他 AWS 区域复制的自动备份。aws rds describe-db-instance-automated-backups \ --db-instance-identifier
new-orcl-db
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查找有关复制备份的信息。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbInstanceAutomatedBackups
。
-
以下代码示例演示了如何使用 describe-db-instances
。
- AWS CLI
-
描述数据库实例
以下
describe-db-instances
示例将检索有关指定数据库实例的详细信息。aws rds describe-db-instances \ --db-instance-identifier
mydbinstancecf
输出:
{ "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... } ] }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDBInstances
。
-
以下代码示例演示了如何使用 describe-db-log-files
。
- AWS CLI
-
描述数据库实例的日志文件
以下
describe-db-log-files
示例将检索有关指定数据库实例的日志文件的详细信息。aws rds describe
-
db-log-files -\-db-instance-identifier
test-instance
输出:
{ "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" } ] }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbLogFiles
。
-
以下代码示例演示了如何使用 describe-db-parameter-groups
。
- AWS CLI
-
描述数据库参数组
以下
describe-db-parameter-groups
示例将检索有关数据库参数组的详细信息。aws rds describe-db-parameter-groups
输出:
{ "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... ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的使用数据库参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDBParameterGroups
。
-
以下代码示例演示了如何使用 describe-db-parameters
。
- AWS CLI
-
描述数据库参数组中的参数
以下
describe-db-parameters
示例将检索有关指定数据库参数组的详细信息。aws rds describe-db-parameters \ --db-parameter-group-name
mydbpg
输出:
{ "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... ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的使用数据库参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDBParameters
。
-
以下代码示例演示了如何使用 describe-db-proxies
。
- AWS CLI
-
描述 RDS 数据库的数据库代理
以下
describe-db-proxies
示例返回了有关数据库代理的信息。aws rds describe-db-proxies
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查看 RDS 代理和《Amazon Aurora 用户指南》中的查看 RDS 代理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbProxies
。
-
以下代码示例演示了如何使用 describe-db-proxy-endpoints
。
- AWS CLI
-
描述数据库代理端点
以下
describe-db-proxy-endpoints
示例返回了有关数据库代理端点的信息。aws rds describe-db-proxy-endpoints
输出:
{ "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 } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查看代理端点和《Amazon Aurora 用户指南》中的创建代理端点。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbProxyEndpoints
。
-
以下代码示例演示了如何使用 describe-db-proxy-target-groups
。
- AWS CLI
-
描述数据库代理端点
以下
describe-db-proxy-target-groups
示例返回了有关数据库代理目标组的信息。aws rds describe-db-proxy-target-groups \ --db-proxy-name
proxyExample
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查看 RDS 代理和《Amazon Aurora 用户指南》中的查看 RDS 代理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbProxyTargetGroups
。
-
以下代码示例演示了如何使用 describe-db-proxy-targets
。
- AWS CLI
-
描述数据库代理目标
以下
describe-db-proxy-targets
示例返回了有关数据库代理目标的信息。aws rds describe-db-proxy-targets \ --db-proxy-name
proxyExample
输出:
{ "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" } } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查看 RDS 代理和《Amazon Aurora 用户指南》中的查看 RDS 代理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbProxyTargets
。
-
以下代码示例演示了如何使用 describe-db-recommendations
。
- AWS CLI
-
示例 1:列出所有数据库建议
以下
describe-db-recommendations
示例列出了您的 AWS 账户中的所有数据库建议。aws rds describe-db-recommendations
输出:
{ "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" } ] } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查看和响应 Amazon RDS 建议和《Amazon Aurora 用户指南》中的查看和响应 Amazon RDS。
示例 2:列出高严重性数据库建议
以下
describe-db-recommendations
示例列出了您的 AWS 账户中的高严重性数据库建议。aws rds describe-db-recommendations \ --filters
Name=severity,Values=high
输出:
{ "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/" } ] } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查看和响应 Amazon RDS 建议和《Amazon Aurora 用户指南》中的查看和响应 Amazon RDS。
示例 3:列出指定数据库实例的数据库建议
以下
describe-db-recommendations
示例列出了指定数据库实例的所有数据库建议。aws rds describe-db-recommendations \ --filters
Name=dbi-resource-id,Values=database-1
输出:
{ "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" } ] } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查看和响应 Amazon RDS 建议和《Amazon Aurora 用户指南》中的查看和响应 Amazon RDS。
示例 4:列出所有有效的数据库建议
以下
describe-db-recommendations
示例列出了您的 AWS 账户中的所有有效数据库建议。aws rds describe-db-recommendations \ --filters
Name=status,Values=active
输出:
{ "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" } ] } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查看和响应 Amazon RDS 建议和《Amazon Aurora 用户指南》中的查看和响应 Amazon RDS。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbRecommendations
。
-
以下代码示例演示了如何使用 describe-db-security-groups
。
- AWS CLI
-
列出数据库安全组
以下
describe-db-security-groups
示例列出了数据库安全组。aws rds describe-db-security-groups
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的列出可用的数据库安全组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbSecurityGroups
。
-
以下代码示例演示了如何使用 describe-db-shard-groups
。
- AWS CLI
-
示例 1:描述数据库分片组
以下
describe-db-shard-groups
示例将检索有关数据库分片组的详细信息。aws rds describe-db-shard-groups
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的 Amazon Aurora 数据库集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbShardGroups
。
-
以下代码示例演示了如何使用 describe-db-snapshot-attributes
。
- AWS CLI
-
描述数据库快照的属性名称和值
以下
describe-db-snapshot-attributes
示例描述了数据库快照的属性名称和值。aws rds describe-db-snapshot-attributes \ --db-snapshot-identifier
mydbsnapshot
输出:
{ "DBSnapshotAttributesResult": { "DBSnapshotIdentifier": "mydbsnapshot", "DBSnapshotAttributes": [ { "AttributeName": "restore", "AttributeValues": [ "123456789012", "210987654321" ] } ] } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的共享数据库快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbSnapshotAttributes
。
-
以下代码示例演示了如何使用 describe-db-snapshots
。
- AWS CLI
-
示例 1:描述数据库实例的数据库快照
以下
describe-db-snapshots
示例将检索有关数据库实例的数据库快照的详细信息。aws rds describe-db-snapshots \ --db-snapshot-identifier
mydbsnapshot
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的创建数据库快照。
示例 2:查找手动拍摄的快照数量
以下
describe-db-snapshots
示例使用--query
选项中的length
运算符来返回在特定 AWS 区域拍摄的手动快照的数量。aws rds describe-db-snapshots \ --snapshot-type
manual
\ --query"length(*[].{DBSnapshots:SnapshotType})"
\ --regioneu-central-1
输出:
35
有关更多信息,请参阅《Amazon RDS 用户指南》中的创建数据库快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDBSnapshots
。
-
以下代码示例演示了如何使用 describe-db-subnet-groups
。
- AWS CLI
-
描述数据库子网组
以下
describe-db-subnet-groups
示例将检索有关指定数据库子网组的详细信息。aws rds describe-db-subnet-groups
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的 Amazon 虚拟私有云(VPC)和 Amazon RDS。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeDbSubnetGroups
。
-
以下代码示例演示了如何使用 describe-engine-default-cluster-parameters
。
- AWS CLI
-
描述 Aurora 数据库引擎的默认引擎和系统参数信息
以下
describe-engine-default-cluster-parameters
示例检索与 MySQL 5.7 兼容的 Aurora 数据库集群的默认引擎和系统参数信息的详细信息。aws rds describe-engine-default-cluster-parameters \ --db-parameter-group-family
aurora-mysql5.7
输出:
{ "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... ] } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的使用数据库参数组和数据库集群参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeEngineDefaultClusterParameters
。
-
以下代码示例演示了如何使用 describe-engine-default-parameters
。
- AWS CLI
-
描述数据库引擎的默认引擎和系统参数信息
以下
describe-engine-default-parameters
示例检索 MySQL 5.7 数据库实例的默认引擎和系统参数信息的详细信息。aws rds describe-engine-default-parameters \ --db-parameter-group-family
mysql5.7
输出:
{ "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... ] } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的使用数据库参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeEngineDefaultParameters
。
-
以下代码示例演示了如何使用 describe-event-categories
。
- AWS CLI
-
描述事件类别
以下
describe-event-categories
示例检索有关所有可用事件源的事件类别的详细信息。aws rds describe-event-categories
输出:
{ "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" ] } ] }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeEventCategories
。
-
以下代码示例演示了如何使用 describe-event-subscriptions
。
- AWS CLI
-
描述事件订阅
此示例描述了当前 AWS 账户的所有 Amazon RDS 事件订阅。
aws rds describe-event-subscriptions
输出:
{ "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... ] }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeEventSubscriptions
。
-
以下代码示例演示了如何使用 describe-events
。
- AWS CLI
-
描述事件
以下
describe-events
示例检索指定数据库实例发生的事件的详细信息。aws rds describe-events \ --source-identifier
test-instance
\ --source-typedb-instance
输出:
{ "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" } ] }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeEvents
。
-
以下代码示例演示了如何使用 describe-export-tasks
。
- AWS CLI
-
描述快照导出任务
以下
describe-export-tasks
示例返回有关将快照导出到 Amazon S3 的信息。aws rds describe-export-tasks
输出:
{ "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": "mybucket", "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": "mybucket", "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 } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的监控快照导出。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeExportTasks
。
-
以下代码示例演示了如何使用 describe-global-clusters
。
- AWS CLI
-
描述全局数据库集群
以下
describe-global-clusters
示例列出了当前 AWS 区域中的 Aurora 全局数据库集群。aws rds describe-global-clusters
输出:
{ "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": [] } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的管理 Aurora 全局数据库。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeGlobalClusters
。
-
以下代码示例演示了如何使用 describe-option-group-options
。
- AWS CLI
-
描述所有可用的选项
以下
describe-option-group-options
示例列出了 Oracle Database 19c 实例的两个选项。aws rds describe-option-group-options \ --engine-name
oracle-ee
\ --major-engine-version19
\ --max-items2
输出:
{ "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==" }
有关更多信息,请参阅《Amazon RDS 用户指南》中的列出选项组的选项和选项设置。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeOptionGroupOptions
。
-
以下代码示例演示了如何使用 describe-option-groups
。
- AWS CLI
-
描述可用的选项组
以下
describe-option-groups
示例列出了 Oracle Database 19c 实例的选项组。aws rds describe-option-groups \ --engine-name
oracle-ee
\ --major-engine-version19
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的列出选项组的选项和选项设置。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeOptionGroups
。
-
以下代码示例演示了如何使用 describe-orderable-db-instance-options
。
- AWS CLI
-
描述可订购的数据库实例选项
以下
describe-orderable-db-instance-options
示例将检索有关运行 MySQL 数据库引擎的数据库实例的可订购选项的详细信息。aws rds describe-orderable-db-instance-options \ --engine
mysql
输出:
{ "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... }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeOrderableDBInstanceOptions
。
-
以下代码示例演示了如何使用 describe-pending-maintenance-actions
。
- AWS CLI
-
列出至少包含一项待处理维护操作的资源
以下
describe-pending-maintenance-actions
示例列出了数据库实例的待处理维护操作。aws rds describe-pending-maintenance-actions
输出:
{ "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" } ] } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的维护数据库实例。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribePendingMaintenanceActions
。
-
以下代码示例演示了如何使用 describe-reserved-db-instances-offerings
。
- AWS CLI
-
描述预留的数据库实例服务
以下
describe-reserved-db-instances-offerings
示例检索有关oracle
的预留数据库实例选项的详细信息。aws rds describe-reserved-db-instances-offerings \ --product-description
oracle
输出:
{ "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... }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeReservedDbInstancesOfferings
。
-
以下代码示例演示了如何使用 describe-reserved-db-instances
。
- AWS CLI
-
描述预留的数据库实例
以下
describe-reserved-db-instances
示例检索有关当前 AWS 账户中任意预留数据库实例的详细信息。aws rds describe-reserved-db-instances
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的 Amazon RDS 的预留数据库实例。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeReservedDbInstances
。
-
以下代码示例演示了如何使用 describe-source-regions
。
- AWS CLI
-
描述源区域
以下
describe-source-regions
示例检索有关所有源 AWS 区域的详细信息。它还显示,自动备份只能从美国西部(俄勒冈州)复制到目标 AWS 区域,即美国东部(弗吉尼亚州北部)。aws rds describe-source-regions \ --region
us-east-1
输出:
{ "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 } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的查找有关复制备份的信息。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeSourceRegions
。
-
以下代码示例演示了如何使用 describe-valid-db-instance-modifications
。
- AWS CLI
-
描述数据库实例的有效修改
以下
describe-valid-db-instance-modifications
示例将检索有关指定数据库实例的有效修改的详细信息。aws rds describe-valid-db-instance-modifications \ --db-instance-identifier
test-instance
输出:
{ "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" } ] } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DescribeValidDbInstanceModifications
。
-
以下代码示例演示了如何使用 download-db-log-file-portion
。
- AWS CLI
-
下载数据库日志文件
以下
download-db-log-file-portion
示例仅下载日志文件的最新部分,将其保存到名为tail.txt
的本地文件中。aws rds download-db-log-file-portion \ --db-instance-identifier
test-instance
\ --log-file-namelog.txt
\ --outputtext
>
tail.txt
要下载整个文件,需要包含
--starting-token 0
参数。以下示例将输出保存至名为full.txt
的本地文件中。aws rds download-db-log-file-portion \ --db-instance-identifier
test-instance
\ --log-file-namelog.txt
\ --starting-token0
\ --outputtext
>
full.txt
保存的文件可能包含空行。下载时,它们会出现在日志文件每个部分的末尾。这通常不会给您的日志文件分析带来任何麻烦。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 DownloadDbLogFilePortion
。
-
以下代码示例演示了如何使用 generate-auth-token
。
- AWS CLI
-
生成身份验证令牌
以下
generate-db-auth-token
示例生成与 IAM 数据库身份验证一起使用的身份验证令牌。aws rds generate-db-auth-token \ --hostname
aurmysql-test.cdgmuqiadpid.us-west-2.rds.amazonaws.com
\ --port3306
\ --regionus-east-1
\ --usernamejane_doe
输出:
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
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 GenerateAuthToken
。
-
以下代码示例演示了如何使用 generate-db-auth-token
。
- AWS CLI
-
生成 IAM 身份验证令牌
以下
generate-db-auth-token
示例生成了用于连接到数据库的 IAM 身份验证令牌。aws rds generate-db-auth-token \ --hostname
mydb.123456789012.us-east-1.rds.amazonaws.com
\ --port3306
\ --regionus-east-1
\ --usernamedb_user
输出:
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
有关更多信息,请参阅《Amazon RDS 用户指南》中的使用 IAM 身份验证连接到数据库实例和《Amazon Aurora 用户指南》中的使用 IAM 身份验证连接到数据库集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 GenerateDbAuthToken
。
-
以下代码示例演示了如何使用 list-tags-for-resource
。
- AWS CLI
-
列出 Amazon RDS 资源上的标签
以下
list-tags-for-resource
示例列出了数据库实例上的所有标签。aws rds list-tags-for-resource \ --resource-name
arn:aws:rds:us-east-1:123456789012:db:orcl1
输出:
{ "TagList": [ { "Key": "Environment", "Value": "test" }, { "Key": "Name", "Value": "MyDatabase" } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的为 Amazon RDS 资源添加标签。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ListTagsForResource
。
-
以下代码示例演示了如何使用 modify-certificates
。
- AWS CLI
-
临时覆盖新数据库实例的系统默认 SSL/TLS 证书
以下
modify-certificates
示例临时覆盖新数据库实例的系统默认 SSL/TLS 证书。aws rds modify-certificates \ --certificate-identifier
rds-ca-2019
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的轮换 SSL/TLS 证书和《Amazon Aurora 用户指南》中的轮换 SSL/TLS 证书。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyCertificates
。
-
以下代码示例演示了如何使用 modify-current-db-cluster-capacity
。
- AWS CLI
-
扩展 Aurora Serverless 数据库集群的容量
以下
modify-current-db-cluster-capacity
示例将 Aurora Serverless 数据库集群的容量扩展到 8。aws rds modify-current-db-cluster-capacity \ --db-cluster-identifier
mydbcluster
\ --capacity8
输出:
{ "DBClusterIdentifier": "mydbcluster", "PendingCapacity": 8, "CurrentCapacity": 1, "SecondsBeforeTimeout": 300, "TimeoutAction": "ForceApplyCapacityChange" }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的手动扩展 Aurora Serverless v1 数据库集群容量。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyCurrentDbClusterCapacity
。
-
以下代码示例演示了如何使用 modify-db-cluster-endpoint
。
- AWS CLI
-
修改自定义数据库集群端点
以下
modify-db-cluster-endpoint
示例修改了指定的自定义数据库集群端点。aws rds modify-db-cluster-endpoint \ --db-cluster-endpoint-identifier
mycustomendpoint
\ --static-membersdbinstance1
dbinstance2
dbinstance3
输出:
{ "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" }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的 Amazon Aurora 连接管理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbClusterEndpoint
。
-
以下代码示例演示了如何使用 modify-db-cluster-parameter-group
。
- AWS CLI
-
修改数据库集群参数组中的参数
以下
modify-db-cluster-parameter-group
示例修改了数据库集群参数组中的参数的值。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"
输出:
{ "DBClusterParameterGroupName": "mydbclusterpg" }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的使用数据库参数组和数据库集群参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbClusterParameterGroup
。
-
以下代码示例演示了如何使用 modify-db-cluster-snapshot-attribute
。
- AWS CLI
-
修改数据库集群快照属性
以下
modify-db-cluster-snapshot-attribute
示例对指定的数据库集群快照属性进行了更改。aws rds modify-db-cluster-snapshot-attribute \ --db-cluster-snapshot-identifier
myclustersnapshot
\ --attribute-namerestore
\ --values-to-add123456789012
输出:
{ "DBClusterSnapshotAttributesResult": { "DBClusterSnapshotIdentifier": "myclustersnapshot", "DBClusterSnapshotAttributes": [ { "AttributeName": "restore", "AttributeValues": [ "123456789012" ] } ] } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的从数据库集群快照还原。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbClusterSnapshotAttribute
。
-
以下代码示例演示了如何使用 modify-db-cluster
。
- AWS CLI
-
示例 1:修改数据库集群
以下
modify-db-cluster
示例更改了名为cluster-2
的数据库集群的主用户密码,并将备份保留期设置为 14 天。--apply-immediately
参数使得可以立即进行更改,而不是等到下一个维护时段。aws rds modify-db-cluster \ --db-cluster-identifier
cluster-2
\ --backup-retention-period14
\ --master-user-passwordnewpassword99
\ --apply-immediately输出:
{ "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": [] } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的修改 Amazon Aurora 数据库集群。
示例 2:将 VPC 安全组与数据库集群关联
以下
modify-db-instance
示例关联特定 VPC 安全组并从数据库集群中移除数据库安全组。aws rds modify-db-cluster \ --db-cluster-identifier
dbName
\ --vpc-security-group-idssg-ID
输出:
{ "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... } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的使用安全组控制访问权限。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbCluster
。
-
以下代码示例演示了如何使用 modify-db-instance
。
- AWS CLI
-
示例 1:修改数据库实例
以下
modify-db-instance
示例将选项组和参数组与兼容的 Microsoft SQL Server 数据库实例相关联。--apply-immediately
参数使选项和参数组立即关联,而不是等到下一个维护时段。aws rds modify-db-instance \ --db-instance-identifier
database-2
\ --option-group-nametest-se-2017
\ --db-parameter-group-nametest-sqlserver-se-2017
\ --apply-immediately输出:
{ "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 } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的修改 Amazon RDS 数据库实例。
示例 2:将 VPC 安全组与数据库实例关联
以下
modify-db-instance
示例关联特定 VPC 安全组并从数据库实例中移除数据库安全组:aws rds modify-db-instance \ --db-instance-identifier
dbName
\ --vpc-security-group-idssg-ID
输出:
{ "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 ommited ... } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的使用安全组控制访问权限。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDBInstance
。
-
以下代码示例演示了如何使用 modify-db-parameter-group
。
- AWS CLI
-
修改数据库参数组
以下
modify-db-parameter-group
示例将更改数据库参数组中clr enabled
参数的值。--apply-immediately
参数使数据库参数组得到立即修改,而不是等到下一个维护时段。aws rds modify-db-parameter-group \ --db-parameter-group-name
test-sqlserver-se-2017
\ --parameters"ParameterName='clr enabled',ParameterValue=1,ApplyMethod=immediate"
输出:
{ "DBParameterGroupName": "test-sqlserver-se-2017" }
有关更多信息,请参阅《Amazon RDS 用户指南》中的修改数据库参数组中的参数。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDBParameterGroup
。
-
以下代码示例演示了如何使用 modify-db-proxy-endpoint
。
- AWS CLI
-
修改 RDS 数据库的数据库代理端点
以下
modify-db-proxy-endpoint
示例修改了数据库代理端点proxyEndpoint
,以将读取超时设置为 65 秒。aws rds modify-db-proxy-endpoint \ --db-proxy-endpoint-name
proxyEndpoint
\ --cli-read-timeout65
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的修改代理端点和《Amazon Aurora 用户指南》中的修改代理端点。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbProxyEndpoint
。
-
以下代码示例演示了如何使用 modify-db-proxy-target-group
。
- AWS CLI
-
修改数据库代理端点
以下
modify-db-proxy-target-group
示例修改了数据库代理目标组,将最大连接数设置为 80,并将最大空闲连接数设置为 10。aws rds modify-db-proxy-target-group \ --target-group-name
default
\ --db-proxy-nameproxyExample
\ --connection-pool-configMaxConnectionsPercent=80,MaxIdleConnectionsPercent=10
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的修改 RDS 代理和《Amazon Aurora 用户指南》中的修改 RDS 代理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbProxyTargetGroup
。
-
以下代码示例演示了如何使用 modify-db-proxy
。
- AWS CLI
-
修改 RDS 数据库的数据库代理
以下
modify-db-proxy
示例修改了名为proxyExample
的数据库代理,使其连接需要 SSL。aws rds modify-db-proxy \ --db-proxy-name
proxyExample
\ --require-tls输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的修改 RDS 代理和《Amazon Aurora 用户指南》中的创建 RDS 代理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbProxy
。
-
以下代码示例演示了如何使用 modify-db-shard-group
。
- AWS CLI
-
示例 1:修改数据库分片组
以下
modify-db-shard-group
示例更改了数据库分片组的最大容量。aws rds modify-db-shard-group \ --db-shard-group-identifier
my-db-shard-group
\ --max-acu1000
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的 Amazon Aurora 数据库集群。
示例 2:描述您的数据库分片组
以下
describe-db-shard-groups
示例将在您运行modify-db-shard-group
命令后检索数据库分片组的详细信息。现在,数据库分片组my-db-shard-group
的最大容量为 1000 个 Aurora 容量单元(ACU)。aws rds describe-db-shard-groups
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的 Amazon Aurora 数据库集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbShardGroup
。
-
以下代码示例演示了如何使用 modify-db-snapshot-attribute
。
- AWS CLI
-
示例 1:允许两个 AWS 账户还原数据库快照
以下
modify-db-snapshot-attribute
示例将向两个 AWS 账户(标识符为111122223333
和444455556666
)授予还原名为mydbsnapshot
的数据库快照的权限。aws rds modify-db-snapshot-attribute \ --db-snapshot-identifier
mydbsnapshot
\ --attribute-namerestore
\ --values-to-add {"111122223333","444455556666"}输出:
{ "DBSnapshotAttributesResult": { "DBSnapshotIdentifier": "mydbsnapshot", "DBSnapshotAttributes": [ { "AttributeName": "restore", "AttributeValues": [ "111122223333", "444455556666" ] } ] } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的共享快照。
示例 2:防止 AWS 账户还原数据库快照
以下
modify-db-snapshot-attribute
示例删除了特定 AWS 账户还原名为mydbsnapshot
的数据库快照的权限。指定单个账户时,账户标识符不能用引号或大括号括起来。aws rds modify-db-snapshot-attribute \ --db-snapshot-identifier
mydbsnapshot
\ --attribute-namerestore
\ --values-to-remove444455556666
输出:
{ "DBSnapshotAttributesResult": { "DBSnapshotIdentifier": "mydbsnapshot", "DBSnapshotAttributes": [ { "AttributeName": "restore", "AttributeValues": [ "111122223333" ] } ] } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的共享快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbSnapshotAttribute
。
-
以下代码示例演示了如何使用 modify-db-snapshot-attributes
。
- AWS CLI
-
修改数据库快照属性
以下
modify-db-snapshot-attribute
示例允许两个 AWS 账户标识符(111122223333
和444455556666
)还原名为mydbsnapshot
的数据库快照。aws rds modify-db-snapshot-attribute \ --db-snapshot-identifier
mydbsnapshot
\ --attribute-namerestore
\ --values-to-add '["111122223333","444455556666"]
'输出:
{ "DBSnapshotAttributesResult": { "DBSnapshotIdentifier": "mydbsnapshot", "DBSnapshotAttributes": [ { "AttributeName": "restore", "AttributeValues": [ "111122223333", "444455556666" ] } ] } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的共享快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbSnapshotAttributes
。
-
以下代码示例演示了如何使用 modify-db-snapshot
。
- AWS CLI
-
修改数据库快照
以下
modify-db-snapshot
示例将名为db5-snapshot-upg-test
的 PostgeSQL 10.6 快照升级为 PostgreSQL 11.7。新的数据库引擎版本将在快照完成升级且其状态变为可用后显示。aws rds modify-db-snapshot \ --db-snapshot-identifier
db5-snapshot-upg-test
\ --engine-version11.7
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的升级 PostgreSQL 数据库快照。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbSnapshot
。
-
以下代码示例演示了如何使用 modify-db-subnet-group
。
- AWS CLI
-
修改数据库子网组
以下
modify-db-subnet-group
示例将 ID 为subnet-08e41f9e230222222
的子网添加到名为mysubnetgroup
的数据库子网组。要保留现有子网组中的子网,请在--subnet-ids
选项中包含其 ID 作为值。确保数据库子网组中的子网至少位于两个不同的可用区中。aws rds modify-db-subnet-group \ --db-subnet-group-name
mysubnetgroup
\ --subnet-ids '["subnet-0a1dc4e1a6f123456","subnet-070dd7ecb3aaaaaaa","subnet-00f5b198bc0abcdef","subnet-08e41f9e230222222"]
'输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的步骤 3:创建数据库子网组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyDbSubnetGroup
。
-
以下代码示例演示了如何使用 modify-event-subscription
。
- AWS CLI
-
修改事件订阅
以下
modify-event-subscription
示例禁用了指定的事件订阅,使其不再向指定的 Amazon Simple Notification Service 主题发布通知。aws rds modify-event-subscription \ --subscription-name
my-instance-events
\ --no-enabled输出:
{ "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 } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyEventSubscription
。
-
以下代码示例演示了如何使用 modify-global-cluster
。
- AWS CLI
-
修改全局数据库集群
以下
modify-global-cluster
示例启用了与 Aurora MySQL 兼容的全局数据库集群的删除保护。aws rds modify-global-cluster \ --global-cluster-identifier
myglobalcluster
\ --deletion-protection输出:
{ "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": [] } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的管理 Aurora 全局数据库。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ModifyGlobalCluster
。
-
以下代码示例演示了如何使用 promote-read-replica-db-cluster
。
- AWS CLI
-
提升数据库集群只读副本
以下
promote-read-replica-db-cluster
示例将指定的只读副本提升为独立的数据库集群。aws rds promote-read-replica-db-cluster \ --db-cluster-identifier
mydbcluster-1
输出:
{ "DBCluster": { "AllocatedStorage": 1, "AvailabilityZones": [ "us-east-1a", "us-east-1b", "us-east-1c" ], "BackupRetentionPeriod": 1, "DatabaseName": "", "DBClusterIdentifier": "mydbcluster-1", ...some output truncated... } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的将只读副本提升为数据库集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 PromoteReadReplicaDbCluster
。
-
以下代码示例演示了如何使用 promote-read-replica
。
- AWS CLI
-
提升只读副本
以下
promote-read-replica
示例将指定的只读副本提升为独立的数据库实例。aws rds promote-read-replica \ --db-instance-identifier
test-instance-repl
输出:
{ "DBInstance": { "DBInstanceArn": "arn:aws:rds:us-east-1:123456789012:db:test-instance-repl", "StorageType": "standard", "ReadReplicaSourceDBInstanceIdentifier": "test-instance", "DBInstanceStatus": "modifying", ...some output truncated... } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 PromoteReadReplica
。
-
以下代码示例演示了如何使用 purchase-reserved-db-instance
。
- AWS CLI
-
购买预留数据库实例服务
以下
purchase-reserved-db-instances-offering
示例购买了预留数据库实例服务。reserved-db-instances-offering-id
必须是describe-reserved-db-instances-offering
命令返回的有效产品编号。aws rds purchase-reserved-db-instances-offering --reserved-db-instances-offering-id 438012d3-4a52-4cc7-b2e3-8dff72e0e706
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 PurchaseReservedDbInstance
。
-
以下代码示例演示了如何使用 purchase-reserved-db-instances-offerings
。
- AWS CLI
-
示例 1:查找要购买的预留数据库实例
以下
describe-reserved-db-instances-offerings
示例列出了实例类为 db.t2.micro 且持续时间为一年的可用预留 MySQL 数据库实例。购买预留数据库实例需要提供产品 ID。aws rds describe-reserved-db-instances-offerings \ --product-description
mysql
\ --db-instance-classdb.t2.micro
\ --duration1
输出:
{ "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 ... ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的 Amazon RDS 的预留数据库实例。
示例 2:购买预留数据库实例
以下
purchase-reserved-db-instances-offering
示例演示如何购买上一个示例中的预留数据库实例服务。aws rds purchase-reserved-db-instances-offering --reserved-db-instances-offering-id 8ba30be1-b9ec-447f-8f23-6114e3f4c7b4
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的 Amazon RDS 的预留数据库实例。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 PurchaseReservedDbInstancesOfferings
。
-
以下代码示例演示了如何使用 reboot-db-instance
。
- AWS CLI
-
重启数据库实例
以下
reboot-db-instance
示例开始重启指定的数据库实例。aws rds reboot-db-instance \ --db-instance-identifier
test-mysql-instance
输出:
{ "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... } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的重启数据库实例。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RebootDBInstance
。
-
以下代码示例演示了如何使用 reboot-db-shard-group
。
- AWS CLI
-
示例 1:重启数据库分片组
以下
reboot-db-shard-group
示例重新启动数据库分片组。aws rds reboot-db-shard-group \ --db-shard-group-identifier
my-db-shard-group
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的重启 Amazon Aurora 数据库实例。
示例 2:描述您的数据库分片组
以下
describe-db-shard-groups
示例将在您运行reboot-db-shard-group
命令后检索数据库分片组的详细信息。数据库分片组my-db-shard-group
现在正在重启。aws rds describe-db-shard-groups
输出:
{ "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" } ] }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的重启 Amazon Aurora 数据库实例。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RebootDbShardGroup
。
-
以下代码示例演示了如何使用 register-db-proxy-targets
。
- AWS CLI
-
向数据库注册数据库代理
以下
register-db-proxy-targets
示例创建了数据库与代理之间的关联。aws rds register-db-proxy-targets \ --db-proxy-name
proxyExample
\ --db-cluster-identifiersdatabase-5
输出:
{ "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" } } ] }
有关更多信息,请参阅《Amazon RDS 用户指南》中的创建 RDS 代理和《Amazon Aurora 用户指南》中的创建 RDS 代理。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RegisterDbProxyTargets
。
-
以下代码示例演示了如何使用 remove-from-global-cluster
。
- AWS CLI
-
将 Aurora 辅助集群从 Aurora 全局数据库集群中分离
以下
remove-from-global-cluster
示例将 Aurora 辅助集群从 Aurora 全局数据库集群中分离。集群从只读变为具有读写能力的独立集群。aws rds remove-from-global-cluster \ --region
us-west-2
\ --global-cluster-identifiermyglobalcluster
\ --db-cluster-identifierarn:aws:rds:us-west-2:123456789012:cluster:DB-1
输出:
{ "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" } ] } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的从 Amazon Aurora Global Database 删除集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RemoveFromGlobalCluster
。
-
以下代码示例演示了如何使用 remove-option-from-option-group
。
- AWS CLI
-
从选项组中删除选项
以下
remove-option-from-option-group
示例从myoptiongroup
中删除了OEM
选项。aws rds remove-option-from-option-group \ --option-group-name
myoptiongroup
\ --optionsOEM
\ --apply-immediately输出:
{ "OptionGroup": { "OptionGroupName": "myoptiongroup", "OptionGroupDescription": "Test", "EngineName": "oracle-ee", "MajorEngineVersion": "19", "Options": [], "AllowsVpcAndNonVpcInstanceMemberships": true, "OptionGroupArn": "arn:aws:rds:us-east-1:123456789012:og:myoptiongroup" } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的从选项组中删除选项。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RemoveOptionFromOptionGroup
。
-
以下代码示例演示了如何使用 remove-role-from-db-cluster
。
- AWS CLI
-
取消 AWS Identity and Access Management(IAM)角色与数据库集群的关联
以下
remove-role-from-db-cluster
示例从数据库集群中删除角色。aws rds remove-role-from-db-cluster \ --db-cluster-identifier
mydbcluster
\ --role-arnarn:aws:iam::123456789012:role/RDSLoadFromS3
此命令不生成任何输出。
有关更多信息,请参阅《Amazon Aurora 用户指南》中的将 IAM 角色与 Amazon Aurora MySQL 数据库集群相关联。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RemoveRoleFromDbCluster
。
-
以下代码示例演示了如何使用 remove-role-from-db-instance
。
- AWS CLI
-
取消 AWS Identity and Access Management(IAM)角色与数据库实例的关联
以下
remove-role-from-db-instance
示例从名为test-instance
的 Oracle 数据库实例中删除了名为rds-s3-integration-role
的角色。aws rds remove-role-from-db-instance \ --db-instance-identifier
test-instance
\ --feature-nameS3_INTEGRATION
\ --role-arnarn:aws:iam::111122223333:role/rds-s3-integration-role
此命令不生成任何输出。
有关更多信息,请参阅《Amazon RDS 用户指南》中的禁用 RDS SQL Server 与 S3 的集成。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RemoveRoleFromDbInstance
。
-
以下代码示例演示了如何使用 remove-source-identifier-from-subscription
。
- AWS CLI
-
从订阅中删除源标识符
以下
remove-source-identifier
示例将从现有订阅中删除指定的源标识符。aws rds remove-source-identifier-from-subscription \ --subscription-name
my-instance-events
\ --source-identifiertest-instance-repl
输出:
{ "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 } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RemoveSourceIdentifierFromSubscription
。
-
以下代码示例演示了如何使用 remove-tags-from-resource
。
- AWS CLI
-
从资源中删除标签
以下
remove-tags-from-resource
示例将从源中删除标签。aws rds remove-tags-from-resource \ --resource-name
arn:aws:rds:us-east-1:123456789012:db:mydbinstance
\ --tag-keysName
Environment
此命令不生成任何输出。
有关更多信息,请参阅《Amazon RDS 用户指南》中的为 Amazon RDS 资源添加标签和《Amazon Aurora 用户指南》中的为 Amazon RDS 资源添加标签。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RemoveTagsFromResource
。
-
以下代码示例演示了如何使用 reset-db-cluster-parameter-group
。
- AWS CLI
-
示例 1:将所有参数重置为其默认值
以下
reset-db-cluster-parameter-group
示例将客户创建的数据库集群参数组中的所有参数值重置为默认值。aws rds reset-db-cluster-parameter-group \ --db-cluster-parameter-group-name
mydbclpg
\ --reset-all-parameters输出:
{ "DBClusterParameterGroupName": "mydbclpg" }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的使用数据库参数组和数据库集群参数组。
示例 2:将指定的参数重置为其默认值
以下
reset-db-cluster-parameter-group
示例将客户创建的数据库集群参数组中的特定参数的参数值重置为默认值。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"
输出:
{ "DBClusterParameterGroupName": "mydbclpg" }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的使用数据库参数组和数据库集群参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ResetDbClusterParameterGroup
。
-
以下代码示例演示了如何使用 reset-db-parameter-group
。
- AWS CLI
-
示例 1:将所有参数重置为其默认值
以下
reset-db-parameter-group
示例将客户创建的数据库参数组中的所有参数值重置为默认值。aws rds reset-db-parameter-group \ --db-parameter-group-name
mypg
\ --reset-all-parameters输出:
{ "DBParameterGroupName": "mypg" }
有关更多信息,请参阅《Amazon RDS 用户指南》中的使用数据库参数组和《Amazon Aurora 用户指南》中的使用数据库参数组和数据库集群参数组。
示例 2:将指定的参数重置为其默认值
以下
reset-db-parameter-group
示例将客户创建的数据库参数组中的特定参数的参数值重置为默认值。aws rds reset-db-parameter-group \ --db-parameter-group-name
mypg
\ --parameters"ParameterName=max_connections,ApplyMethod=immediate"
\"ParameterName=max_allowed_packet,ApplyMethod=immediate"
输出:
{ "DBParameterGroupName": "mypg" }
有关更多信息,请参阅《Amazon RDS 用户指南》中的使用数据库参数组和《Amazon Aurora 用户指南》中的使用数据库参数组和数据库集群参数组。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 ResetDbParameterGroup
。
-
以下代码示例演示了如何使用 restore-db-cluster-from-s3
。
- AWS CLI
-
从 Amazon S3 还原 Amazon Aurora 数据库集群
以下
restore-db-cluster-from-s3
示例从 Amazon S3 中的 MySQL 5.7 数据库备份文件中还原了与 Amazon Aurora MySQL 版本 5.7 兼容的数据库集群。aws rds restore-db-cluster-from-s3 \ --db-cluster-identifier
cluster-s3-restore
\ --engineaurora-mysql
\ --master-usernameadmin
\ --master-user-passwordmypassword
\ --s3-bucket-namemybucket
\ --s3-prefixtest-backup
\ --s3-ingestion-role-arnarn:aws:iam::123456789012:role/service-role/TestBackup
\ --source-enginemysql
\ --source-engine-version5.7.28
输出:
{ "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": [] } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的通过使用 Amazon S3 存储桶从 MySQL 中迁移数据。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RestoreDbClusterFromS3
。
-
以下代码示例演示了如何使用 restore-db-cluster-from-snapshot
。
- AWS CLI
-
从快照还原数据库集群
以下
restore-db-cluster-from-snapshot
示例从名为test-instance-snapshot
的数据库集群快照还原与 PostgreSQL 版本 10.7 兼容的 Aurora PostgreSQL 数据库集群。aws rds restore-db-cluster-from-snapshot \ --db-cluster-identifier
newdbcluster
\ --snapshot-identifiertest-instance-snapshot
\ --engineaurora-postgresql
\ --engine-version10.7
输出:
{ "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": [] } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的从数据库集群快照还原。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RestoreDbClusterFromSnapshot
。
-
以下代码示例演示了如何使用 restore-db-cluster-to-point-in-time
。
- AWS CLI
-
将数据库集群还原到指定时间
以下
restore-db-cluster-to-point-in-time
示例将名为database-4
的数据库集群还原到尽可能晚的时间。使用copy-on-write
作为还原类型,将新数据库集群还原为源数据库集群的克隆。aws rds restore-db-cluster-to-point-in-time \ --source-db-cluster-identifier
database-4
\ --db-cluster-identifiersample-cluster-clone
\ --restore-typecopy-on-write
\ --use-latest-restorable-time输出:
{ "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 } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的将数据库集群还原到指定时间。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RestoreDbClusterToPointInTime
。
-
以下代码示例演示了如何使用 restore-db-instance-from-db-snapshot
。
- AWS CLI
-
从数据库快照还原数据库实例
以下
restore-db-instance-from-db-snapshot
示例从指定数据库快照创建数据库实例类为db.t3.small
且名为db7-new-instance
的新数据库实例。从中拍摄快照的源数据库实例使用已弃用的数据库实例类,因此您无法对其进行升级。aws rds restore-db-instance-from-db-snapshot \ --db-instance-identifier
db7-new-instance
\ --db-snapshot-identifierdb7-test-snapshot
\ --db-instance-classdb.t3.small
输出:
{ "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": [] } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的从数据库快照还原。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RestoreDbInstanceFromDbSnapshot
。
-
以下代码示例演示了如何使用 restore-db-instance-from-s3
。
- AWS CLI
-
从 Amazon S3 中的备份还原数据库实例
以下
restore-db-instance-from-s3
示例根据my-backups
S3 存储桶中的现有备份新建一个名为restored-test-instance
的数据库实例。aws rds restore-db-instance-from-s3 \ --db-instance-identifier
restored-test-instance
\ --allocated-storage250
--db-instance-classdb.m4.large
--enginemysql
\ --master
-username master --master-user-passwordsecret99
\ --s3-bucket-namemy-backups
--s3-ingestion-role-arnarn:aws:iam::123456789012:role/my-role
\ --source-enginemysql
--source-engine-version5.6.27
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RestoreDbInstanceFromS3
。
-
以下代码示例演示了如何使用 restore-db-instance-to-point-in-time
。
- AWS CLI
-
示例 1:将数据库实例还原到某个时间点
截至指定的时间,以下
restore-db-instance-to-point-in-time
示例会将test-instance
还原到名为restored-test-instance
的新数据库实例。aws rds restore-db-instance-to-point-in-time \ --source-db-instance-identifier
test-instance
\ --target-db-instancerestored-test-instance
\ --restore-time2018-07-30T23:45:00.000Z
输出:
{ "DBInstance": { "AllocatedStorage": 20, "DBInstanceArn": "arn:aws:rds:us-east-1:123456789012:db:restored-test-instance", "DBInstanceStatus": "creating", "DBInstanceIdentifier": "restored-test-instance", ...some output omitted... } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的将数据库实例还原到指定时间。
示例 2:将数据库实例从复制备份还原到指定时间
以下
restore-db-instance-to-point-in-time
示例从复制的自动备份将 Oracle 数据库实例恢复到指定时间。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-identifiermyorclinstance-from-replicated-backup
\ --restore-time2020-12-08T18:45:00.000Z
输出:
{ "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": [] } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的从复制备份还原到指定时间。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 RestoreDbInstanceToPointInTime
。
-
以下代码示例演示了如何使用 start-activity-stream
。
- AWS CLI
-
启动数据库活动流
以下
start-activity-stream
示例启动异步活动流来监控名为 my-pg-cluster 的 Aurora 集群。aws rds start-activity-stream \ --region
us-east-1
\ --modeasync
\ --kms-key-idarn:aws:kms:us-east-1:1234567890123:key/a12c345d-6ef7-890g-h123-456i789jk0l1
\ --resource-arnarn:aws:rds:us-east-1:1234567890123:cluster:my-pg-cluster
\ --apply-immediately输出:
{ "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 }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的启动数据库活动流。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 StartActivityStream
。
-
以下代码示例演示了如何使用 start-db-cluster
。
- AWS CLI
-
启动数据库集群
以下
start-db-cluster
示例启动数据库集群及其数据库实例。aws rds start-db-cluster \ --db-cluster-identifier
mydbcluster
输出:
{ "DBCluster": { "AllocatedStorage": 1, "AvailabilityZones": [ "us-east-1a", "us-east-1e", "us-east-1b" ], "BackupRetentionPeriod": 1, "DatabaseName": "mydb", "DBClusterIdentifier": "mydbcluster", ...some output truncated... } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的停止和启动 Amazon Aurora 数据库集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 StartDbCluster
。
-
以下代码示例演示了如何使用 start-db-instance-automated-backups-replication
。
- AWS CLI
-
启用跨区域自动备份
以下
start-db-instance-automated-backups-replication
示例将数据库实例的自动备份从美国东部(弗吉尼亚州北部)地区复制到美国西部(俄勒冈州)地区。备份保留期为 14 天。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-period14
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的启用跨区域自动备份。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 StartDbInstanceAutomatedBackupsReplication
。
-
以下代码示例演示了如何使用 start-db-instance
。
- AWS CLI
-
启动数据库实例
以下
start-db-instance
示例启动了指定的数据库实例。aws rds start-db-instance \ --db-instance-identifier
test-instance
输出:
{ "DBInstance": { "DBInstanceStatus": "starting", ...some output truncated... } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 StartDbInstance
。
-
以下代码示例演示了如何使用 start-export-task
。
- AWS CLI
-
将快照导出到 Amazon S3
以下
start-export-task
示例将名为db5-snapshot-test
的数据库快照导出到名为mybucket
的 Amazon S3 存储桶。aws rds start-export-task \ --export-task-identifier
my-s3-export
\ --source-arnarn:aws:rds:us-west-2:123456789012:snapshot:db5-snapshot-test
\ --s3-bucket-namemybucket
\ --iam-role-arnarn:aws:iam::123456789012:role/service-role/ExportRole
\ --kms-key-idarn:aws:kms:us-west-2:123456789012:key/abcd0000-7fca-4128-82f2-aabbccddeeff
输出:
{ "ExportTaskIdentifier": "my-s3-export", "SourceArn": "arn:aws:rds:us-west-2:123456789012:snapshot:db5-snapshot-test", "SnapshotTime": "2020-03-27T20:48:42.023Z", "S3Bucket": "mybucket", "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 }
有关更多信息,请参阅《Amazon RDS 用户指南》中的将快照导出到 Amazon S3 存储桶。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 StartExportTask
。
-
以下代码示例演示了如何使用 stop-activity-stream
。
- AWS CLI
-
停止数据库活动流
以下
stop-activity-stream
示例停止了名为 my-pg-cluster 的 Aurora 集群中的活动流。aws rds stop-activity-stream \ --region
us-east-1
\ --resource-arnarn:aws:rds:us-east-1:1234567890123:cluster:my-pg-cluster
\ --apply-immediately输出:
{ "KmsKeyId": "arn:aws:kms:us-east-1:1234567890123:key/a12c345d-6ef7-890g-h123-456i789jk0l1", "KinesisStreamName": "aws-rds-das-cluster-0ABCDEFGHI1JKLM2NOPQ3R4S", "Status": "stopping" }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的停止活动流。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 StopActivityStream
。
-
以下代码示例演示了如何使用 stop-db-cluster
。
- AWS CLI
-
停止数据库集群
以下
stop-db-cluster
示例停止了数据库集群及其数据库实例。aws rds stop-db-cluster \ --db-cluster-identifier
mydbcluster
输出:
{ "DBCluster": { "AllocatedStorage": 1, "AvailabilityZones": [ "us-east-1a", "us-east-1e", "us-east-1b" ], "BackupRetentionPeriod": 1, "DatabaseName": "mydb", "DBClusterIdentifier": "mydbcluster", ...some output truncated... } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的停止和启动 Amazon Aurora 数据库集群。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 StopDbCluster
。
-
以下代码示例演示了如何使用 stop-db-instance-automated-backups-replication
。
- AWS CLI
-
停止复制自动备份
以下
stop-db-instance-automated-backups-replication
结束了将自动备份复制到美国西部(俄勒冈州)区域。所复制备份的保留期为设定的备份保留期。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"
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的停止自动备份复制。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 StopDbInstanceAutomatedBackupsReplication
。
-
以下代码示例演示了如何使用 stop-db-instance
。
- AWS CLI
-
停止数据库实例
以下
stop-db-instance
示例停止了指定的数据库实例。aws rds stop-db-instance \ --db-instance-identifier
test-instance
输出:
{ "DBInstance": { "DBInstanceStatus": "stopping", ...some output truncated... } }
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 StopDbInstance
。
-
以下代码示例演示了如何使用 switchover-blue-green-deployment
。
- AWS CLI
-
示例 1:切换 RDS 数据库实例的蓝绿部署
以下
switchover-blue-green-deployment
示例将指定的绿色环境提升为新的生产环境。aws rds switchover-blue-green-deployment \ --blue-green-deployment-identifier
bgd-wi89nwzglccsfake
\ --switchover-timeout300
输出:
{ "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" } }
有关更多信息,请参阅《Amazon RDS 用户指南》中的切换蓝绿部署。
示例 2:为 Aurora MySQL 数据库集群提升蓝绿部署
以下
switchover-blue-green-deployment
示例将指定的绿色环境提升为新的生产环境。aws rds switchover-blue-green-deployment \ --blue-green-deployment-identifier
bgd-wi89nwzglccsfake
\ --switchover-timeout300
输出:
{ "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" } }
有关更多信息,请参阅《Amazon Aurora 用户指南》中的切换蓝绿部署。
-
有关 API 详细信息,请参阅《AWS CLI 命令参考》中的 SwitchoverBlueGreenDeployment
。
-