search

aws-solutions / aws-crr-monitor

A solution for near real-time monitoring of replication of objects in Amazon S3 between a source bucket and a destination bucket across multiple regions.
https://aws.amazon.com/solutions/cross-region-replication-monitor
Apache License 2.0
39 stars 16 forks source link

Lambda failing: Specify a valid number of DataResources.Values (0 to 250) for all your selectors #7

Open jonjohnston opened 5 years ago

jonjohnston commented 5 years ago

Also have a support case open. 6300204691

Need some suggestions on how to avoid the 250 value limit for the 'PutEventSelectors' API call.

Looking at some of the documentation for CloudTrail and that error message I think the easiest solution would be to modify the trail being created to track all s3 buckets as the 250 limit doesn't apply when we specify all s3 buckets then. I think it would be less than creating arrays and such. Can you let me know if this sounds like a viable workaround while I try to produce an example to follow?

mobri2a commented 4 years ago

Originally I wrote CRR Monitor to watch all buckets. I decided to go to a match per bucket so as to limit the number of events hitting the CRRMonitor agent lambda. But with 250 buckets I think you've reached the tipping point. Yes, this is a viable workaround. Perhaps the solution template should have a "watch all buckets" option.