unfortunately I couldn't find any workaround to force v2 auth.
The problem has another step here. V4 would probably work just as well as V2 with your S3 implementation but doesn't because of the broken region setting. So for the S3 CLI client, both auth mechanism work fine because it has the right region set, but ES is broken because it's hard set to us-east-1.