Expired SSL/TLS certificates should be removed from AWS IAM
This check looks at the server certificates stored in AWS IAM and whether any of them are past their expiry date. The safe setting is to have none left that have expired.
Why it matters
IAM can hold server certificates that you uploaded for older AWS services. Once such a certificate has expired, it no longer proves anything, but it still sits in the account with its name, its history and, in some setups, a reference from a listener. Leaving it there invites someone to attach it again by mistake, which breaks the encrypted connection for visitors, and it clutters the inventory when you try to find certificates that matter.
The AWS documentation on server certificates in IAM explains that this store is meant for specific regions and cases, and that AWS Certificate Manager is the recommended place for new certificates. Clearing out expired entries keeps the account tidy and removes a source of outages and confusion. It also makes a later review simpler, because every certificate that remains in the list is one that someone should be able to explain.
How to check it yourself
Portal: the IAM console does not list server certificates, so use the command line or an API tool for this check.
Read-only command (AWS CLI, list only):
aws iam list-server-certificates --query "ServerCertificateMetadataList[].{Name:ServerCertificateName,Expires:Expiration}" --output tableCompare each expiry date with today. Any certificate with a date in the past is a finding. Before you remove one, find out whether a load balancer or a CloudFront distribution still points at it.
How to fix it
Steps: confirm that the certificate is not in use, replace it where needed with a valid certificate from AWS Certificate Manager, and then delete the expired one. This is done through the CLI or API because the console has no page for it.
Script (this deletes an object, so run it deliberately, one certificate at a time):
aws iam delete-server-certificate --server-certificate-name NAME_OF_EXPIRED_CERTConfigCobra only reads your account. It never deletes a certificate for you.
What changes when you fix it
An expired certificate that nothing uses disappears quietly with no visible effect. If something still referenced it, that service was already presenting an expired certificate, so visitors were seeing browser warnings; replacing it with a valid certificate fixes that.
The people affected are the owners of any load balancer or distribution that used the certificate. Deletion cannot be undone, so keep the certificate file and chain somewhere safe if you might need to inspect them later.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Amazon Web Services Foundations v7.0.0 | 2.17 | Level 1 |
Check this on your AWS
ConfigCobra runs this check with every other control of the CIS Amazon Web Services Benchmarks, read-only.