Class RedshiftException

You are not authorized to access the cluster.

The owner of the specified snapshot has not authorized your account to access the snapshot.

The authentication profile already exists.

The authentication profile can't be found.

The size or number of authentication profiles has exceeded the quota. The maximum length of the JSON string and maximum number of authentication profiles is determined by a quota for your account.

The specified CIDR block or EC2 security group is already authorized for the specified cluster security group.

The specified CIDR IP range or EC2 security group is not authorized for the specified cluster security group.

The authorization quota for the cluster security group has been reached.

The maximum number for a batch delete of snapshots has been reached. The limit is 100.

The maximum number for snapshot identifiers has been reached. The limit is 100.

Could not find the specified S3 bucket.

The account already has a cluster with the given identifier.

The ClusterIdentifier parameter does not refer to an existing cluster.

Cluster is already on the latest database revision.

A cluster parameter group with the same name already exists.

The parameter group name does not refer to an existing parameter group.

The request would result in the user exceeding the allowed number of cluster parameter groups. For information about increasing your quota, go to Limits in Amazon Redshift in the Amazon Redshift Cluster Management Guide.

The request would exceed the allowed number of cluster instances for this account. For information about increasing your quota, go to Limits in Amazon Redshift in the Amazon Redshift Cluster Management Guide.

A cluster security group with the same name already exists.

The cluster security group name does not refer to an existing cluster security group.

The request would result in the user exceeding the allowed number of cluster security groups. For information about increasing your quota, go to Limits in Amazon Redshift in the Amazon Redshift Cluster Management Guide.

The value specified as a snapshot identifier is already used by an existing snapshot.

The snapshot identifier does not refer to an existing cluster snapshot.

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

A ClusterSubnetGroupName is already used by an existing cluster subnet group.

The cluster subnet group name does not refer to an existing cluster subnet group.

The request would result in user exceeding the allowed number of cluster subnet groups. For information about increasing your quota, go to Limits in Amazon Redshift in the Amazon Redshift Cluster Management Guide.

The request would result in user exceeding the allowed number of subnets in a cluster subnet groups. For information about increasing your quota, go to Limits in Amazon Redshift in the Amazon Redshift Cluster Management Guide.

There is a conflict while updating the resource policy.

Cross-region snapshot copy was temporarily disabled. Try your request again.

An error occurred when an attempt was made to change the custom domain association.

An error occurred. The custom domain name couldn't be found.

A dependent service denied access for the integration.

The request cannot be completed because a dependent service is throttling requests made by Amazon Redshift on your behalf. Wait and retry the request.

Your request cannot be completed because a dependent internal service is temporarily unavailable. Wait 30 to 60 seconds and try again.

The account already has a Redshift-managed VPC endpoint with the given identifier.

The authorization already exists for this endpoint.

The authorization for this endpoint can't be found.

The number of endpoint authorizations per cluster has exceeded its limit.

The endpoint name doesn't refer to an existing endpoint.

The number of Redshift-managed VPC endpoints per authorization has exceeded its limit.

The number of Redshift-managed VPC endpoints per cluster has exceeded its limit.

The request would exceed the allowed number of event subscriptions for this account. For information about increasing your quota, go to Limits in Amazon Redshift in the Amazon Redshift Cluster Management Guide.

There is already an existing Amazon Redshift HSM client certificate with the specified identifier.

There is no Amazon Redshift HSM client certificate with the specified identifier.

The quota for HSM client certificates has been reached. For information about increasing your quota, go to Limits in Amazon Redshift in the Amazon Redshift Cluster Management Guide.

There is already an existing Amazon Redshift HSM configuration with the specified identifier.

There is no Amazon Redshift HSM configuration with the specified identifier.

The quota for HSM configurations has been reached. For information about increasing your quota, go to Limits in Amazon Redshift in the Amazon Redshift Cluster Management Guide.

You have exceeded the allowed number of table restore requests. Wait for your current table restore requests to complete before making a new request.

The specified options are incompatible.

The number of nodes specified exceeds the allotted capacity of the cluster.

The cluster does not have read bucket or put object permissions on the S3 bucket specified when enabling logging.

The integration can't be found.

The authentication profile request is not valid. The profile name can't be null or empty. The authentication profile API operation must be available in the Amazon Web Services Region.

The status of the authorization is not valid.

The cluster parameter group action can not be completed because another task is in progress that involves the parameter group. Wait a few moments and try the operation again.

The state of the cluster security group is not available.

The cluster snapshot schedule state is not valid.

