fix(rds): use CustSubscriptionId instead of CustomerAwsId for event subscriptions #2099
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.
The loadEventSubscription function was incorrectly using CustomerAwsId (AWS account ID) instead of CustSubscriptionId (subscription name) as the resource identifier. This caused import failures when the account ID was used as the subscription name in Terraform operations.
Fixes event subscription import errors where AWS would reject the account ID as an invalid subscription identifier.