AWS Amazon RDS Error Codes

The specified CIDR IP range or Amazon EC2 security group is already authorized for the specified DB security group.

The specified CIDR IP range or Amazon EC2 security group might not be authorized for the specified DB security group. Or, RDS might not be authorized to perform necessary actions using IAM on your behalf.

The DB security group authorization quota has been reached.

A blue/green deployment with the specified name already exists.

BlueGreenDeploymentIdentifier doesn't refer to an existing blue/green deployment.

CertificateIdentifier doesn't refer to an existing certificate.

An error occurred while trying to create the CEV.

CustomAvailabilityZoneId doesn't refer to an existing custom Availability Zone identifier.

A CEV with the specified name already exists.

The specified CEV was not found.

You have exceeded your CEV quota.

The user already has a DB cluster with the given identifier.

No automated backup for this DB cluster was found.

The quota for retained automated backups was exceeded. This prevents you from retaining any additional automated backups. The retained automated backups quota is the same as your DB cluster quota.

BacktrackIdentifier doesn't refer to an existing backtrack.

The specified custom endpoint can't be created because it already exists.

The specified custom endpoint doesn't exist.

The cluster already has the maximum number of custom endpoints.

DBClusterIdentifier doesn't refer to an existing DB cluster.

DBClusterParameterGroupName doesn't refer to an existing DB cluster parameter group.

The user attempted to create a new DB cluster and the user has already reached the maximum allowed DB cluster quota.

The specified IAM role Amazon Resource Name (ARN) is already associated with the specified DB cluster.

The specified IAM role Amazon Resource Name (ARN) isn't associated with the specified DB cluster.

You have exceeded the maximum number of IAM roles that can be associated with the specified DB cluster.

The user already has a DB cluster snapshot with the given identifier.

DBClusterSnapshotIdentifier doesn't refer to an existing DB cluster snapshot.

The user already has a DB instance with the given identifier.

No automated backup for this DB instance was found.

The quota for retained automated backups was exceeded. This prevents you from retaining any additional automated backups. The retained automated backups quota is the same as your DB instance quota.

DBInstanceIdentifier doesn't refer to an existing DB instance.

An attempt to download or examine log files didn't succeed because an Aurora Serverless v2 instance was paused.

The specified RoleArn or FeatureName value is already associated with the DB instance.

The specified RoleArn value doesn't match the specified feature for the DB instance.

You can't associate any more Amazon Web Services Identity and Access Management (IAM) roles with the DB instance because the quota has been reached.

LogFileName doesn't refer to an existing DB log file.

A DB parameter group with the same name exists.

DBParameterGroupName doesn't refer to an existing DB parameter group.

The request would result in the user exceeding the allowed number of DB parameter groups.

The specified proxy name must be unique for all proxies owned by your Amazon Web Services account in the specified Amazon Web Services Region.

The specified DB proxy endpoint name must be unique for all DB proxy endpoints owned by your Amazon Web Services account in the specified Amazon Web Services Region.

The DB proxy endpoint doesn't exist.

The DB proxy already has the maximum number of endpoints.

The specified proxy name doesn't correspond to a proxy owned by your Amazon Web Services account in the specified Amazon Web Services Region.

Your Amazon Web Services account already has the maximum number of proxies in the specified Amazon Web Services Region.

The proxy is already associated with the specified RDS DB instance or Aurora DB cluster.

The specified target group isn't available for a proxy owned by your Amazon Web Services account in the specified Amazon Web Services Region.

The specified RDS DB instance or Aurora DB cluster isn't available for a proxy owned by your Amazon Web Services account in the specified Amazon Web Services Region.

A DB security group with the name specified in DBSecurityGroupName already exists.

DBSecurityGroupName doesn't refer to an existing DB security group.

A DB security group isn't allowed for this action.

The request would result in the user exceeding the allowed number of DB security groups.

The specified DB shard group name must be unique in your Amazon Web Services account in the specified Amazon Web Services Region.

The specified DB shard group name wasn't found.

DBSnapshotIdentifier is already used by an existing snapshot.

DBSnapshotIdentifier doesn't refer to an existing DB snapshot.

The specified snapshot tenant database wasn't found.

DBSubnetGroupName is already used by an existing DB subnet group.

Subnets in the DB subnet group should cover at least two Availability Zones unless there is only one Availability Zone.

The DBSubnetGroup shouldn't be specified while creating read replicas that lie in the same region as the source instance.

DBSubnetGroupName doesn't refer to an existing DB subnet group.

The request would result in the user exceeding the allowed number of DB subnet groups.

The request would result in the user exceeding the allowed number of subnets in a DB subnet groups.

The DB upgrade failed because a resource the DB depends on can't be modified.

Domain doesn't refer to an existing Active Directory domain.

The AMI configuration prerequisite has not been met.

You have reached the maximum number of event subscriptions.

You can't start an export task that's already running.

The export task doesn't exist.

The GlobalClusterIdentifier already exists. Specify a new global database identifier (unique name) to create a new global database cluster or to rename an existing one.

