AWS IoT FleetWise will no longer be open to new customers as of April 30, 2026. Existing AWS IoT FleetWise customers can continue using the service. The [Guidance for Connected Mobility on AWS](https://aws.amazon.com/solutions/guidance/connected-mobility-on-aws/) provides guidance on how to develop and deploy modular services for connected mobility solutions that can be used to achieve equivalent capabilities as AWS IoT FleetWise.

# Delete an AWS IoT FleetWise signal catalog
<a name="delete-signal-catalog"></a>

You can use the [DeleteSignalCatalog](https://docs.aws.amazon.com/iot-fleetwise/latest/APIReference/API_DeleteSignalCatalog.html) API operation to delete a signal catalog. The following example uses AWS CLI.

**Important**  
Before deleting a signal catalog, make sure it has no associated vehicle models, decoder manifests, vehicles, fleets, or campaigns. For instructions, see the following:  
[Delete an AWS IoT FleetWise vehicle model](delete-vehicle-model.md)
[Delete an AWS IoT FleetWise decoder manifest](delete-decoder-manifest.md)
[Delete an AWS IoT FleetWise vehicle](delete-vehicle.md)
[Delete an AWS IoT FleetWise fleet](delete-fleet-cli.md)
[Delete an AWS IoT FleetWise campaign](delete-campaign.md)

To delete an existing signal catalog, run the following command. Replace *signal-catalog-name* with the name of the signal catalog that you're deleting.

```
aws iotfleetwise delete-signal-catalog --name signal-catalog-name
```

## Verify signal catalog deletion
<a name="verify-catalog-update"></a>

You can use the [ListSignalCatalogs](https://docs.aws.amazon.com/iot-fleetwise/latest/APIReference/API_ListSignalCatalogs.html) API operation to verify if a signal catalog has been deleted. The following example uses AWS CLI.

To retrieve a paginated list of summaries of all signal catalogs, run the following command.

```
aws iotfleetwise list-signal-catalogs
```

If you [enabled encryption](key-management.md) using a customer managed AWS KMS key, include the following policy statement so that your role can invoke the `ListSignalCatalogs` API operation. 

------
#### [ JSON ]

****  

```
{
    "Version":"2012-10-17",		 	 	 
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "kms:Decrypt"
            ],
            "Resource": [
                "arn:aws:kms:us-east-1:111122223333:key/KMS_KEY_ID"
            ]
        }
    ]
}
```

------