ServiceGraph Connector for AWS Does Not Retire Cloud Storage and Cloud Database CIsIssue The functional specification for the Service Graph connector for AWSunder deletion says "We will identify the resource as deleted and perform the operation based on the hardware or software type."The Service Graph connector for AWS sets the Install Status for EC2 instances to Retired when they are deleted in AWSCauseThe data source was not run within 3 days of resource deletion, hence the CI was not marking the resource status as Absent.ResolutionThe number of days the deleted resources to consider for marking Absent / Retired. ListDiscoveredResources "resourceDeletionTime" returns a unix timestamp number when the resource got deleted.https://docs.aws.amazon.com/config/latest/APIReference/API_ListDiscoveredResources.html System Property -> sn_aws_integ.delete_resource_timelineValue -> 3 (Default) The above system property sn_aws_integ.delete_resource_timeline can be customised by setting the value as required to sync the CI status in CMDB and mark the resource as 'Absent' Related LinksAdditionally, the REST API can be executed manually in Postman to check if the resources are listed as deleted and view the response payload if the resource is deleted.(Document reference: https://docs.aws.amazon.com/config/latest/APIReference/API_ListDiscoveredResources.html) Service Graph Connector for AWS - Diagnostic Tool & Troubleshooting Issues https://www.servicenow.com/community/cmdb-articles/service-graph-connector-for-aws-diagnostic-tool-troubleshooting/ta-p/2300683 1. Does the diagnostic tool show access to ListDiscovered Resources API access as 200 for the account where the S3 bucket is present? 2. If Yes, is the deleted resource displayed as shown in the attachment? Until we see the resource is deleted, we cannot get that info into CMDB. As a CMDB rule, based on resource types we mark it as Retired / Absent. For S3, we will be marking it as Absent.