For 'account' I actually had to use the value '\<org\>-\<account\>' in configuration. This paged proved useful:
https://docs.snowflake.com/en/user-guide/admin-account-identifier.html
In short, there are two values I needed: 'org' and 'account'. There is a 'locator' identifier that is deprecated but still visible in the UI at the time of this writing.
As for `snowsql` CLI, I had to do the same, but in addition set region to 'us-west-2' (even though my Snowflake instance is in 'us-east-2'!) to satisfy SSL certificate checks. The CLI then successfully connected using the correct domain of '\<account\>.us-east-2.aws.snowflakecomputing.com'.
Snowsql version: 1.2.23

For 'account' I actually had to use the value '\<org\>-\<account\>' in configuration. This paged proved useful:
https://docs.snowflake.com/en/user-guide/admin-account-identifier.html
In short, there are two values I needed: 'org' and 'account'. There is a 'locator' identifier that is deprecated but still visible in the UI at the time of this writing.
As for `snowsql` CLI, I had to do the same, but in addition set region to 'us-west-2' (even though my Snowflake instance is in 'us-east-2'!) to satisfy SSL certificate checks. The CLI then successfully connected using the correct domain of '\<account\>.us-east-2.aws.snowflakecomputing.com'.
Snowsql version: 1.2.23