Your go containers don't need anything more than your static binary, root certs, and tzinfo files. Everything else is extra.
Not to mention the load balancer and container orchestration to run the containers.
It's not all bad. Container tools and services are ubiquitous, pleasant to use, and support literally any workload you may have.
But throwing a zip in S3 and having API gateway send it requests is far less moving parts (at least that we have to worry about).
On AWS Lambda, I can't just rip out my entire infrastructure and move elsewhere. I'm stuck with AWS Lambda until I rewrite my functions to not rely on AWS Lambda and AWS Services.
If my hoster decides they don't like me anymore, I can move my business elsewhere within the hour. Can you move AWS Lambda to another provider within the hour?