Difference between revisions of "InvalidDBSubnetGroupStateFault"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
== Related == | == Related == | ||
* <code>[[aws rds describe-db-instances]]</code> | * <code>[[aws rds describe-db-instances]]</code> | ||
| + | * <code>[[aws rds delete-db-instance --db-instance-identifier]]</code> | ||
== See also == | == See also == | ||
Latest revision as of 22:32, 5 June 2022
╷ │ Error: deleting RDS Subnet Group (complete-postgresql): InvalidDBSubnetGroupStateFault: Cannot delete the subnet group 'complete-postgresql' because at least one database instance: complete-postgresql-default is still using it. │ status code: 400, request id: de6a2058-a025-4560-8272-7bdbbf56ece7 │ │ ╵
Related[edit]
See also[edit]
- Amazon databases: AWS RDS, storage,
aws rds, Amazon RDS Proxy, RDS FAQs, PostgreSQL, MySQL, SQL Server, AWS Outposts, Amazon Aurora, Amazon Aurora Serverless , Amazon DocumentDB, Amazon DynamoDB, Amazon Redshift, Amazon QLDB, Amazon RDS Performance Insights, DataFileRead, DMS, Amazon Neptune, Amazon MemoryDB for Redis, Amazon RDS query editor for Aurora Serverless, Amazon Redshift query editor, AWS RDS Snapshots, AWS RDS Instance Types,rds_superuser, Authentication, autoscaling
Advertising:
