/api/database/{id} does not work to connect to athena in us-east-1

Bug reports
1

metabase v0.55.1.4

When we hit the below API through metabase image deployed in AWS ECS container, it connects to AWS athena in all other regions except us-east-1.

curl --location --request PUT 'https://metabase.de.prod.dataplatform.mimecast.lan/api/database/12' \
--header 'X-Metabase-Session: 258d3ade-3ae8-431b-a2c7-c5e3855db34c' \
--header 'Content-Type: application/json' \
--header 'Cookie: metabase.DEVICE=b4815617-fe34-4e70-ac16-5a921376bbe7' \
--data '{
        "name" : "athena-us-east-1",
        "engine": "athena",
        "is_fully_sync": true,
        "details" : {
            "additional-options": "RowsToFetchPerBlock=10000000;EnableResultReuse=1;UseResultsetStreaming=1;UseMultipleS3Threads=40;S3ResultBlockSize=2146435072",
            "s3_staging_dir": "s3://082394382481-us-east-1-us-metabase-athena/athena",
            "advanced-options": true,
            "region": "us-east-1",
            "workgroup": "metabase-prod",
            "catalog" : null
        }
    } '

In us-east-1 we get an exception as shown below:

{
    "message": "Connection test failed: Query execution failed: Could not load query result metadata from \"s3://082394382481-us-east-1-us-metabase-athena/athena/b589e2f1-10f5-41f8-8593-d5112a78efd9.csv.metadata\": software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: The connection was closed during the request. The request will usually succeed on a retry, but if it does not: consider disabling any proxies you have configured, enabling debug logging, or performing a TCP dump to identify the root cause. If this is a streaming operation, validate that data is being read or written in a timely manner. Channel Information: ChannelDiagnostics(channel=[id: 0x442e343b, L:/100.80.116.210:40794 ! R:082394382481-us-east-1-us-metabase-athena.s3.amazonaws.com/3.5.25.223:443], channelAge=PT0.191127601S, requestCount=1, responseCount=0, lastIdleDuration=PT0.000076427S)"
}

Underlying reason for the above exception is

{
    "message": "Could not connect: Invalid connection parameter(s): Invalid fetch size: \"100000000\" (expected an integer between 0 and 1000000); Invalid fetch size: \"100000000\" (expected an integer between 0 and 1000000);"
}

Weird thing is the request works with RowsToFetchPerBlock=10000000(7 zeroes) and does not work with RowsToFetchPerBlock=1000000(6 zeroes) which is error message asked us to do. And this happens only in athena deployed in us-east-1.