AWS Config support for ElastiCache resource types

Question

I'm looking to write a custom AWS Config rule using Guard to validate the configuration of my ElastiCache resources, but I found that ElastiCache is not listed under the supported resource types. In addition, when I went into my AWS Config settings to configure my "Customer managed recorder", I couldn't find any ElasticCache resources in the dropdown list when I tried to add a resource type to my recorder.

However, there are several managed AWS Config rules that deal with the resource type AWS::ElastiCache::CacheCluster - for example elasticache-auto-minor-version-upgrade-check.

How come ElastiCache is not listed in the supported resource types but is in fact supported by managed rules like elasticache-auto-minor-version-upgrade-check?

However, there are several managed AWS Config rules that deal with the resource type **AWS::ElastiCache::CacheCluster** - for example [elasticache-auto-minor-version-upgrade-check](https://docs.aws.amazon.com/config/latest/developerguide/elasticache-auto-minor-version-upgrade-check.html).

How come ElastiCache is not listed in the supported resource types but is in fact supported by managed rules like **elasticache-auto-minor-version-upgrade-check**?

re:Post Agent · Answer

There appears to be some confusion regarding the support for ElastiCache resources in AWS Config. While ElastiCache resources are indeed supported by AWS Config, they may not be listed explicitly in some documentation or user interfaces.

AWS Config does support tracking ElastiCache resources, including the following resource types:

1. AWS::ElastiCache::CacheCluster
2. AWS::ElastiCache::ReplicationGroup
3. AWS::ElastiCache::SubnetGroup
4. AWS::ElastiCache::ParameterGroup

The fact that there are managed AWS Config rules like "elasticache-auto-minor-version-upgrade-check" that deal with the AWS::ElastiCache::CacheCluster resource type confirms this support.

The discrepancy you're experiencing might be due to a few reasons:

1. Documentation lag: The list of supported resource types in the AWS Config documentation might not be fully up-to-date.

2. Regional availability: Some resource types might not be supported in all regions. Make sure you're looking in the correct region where your ElastiCache resources are deployed.

3. UI limitations: The dropdown list in the AWS Config settings for configuring the "Customer managed recorder" might not show all supported resource types, possibly due to UI constraints or regional differences.

4. Configuration issues: It's possible that AWS Config is not set up to record ElastiCache resources in your account or region. You may need to update your AWS Config settings to include these resource types.

To ensure AWS Config is properly set up to track your ElastiCache resources:

1. Review your configuration recorder settings in the AWS Config console.
2. Make sure the ElastiCache resource types you want to track are selected for recording.
3. If you're writing a custom AWS Config rule using Guard, you should be able to use the ElastiCache resource types mentioned above.

If you're still unable to find or configure ElastiCache resources in AWS Config, it would be advisable to contact AWS support for further assistance, as they can provide the most up-to-date and account-specific information.  
**Sources**  
[finding lost resource using AWS config. | AWS re:Post](https://repost.aws/questions/QU8gdVU2E5Q62v8XLARwIfuA/finding-lost-resource-using-aws-config)  
[elasticache-auto-minor-version-upgrade-check - AWS Config](https://docs.aws.amazon.com/config/latest/developerguide/elasticache-auto-minor-version-upgrade-check.html)

AWS Config support for ElastiCache resource types

Relevant content