# CloudQuery sync slow and failing with aws\_inspector\_findings and aws\_inspector2\_findings tables

**URL:** <https://community.cloudquery.io/t/cloudquery-sync-slow-and-failing-with-aws-inspector-findings-and-aws-inspector2-findings-tables/308>\
**Category:** CloudQuery Plugins\
**Created:** [March 12, 2024, 9:38am UTC](https://community.cloudquery.io/t/cloudquery-sync-slow-and-failing-with-aws-inspector-findings-and-aws-inspector2-findings-tables/308 "2024-03-12T09:38:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![concise-oryx](https://avatars.discourse-cdn.com/v4/letter/c/67e7ee/32.png) [@concise-oryx](https://community.cloudquery.io/u/concise-oryx)\
**Post date:** [March 12, 2024, 9:38am UTC](https://community.cloudquery.io/t/cloudquery-sync-slow-and-failing-with-aws-inspector-findings-and-aws-inspector2-findings-tables/308/1 "2024-03-12T09:38:13Z")

</div>

Using `aws_inspector_findings` and `aws_inspector2_findings` tables in CloudQuery is taking more time to sync for all the accounts in our database, and then failing for some accounts randomly. It is almost running for 7 to 8 hours and failing for some random accounts.

What should we do for these tables? One thing we have observed is that when we skip these two tables, the sync works fine and runs as expected in 2 to 2.5 hours.

How can we overcome this issue?

---

<div class="post-metadata">

**Author:** ![ben](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/ben/32/88_2.png) [@ben](https://community.cloudquery.io/u/ben)\
**Post date:** [March 12, 2024, 12:43pm UTC](https://community.cloudquery.io/t/cloudquery-sync-slow-and-failing-with-aws-inspector-findings-and-aws-inspector2-findings-tables/308/2 "2024-03-12T12:43:35Z")

</div>

The two tables you have highlighted have the potential to have a lot of resources, so the fact that it takes so long is not that surprising. The best way to speed up syncing is to use the `table_option`. This allows you to specify which findings to sync based on the available filters from AWS. More details about this can be found [here](https://hub.cloudquery.io/plugins/source/cloudquery/aws/latest/docs#configuration-configuration-spec).

As for general performance, you can look into splitting your syncs into multiple smaller jobs by following the guidance found [here](https://docs.cloudquery.io/docs/advanced-topics/performance-tuning).

---

<div class="post-metadata">

**Author:** ![concise-oryx](https://avatars.discourse-cdn.com/v4/letter/c/67e7ee/32.png) [@concise-oryx](https://community.cloudquery.io/u/concise-oryx)\
**Post date:** [March 13, 2024, 3:18am UTC](https://community.cloudquery.io/t/cloudquery-sync-slow-and-failing-with-aws-inspector-findings-and-aws-inspector2-findings-tables/308/3 "2024-03-13T03:18:19Z")

</div>

Okay, we will try this and let you know. Thanks for the information.