1 Answer
- Newest
- Most votes
- Most comments
0
Hello!
Ive looked into the issue you are having and understand that you are having a problem with the Config Rule Evaluation limit. Although the limit of 100 resource evaluations for a Custom Rule cannot be increased, the workaround would be to split the resource array into multiple PutEvaluations API calls. You can reuse the same ResultToken from the Lambda execution.
Since you are getting an InvalidResultTokenException, I would also suggest to check if the ResultToken is parsed correctly in your code and if it is being used in the correct region, account, etc. I hope that helps with the issue you are having! I have attached a link below that goes more in depth on request parameters.
answered a year ago
Relevant content
- asked 3 years ago
- asked 2 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago