You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
While identifying DB assets and organizing the endpoints of the instances, it is difficult to achieve this with the current columns of the aws_elasticache_cluster table.
Describe the solution you'd like
If ShowCacheNodeInfo is passed as a parameter when calling DescribeCacheClusters, I can get additional information about individual cache nodes. Therefore, I intend to utilize this.
Describe alternatives you've considered
For now, I plan to temporarily use the exec plugin and AWS CLI, but it seems more natural for the aws_elasticache_cluster to support this natively.
Additional context
Simply passing ShowCacheNodeInfo in every query raises concerns about performance degradation. Therefore, I want to pass this parameter only when columns like cache_node_endpoint or cache_node_status are included in the select statement. I'm curious if there are any best practices for this approach.
By appending ShowCacheNodeInfo, we can obtain the following information. Please refer to the image below.
I only need the endpoint information here, but other information could be useful elsewhere.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
While identifying DB assets and organizing the endpoints of the instances, it is difficult to achieve this with the current columns of the aws_elasticache_cluster table.
Describe the solution you'd like
If ShowCacheNodeInfo is passed as a parameter when calling DescribeCacheClusters, I can get additional information about individual cache nodes. Therefore, I intend to utilize this.
Describe alternatives you've considered
For now, I plan to temporarily use the exec plugin and AWS CLI, but it seems more natural for the aws_elasticache_cluster to support this natively.
Additional context
The text was updated successfully, but these errors were encountered: