Troubleshooting DB issues for Amazon RDS Custom for SQL Server

SP-S0000

Manual Unsupported Configuration

The RDS Custom DB instance status is set to [Unsupported configuration] because of: X.

To resolve this issue, create a support case.

SP-S1001

EC2 Instance State

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The underlying EC2 instance %s has been stopped without stopping the RDS instance. You can resolve this by starting the underlying EC2 instance and ensuring that the binary and data volumes are attached. If your intention is to stop the RDS instance, make sure that underlying EC2 instance is in the AVAILABLE state first and then use the RDS console or CLI to stop the RDS instance.

To check the status of a DB instance, use the console or run the following Amazon CLI command:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep DBInstanceStatus
                        

SP-S1002

EC2 Instance State

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The RDS DB instance status is set to STOPPED but the underlying EC2 instance %s has been started. You can resolve this by stopping the underlying EC2 instance. If your intention is to start the RDS instance, use the console or CLI.

Use the following Amazon CLI command to check the status of a DB instance:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep DBInstanceStatus

You can also check the status of the EC2 instance using the EC2 console.

To start a DB instance, use the console or run the following Amazon CLI command:

aws rds start-db-instance \
--db-instance-identifier db-instance-name

SP-S1003

EC2 Instance Class

The RDS Custom DB instance status is set to [Unsupported configuration] because of: There is a mismatch between the expected and configured DB instance class of the EC2 host. You can resolve this by modifying the DB instance class to its original class type.

Use the following CLI command to check the expected DB instance class:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep DBInstanceClass

SP-S1004

EBS Storage Volume Not Accessible

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The original EBS storage volume %s that was associated with the EC2 instance is currently not accessible.

SP-S1005

EBS Storage Volume Detached

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The original EBS storage volume "volume-id" isn’t attached. You can resolve this by attaching the EBS volume associated to the EC2 instance.

After re-attaching the EBS volume, use the following CLI commands to check if the EBS volume 'volume-id' is properly attached to the RDS instance:

aws ec2 describe-volumes \
--volume-ids volume-id |grep InstanceId

SP-S1006

EBS Storage Volume Size

The RDS Custom DB instance status is set to [Unsupported configuration] because of: There is a mismatch between the expected and configured settings of EBS storage volume "volume-id". The volume size has been changed manually at EC2 level from its original value(s) of [%s]. To resolve this issue, create a support case.

Use the following CLI command to compare the volume size of the EBS volume 'volume-id' details and the RDS instance details:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep AllocatedStorage

Use the following CLI command to view the actual allocated volume size:

aws ec2 describe-volumes \
--volume-ids |grep Size

SP-S1007

EBS Storage Volume Configuration

The RDS Custom DB instance status is set to [Unsupported configuration] because of: There is a mismatch between the expected and configured settings of EBS storage volume "volume-id". You can resolve this by modifying the EBS storage volume configuration [IOPS, Throughput, Volume type] to its original value(s) of [IOPS: %s, Throughput: %s, Volume type: %s] at the EC2 level. For future storage modifications, use the RDS console or CLI. The volume size has also been changed manually at EC2 level from its original value(s) of [%s]. To resolve this issue, create a support case.

Use the following CLI command to compare the volume type of the EBS volume 'volume-id' details and the RDS instance details. Make sure that the values at the EBS level matches the values at the RDS level:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep StorageType

To get the expected value for Storage Throughput at the RDS level:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep StorageThroughput

To get the expected value for Volume IOPS at the RDS level:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep Iops

To get the current Storage Type at the EC2 Level:

aws ec2 describe-volumes \
--volume-ids |grep VolumeType

To get the current value for Storage Throughput at the EC2 Level:

aws ec2 describe-volumes \
--volume-ids |grep Throughput

To get the current value for Volume IOPS at the EC2 Level:

aws ec2 describe-volumes \
--volume-ids |grep Iops

SP-S1008

EBS Storage Volume Size and Configuration

The RDS Custom DB instance status is set to [Unsupported configuration] because of: There is a mismatch between the expected and configured settings of EBS storage volume "volume-id". You can resolve this by modifying the EBS storage volume configuration [IOPS, Throughput, Volume type] to its original value(s) of [IOPS: %s, Throughput: %s, Volume type: %s] at the EC2 level. For future storage modifications, use the RDS console or CLI. The volume size has also been changed manually at EC2 level from its original value(s) of [%s]. To resolve this issue, create a support case.

Use the following CLI command to compare the volume type of the EBS volume 'volume-id' details and the RDS instance details. Make sure that the values at the EBS level matches the values at the RDS level:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep StorageType

To get the expected value for Storage Throughput at the RDS level:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep StorageThroughput

To get the expected value for Volume IOPS at the RDS level:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep Iops

To get the current Storage Type at the EC2 Level:

aws ec2 describe-volumes \
--volume-ids |grep VolumeType

To get the current value for Storage Throughput at the EC2 Level:

aws ec2 describe-volumes \
--volume-ids |grep Throughput

To get the current value for Volume IOPS at the EC2 Level:

aws ec2 describe-volumes \
--volume-ids |grep Iops

To get the expected Allocated Volume Size:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep AllocatedStorage

To get the actual Allocated Volume Size:

aws ec2 describe-volumes \
--volume-ids |grep Size

SP-S1009

SQS Permissions

