welcome to the n8n community @YELA
I would first fix the n8n public base URL and OAuth redirect setup on the AWS host or reverse proxy, then recreate the Google credential and use the exact OAuth Redirect URL shown by n8n in Google Cloud, because a 414 at the final Google sign-in step usually points to a bad or oversized auth URL rather than the Client ID or Secret themselves.