Cleaning up resources
To avoid incurring unnecessary charges, delete the resources you created after you're done
with the getting started exercise. To delete the resources, use either the Amazon Personalize
console or the Delete
APIs from the SDKs or the AWS Command Line Interface (AWS CLI). For example,
use the DeleteCampaign API to delete
a campaign.
You can't delete a resource whose status is CREATE PENDING or IN PROGRESS. The resource
status must be ACTIVE or CREATE FAILED. Check the status using the Describe
APIs,
for example, DescribeCampaign.
Some resources must be deleted before others, as shown in the following table. This process can take some time.
To delete the training data you uploaded, ratings.csv
, see How do I delete objects from an S3
bucket?.
Cleaning up domain-based resources
If you created a Domain dataset group, delete resources as follows:
Resource to be deleted | Delete this first | Notes |
---|---|---|
Recommender | ||
DatasetImportJob | Can't be deleted. | |
Dataset |
No associated No associated |
|
DatasetSchema | All datasets that reference the schema. | |
DatasetGroup |
All associated recommenders All datasets in the dataset group. |
Cleaning up custom resources
If you created a Custom dataset group, delete resources as follows:
Resource to be deleted | Delete this first | Notes |
---|---|---|
Campaign | ||
DatasetImportJob | Can not be deleted. | |
EventTracker | The event-interactions dataset that is associated with the event tracker is not deleted and continues to be used by the solution version. | |
Dataset |
No associated No associated |
|
DatasetSchema | All datasets that reference the schema. | |
Solution | All campaigns based on the solution version. | No associated SolutionVersion can have a status of CREATE PENDING or
IN PROGRESS. |
SolutionVersion | Deleted when the associated Solution is deleted. |
|
DatasetGroup |
All associated event trackers. All associated solutions. All datasets in the dataset group. |