I have two questions about event-based sync with the AWS source plugin.
I read the section on the AWS plugin documentation page but haven’t begun looking into the CloudFormation and Kinesis parts yet. Is the CloudQuery container routinely polling the Kinesis stream, or is Kinesis pushing data to CloudQuery?
What impact does this have on _cq_sync_time? We key off of that for some TTL indexes in our database to only keep a few months of stale records.
We use _cq_sync_time to see when a resource was last seen by CloudQuery. If the process is long-lived, then it becomes less useful for us as an approximation of the last-seen time. I guess we might have to rethink what we are doing with that.
@ben I was looking on the documentation for more information on pricing for event sync since it’s a premium feature, but the pricing page only mentions “Pay as You Go” and “Support” plans. Do you know where I could find this info?
Appreciate you opening that issue! As for premium features, if you have any indication about the type of pricing model you’re thinking about, that would be helpful. We are in discussions to make use of event-based sync but don’t want to commit if it’s something we couldn’t afford for the whole org.
Hi @dominant-worm - Happy to walk you through our pricing structure and answer any questions you might have. Here’s a link to my calendar if you’d like to set up a quick call: https://calendly.com/josh-cloudquery