The v1 scanner (phases 1-3) triggered some abuse reports with AWS that prompted the need to add a user-agent to help identify the traffic to agencies monitoring their traffic.
It doesn't appear that the v2 scanner will face the same issues, for a few reasons (running straight out of chrome, and only doing ~4 hits instead of ~25-30/day, so we don't feel the need to add a user agent to v2 for now. It may still be a good idea that we should return to at some point.
The v1 scanner (phases 1-3) triggered some abuse reports with AWS that prompted the need to add a user-agent to help identify the traffic to agencies monitoring their traffic.
It doesn't appear that the v2 scanner will face the same issues, for a few reasons (running straight out of chrome, and only doing ~4 hits instead of ~25-30/day, so we don't feel the need to add a user agent to v2 for now. It may still be a good idea that we should return to at some point.