🐛 Handle DNS resolution errors in ElastiCache discovery#6902
Merged
Conversation
ElastiCache endpoints may not resolve in all regions, causing discovery to fail with "no such host" errors. Use the existing IsServiceNotAvailableInRegionError helper to gracefully skip unavailable regions, matching the pattern used by 12+ other AWS resources (memorydb, msk, opensearch, etc.). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Member
Author
|
Fixes discovery errors we get on the CLI right now: |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
DescribeCacheClustersandDescribeServerlessCachesfail with "no such host" DNS errors in regions where ElastiCache endpoints don't resolveIsServiceNotAvailableInRegionErrorchecks to bothgetCacheClustersandgetServerlessCaches, matching the established pattern used by 12+ other AWS resources (memorydb, msk, opensearch, elb, cognito, etc.)Test plan
make providers/build/aws && make providers/install/aws)mql run aws -c "aws.elasticache.cacheClusters"— should no longer error on regions where ElastiCache DNS doesn't resolve🤖 Generated with Claude Code