Tables to be Preserved for SG-AWS During CloneIssue Customers using SG-AWS are experiencing issues after cloning when the appropriate tables are not preserved - resulting in loss of integration or configuration. Please follow the approach suggested here to ensure the setup is retained by preserving the required tables during the clone process.ReleaseAllResolutionPlease ensure the following tables are preserved during the cloning process for SG-AWS to avoid impacting the existing setup: sys_aliashttp_connectionaws_credentialsscheduled_import_setsys_data_sourcesn_cmdb_int_util_service_graph_connectionsn_cmdb_int_util_service_graph_connection_propertysn_cmdb_int_util_service_graph_connection_data_sourcesn_cmdb_int_util_service_graph_connection_scheduled_data_importsn_sgc_central_service_graph_connection_triggersn_sgc_central_installed_connections[optional]import_logsn_aws_integ_sg_aws_diagnostic_summary_notessn_aws_integ_sg_aws_diagnostic_summarysn_aws_integ_sg_aws_eks_ec2_resourcesn_cmdb_int_util_cmdb_integration_executionsn_cmdb_int_util_cmdb_integration_execution_import_setsn_cmdb_int_util_cmdb_integration_execution_errorsn_cmdb_int_util_cmdb_integration_execution_auditsys_execution_contextsys_import_setsys_import_set_runsys_import_set_executionsys_parallel_jobsys_concurrent_import_setsys_concurrent_import_set_jobsys_pd_contextsys_pd_activity_context Please make sure these tables are excluded from the cloning process to retain the existing SG-AWS configuration.