What should the SysOps administrator do to stop the loop without errors?
Delete all the objects from the S3 bucket.
Set the function’s reserved concurrency to 0.
Update the S3 bucket policy to deny access for the function.
Publish a new version of the function.
Explanations:
Deleting objects may stop the loop temporarily but will not prevent future recursive invocations if new objects are added. It is not a reliable or immediate solution to stop recursive invocations.
Setting the function’s reserved concurrency to 0 immediately prevents any invocations of the function, effectively stopping the recursive loop without affecting other configurations.
Updating the bucket policy to deny access may take time to propagate and could cause unintended access issues. It is not the most immediate or effective way to stop the invocations.
Publishing a new version does not stop the existing version’s invocations. It only creates an additional version, which would not prevent the recursive loop from running on the original version.
I calculate that the answer is:
Set the function’s reserved concurrency to 0.
To the best of my knowledge, the answer is:
Set the function’s reserved concurrency to 0.