The specified cluster snapshot is not in the available state, or other accounts are authorized to access the snapshot.

The specified cluster is not in the available state.

The cluster subnet group cannot be deleted because it is in use.

The state of the subnet is invalid.

The provided cluster track name is not valid.

There is an error with the datashare.

The Elastic IP (EIP) is invalid or cannot be found.

The status of the endpoint is not valid.

The specified HSM client certificate is not in the available state, or it is still in use by one or more Amazon Redshift clusters.

The specified HSM configuration is not in the available state, or it is still in use by one or more Amazon Redshift clusters.

The namespace isn't valid because the namespace doesn't exist. Provide a valid namespace.

The resource policy isn't valid.

Indicates that the Reserved Node being exchanged is not in an active state.

The restore is invalid.

The retention period specified is either in the past or is not a valid value.

The value must be either -1 or an integer between 1 and 3,653.

The S3 bucket name is invalid. For more information about naming rules, go to Bucket Restrictions and Limitations in the Amazon Simple Storage Service (S3) Developer Guide.

The string specified for the logging S3 key prefix does not comply with the documented constraints.

The schedule you submitted isn't valid.

The scheduled action is not valid.

The snapshot copy grant can't be deleted because it is used by one or more clusters.

The requested subnet is not valid, or not all of the subnets are in the same VPC.

The subscription request is invalid because it is a duplicate request. This subscription request is already in progress.

The value specified for the sourceDatabaseName, sourceSchemaName, or sourceTableName parameter, or a combination of these, doesn't exist in the snapshot.

The tag is invalid.

The usage limit is not valid.

The cluster subnet group does not cover all Availability Zones.

There are no subnets in your VPC with associated IPv6 CIDR blocks. To use dual-stack mode, associate an IPv6 CIDR block with each subnet in your VPC.

The encryption key has exceeded its grant limit in Amazon Web Services KMS.

The operation would exceed the number of nodes allowed for a cluster.

The operation would exceed the number of nodes allotted to the account. For information about increasing your quota, go to Limits in Amazon Redshift in the Amazon Redshift Cluster Management Guide.

The name of the partner was not found.

The application you attempted to add already exists.

The application you attempted to find doesn't exist.

The maximum number of Redshift IAM Identity Center applications was exceeded.

User already has a reservation with the given identifier.

Indicates that the reserved node has already been exchanged.

The reserved-node exchange status wasn't found.

The specified reserved compute node not found.

Specified offering does not exist.

Request would exceed the user's compute node quota. For information about increasing your quota, go to Limits in Amazon Redshift in the Amazon Redshift Cluster Management Guide.

A resize operation for the specified cluster is not found.

The resource could not be found.

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

You do not have permission to publish to the specified Amazon SNS topic.

An Amazon SNS topic with the specified Amazon Resource Name (ARN) does not exist.

The definition you submitted is not supported.

The scheduled action already exists.

The scheduled action cannot be found.

The quota for scheduled actions exceeded.

The action type specified for a scheduled action is not supported.

The cluster already has cross-region snapshot copy disabled.

The cluster already has cross-region snapshot copy enabled.

Cross-region snapshot copy was temporarily disabled. Try your request again.

The snapshot copy grant can't be created because a grant with the same name already exists.

The specified snapshot copy grant can't be found. Make sure that the name is typed correctly and that the grant exists in the destination region.

The Amazon Web Services account has exceeded the maximum number of snapshot copy grants in this region.

The specified snapshot schedule already exists.

We could not find the specified snapshot schedule.

You have exceeded the quota of snapshot schedules.

The specified snapshot schedule is already being updated.

The specified Amazon Redshift event source could not be found.

A specified subnet is already in use by another cluster.

There is already an existing event notification subscription with the specified name.

The value specified for the event category was not one of the allowed values, or it specified a category that does not apply to the specified source type. The allowed values are Configuration, Management, Monitoring, and Security.

An Amazon Redshift event with the specified event ID does not exist.

An Amazon Redshift event notification subscription with the specified name does not exist.

The value specified for the event severity was not one of the allowed values, or it specified a severity that does not apply to the specified source type. The allowed values are ERROR and INFO.

The number of tables in the cluster exceeds the limit for the requested new cluster node type.

The specified TableRestoreRequestId value was not found.

You have exceeded the number of tags allowed.

Your account is not authorized to perform the requested operation.

The partner integration is not authorized.

The specified region is incorrect or does not exist.

The requested operation isn't supported.

A request option was specified that is not supported.

The usage limit already exists.

The usage limit identifier can't be found.