I’m going to try to speak from all sides.
For context: I am a software developer/architect/team lead depending on how the wind blows. I am also now responsible for guiding the “cloud native initiatives.” I’m going to hit a ceiling in the next year or two as an IC in my market and might want to go into consulting working for a company.
I have six AWS certifications: The three associate certs, two professional and one specialty. The company paid for all but the first. I use them as a guided learning path to help me know what I don’t know.
With six certifications, I run the risk of looking like a paper tiger - someone who spends more time getting certifications than having practical experience. I’m leaving the three associate certs off of my resume. I have enough real world experience on my resume to show that I know the core areas of AWS that they cover.
Consulting companies care about relevant certifications because they can tell their clients that their consultants have them and they need them to keep their “partner” status.
I’ve also been on the other side of the table interviewing candidates. I take most certifications as a slightly negative signal and I definitely don’t think of them as proof of anything. I got my first AWS certification without ever logging into a AWS. I passed the two professional certs and the one associate cert with only nine months of experience with AWS doing small proofs of concepts.
All that to say. I agree completely. Putting it on your resume will only pass you through the HR filter if it is a certification that is required for the company to keep partner status. Any decent hiring manager will ignore them.