The GlobalClusterIdentifier doesn't refer to an existing global database cluster.

The number of global database clusters for this account is already at the maximum allowed.

The IAM role requires additional permissions to export to an Amazon S3 bucket.

The IAM role is missing for exporting to an Amazon S3 bucket.

The request would result in the user exceeding the allowed number of DB instances.

The requested operation can't be performed because there aren't enough available IP addresses in the proxy's subnets. Add more CIDR blocks to the VPC or remove IP address that aren't required from the subnets.

The DB cluster doesn't have enough capacity for the current operation.

The specified DB instance class isn't available in the specified Availability Zone.

There is insufficient storage available for the current action. You might be able to resolve this error by updating your subnet group to use different Availability Zones that have more storage available.

The integration you are trying to create already exists.

A conflicting conditional operation is currently in progress against this resource. Typically occurs when there are multiple requests being made to the same resource at the same time, and these requests conflict with each other.

The specified integration could not be found.

You can't crate any more zero-ETL integrations because the quota has been reached.

The blue/green deployment can't be switched over or deleted because there is an invalid configuration in the green environment.

You can't delete the CEV.

The automated backup is in an invalid state. For example, this automated backup is associated with an active cluster.

Capacity isn't a valid Aurora Serverless DB cluster capacity. Valid capacity values are 2, 4, 8, 16, 32, 64, 128, and 256.

The requested operation can't be performed on the endpoint while the endpoint is in this state.

The supplied value isn't a valid DB cluster snapshot state.

The requested operation can't be performed while the cluster is in this state.

The automated backup is in an invalid state. For example, this automated backup is associated with an active instance.

The DB instance isn't in a valid state.

The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you can't delete it when the parameter group is in this state.

You can't perform this operation while the DB proxy endpoint is in a particular state.

The requested operation can't be performed while the proxy is in this state.

The state of the DB security group doesn't allow deletion.

The DB shard group must be in the available state.

The state of the DB snapshot doesn't allow deletion.

The DBSubnetGroup doesn't belong to the same VPC as that of an existing cross-region read replica of the same source instance.

The DB subnet group cannot be deleted because it's in use.

The DB subnet isn't in the available state.

This error can occur if someone else is modifying a subscription. You should retry the action.

The export is invalid for exporting to an Amazon S3 bucket.

The state of the export snapshot is invalid for exporting to an Amazon S3 bucket.

You can't cancel an export task that has completed.

The global cluster is in an invalid state and can't perform the requested operation.

The integration is in an invalid state and can't perform the requested operation.

The option group isn't in the available state.

The operation can't be performed because another operation is in progress.

Cannot restore from VPC backup to non-VPC DB instance.

The specified Amazon S3 bucket name can't be found or Amazon RDS isn't authorized to access the specified Amazon S3 bucket. Verify the SourceS3BucketName and S3IngestionRoleArn values and try again.

The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.

The DB subnet group doesn't cover all Availability Zones after it's created because of users' change.

An error occurred accessing an Amazon Web Services KMS key.

The maximum number of DB shard groups for your Amazon Web Services account in the specified Amazon Web Services Region has been reached.

The network type is invalid for the DB instance. Valid nework type values are IPV4 and DUAL.

The option group you are trying to create already exists.

The specified option group could not be found.

The quota of 20 option groups was exceeded for this Amazon Web Services account.

SourceDBInstanceIdentifier refers to a DB instance with BackupRetentionPeriod equal to 0.

Provisioned IOPS not available in the specified Availability Zone.

User already has a reservation with the given identifier.

The specified reserved DB Instance not found.

Request would exceed the user's DB Instance quota.

Specified offering does not exist.

The specified resource ID was not found.

You have exceeded the maximum number of accounts that you can share a manual DB snapshot with.

The request would result in the user exceeding the allowed number of DB snapshots.

SNS has responded that there is a problem with the SNS topic specified.

You do not have permission to publish to the SNS topic ARN.

The SNS topic ARN does not exist.

The source DB cluster isn't supported for a blue/green deployment.

The source DB instance isn't supported for a blue/green deployment.

The requested source could not be found.

The request would result in the user exceeding the allowed amount of storage available across all DB instances.

The aurora-iopt1 storage type isn't available, because you modified the DB cluster to use this storage type less than one month ago.

The specified StorageType can't be associated with the DB instance.

The DB subnet is already in use in the Availability Zone.

The supplied subscription name already exists.

The supplied category does not exist.

The subscription name does not exist.

You attempted to either create a tenant database that already exists or modify a tenant database to use the name of an existing tenant database.

The specified tenant database wasn't found in the DB instance.

You attempted to create more tenant databases than are permitted in your Amazon Web Services account.

The specified DB engine version isn't supported for Aurora Limitless Database.

The operation violates VPC encryption control settings. Make sure that your DB instance type supports the Nitro encryption-in-transit capability, or modify your VPC's encryption controls to not enforce encryption-in-transit.