Same results with Safari.
I’ll have to have somebody else on my team sign up for this, heh.
Alright, I think we got to the bottom of it. It’s a new Firebase feature. We disabled it. Potentially it marked you as a bot 
Sorry. Can you try again one last time? (It might take 15 minutes for this to go into effect - sorry for this.)
Cool! I’ll give it a try in a bit, thank you.
Okay, I managed to create an account! Thank you!
Awesome! Phew, ok we disabled this Firebase feature until we dig deeper into why it classified you as a bot and if we can get some alerting and manual intervention with this.
@pure-quetzal, any progress on testing?
Any updates?
I think you can verify with the objects that are already in the bucket (no need to wait till the last resource is synced).
Trying to verify, having difficulty I have reason to believe it is working but I will confirm when I am able.
Yes! It is working!!! Thank you!
OK, I’ll make a release then.
We’ve decided to mark the fix breaking as some users could’ve been working around this bug by performing base64 decoding.
So, it’ll be v5.0.0.
It’ll appear on the hub soon.
JFYI: https://hub.cloudquery.io/plugins/destination/cloudquery/s3/latest/docs (v5.0.0 was released yesterday)
Thank you so much, team! 
Regarding athena compatibility in the S3 destination – is the expectation with the JSON key substitutions that are performed that when crawled with Glue, will result in some sort of map type for the column?
It will be a valid JSON (it can be an array for sure).
The compatibility mode just replaces some unsupported (by Glue) characters with underscores.