The RDS Custom DB instance status is set to [Unsupported configuration] because of: Amazon Simple Queue Service (SQS) permissions are missing for the IAM instance profile. You can resolve this by making sure the IAM profile associated with the host has the following permissions: ["SQS:SendMessage","SQS:ReceiveMessage","SQS:DeleteMessage","SQS:GetQueueUrl"].

SP-S1010

SQS VPC Endpoint

The RDS Custom DB instance status is set to [Unsupported configuration] because of: A VPC endpoint policy is blocking the Amazon Simple Queue Service (SQS) operations. You can resolve this by modifying your VPC endpoint policy to allow the required SQS actions.

SP-S2001

SQL Service Status

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The SQL Server service isn’t started. You can resolve this by restarting the SQL Server service on the host. If this DB instance is a Multi-AZ DB instance and restart fails, then stop and start the host to initiate a failover.

SP-S2002

RDS Custom Agent Status

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The RDS Custom Agent service isn’t installed or couldn’t be started. You can resolve this by reviewing the Windows Event Log to determine why the service won’t start, and take appropriate steps to fix the issue. For additional assistance, create a support case.

Log in to the host and make sure that the RDS Custom agent is running.

You can use the following commands to view the agent status.

$name = "RDSCustomAgent"
$service = Get-Service $name
Write-Host $service.Status

If the status isn't Running, you can start the service with the following command:

Start-Service $name

If the agent can't start, check the Windows Events to see why it can't start. The agent requires a Windows user to start the service. Ensure a Windows user exists and has privileges to run the service.

SP-S2003

SSM Agent Status

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The Amazon SSM Agent service is unreachable. You can troubleshoot this by checking the service status with the Get-Service AmazonSSMAgent PowerShell command, or starting the service with Start-Service AmazonSSMAgent. Ensure that HTTPS (port 443) outbound traffic to the ssm, ssmmessages, and ec2messages regional endpoints is allowed.

For more information, see Troubleshooting SSM Agent.

To troubleshoot SSM endpoints, see Unable to connect to SSM endpoints and Use ssm-cli to troubleshoot managed node availability.

SP-S2004

RDS Custom Agent Login

SP-S2004 The RDS Custom DB instance status is set to [Unsupported configuration] because of: An unexpected issue occurred with the SQL login "$HOSTNAME/RDSAgent”. To resolve this issue, create a support case.

SP-S2005

Timezone

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The timezone on the Amazon EC2 Instance [%s] was changed. You can resolve this by modifying the time zone back to the setting specified during instance creation. If you would like to create an instance with a specific timezone, see the RDS Custom documentation.

Run the Get-Timezone PowerShell command to confirm the timezone.

For more information, see Local time zone for RDS Custom for SQL Server DB instances.

SP-S2006

High Availability Software Solution Version

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The high availability software solution of the current instance is different from the expected version. To resolve this issue, create a support case.

SP-S2007

High Availability Software Solution Configuration

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The configuration settings of the high availability software solution have been modified to unexpected values on the instance %s. To fix this issue, reboot the EC2 instance. When you reboot the EC2 instance, it automatically updates the settings to the required configuration for the high availability software solution.

SP-S3001

SQL Server Shared Memory Protocol

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The SQL Server shared memory protocol is disabled. You can resolve this by enabling the shared memory protocol in SQL Server Configuration Manager.

You can validate this by checking: SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for MSSQLSERVER> Shared Memory as Enabled. After you enable the protocol, restart the SQL Server process.

SP-S3002

Service Master Key

The RDS Custom DB instance status is set to [Unsupported configuration] because of: RDS Automation is unable to take the backup of Service Master Key (SMK) as part of the new SMK generation. To resolve this issue, create a support case.

SP-S3003

Service Master Key

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The metadata related to the Service Master Key (SMK) is missing or incomplete. To resolve this issue, create a support case.

SP-S3004

DB Engine Version and Edition

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The current SQL Server edition and version doesn't match with the expected SQL Server edition: [%s] and version: [%s]. You can resolve this by making sure that the current SQL Server version and edition matches what you specified during the creation or last modification of the DB instance.

Run the following query to get the SQL version:

select @@version

Run the following Amazon CLI command to get the RDS SQL engine version:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep Engine

SP-S3005

DB Engine Edition

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The current SQL Server edition doesn't match with the expected SQL Server edition: [%s]. You can resolve this by making sure that the current SQL Server Edition matches what you specified during the instance creation.

Run the following query to get the SQL edition:

select @@version

Run the following Amazon CLI command to get the RDS SQL engine edition:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep Engine

SP-S3006

DB Engine Version

The RDS Custom DB instance status is set to [Unsupported configuration] because of: The current SQL Server version doesn't match with the expected SQL Server version: %s. You can resolve this by making sure that the current SQL Server version matches what you specified during the creation or last modification of the DB instance. For further assistance, create a support case.

Run the following query to get the SQL version:

select @@version

Run the following Amazon CLI command to get the RDS SQL engine version:

aws rds describe-db-instances \
--db-instance-identifier db-instance-name |grep EngineVersion

SP-S3007

Database file location

The RDS Custom DB instance status is set to [Unsupported configuration] because of: Database files are configured outside of the D:\ drive. You can resolve this by making sure that all database files, including ROW, LOG, FILESTREAM, etc... are stored on the D:\ drive.

Run the following query to list the location of database files that aren't in the default path:

USE master;
SELECT physical_name as  files_not_in_default_path
FROM sys.master_files
WHERE SUBSTRING(physical_name,1,3)!='D:\';