Fix incorrect IAM role reference in Listener CloudFormation template #94
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR resolves an issue in the Listener CloudFormation template where the
ListenerLambdaresource was incorrectly referenced under theRolesproperty of theListenerPolicyresource. The incorrect reference has been updated toListenerRole, ensuring proper association and functionality.Changes Made:
Rolesproperty ofListenerPolicyincloudformation-stacks/listener.template.yamlfile.Impact of the Change:
Resource handler returned message: "The role with name axiom-cloudwatch-listener cannot be found.Testing:
Please review and merge this fix. Let me know if additional updates or testing is required.