1 Answer
- Newest
- Most votes
- Most comments
0
I think perhaps the subscription filter policy for removing automated integration test messages I had was the cause for not getting console test messages:
{
"ip": [
{
"anything-but": "192.168.0.80"
}
]
}
I didn't think this would block AWS console test messages, and even after removing it the console test messages were blocked. But some minutes later the console test messages would work again. I could be wrong, but it appears that two strange things are a factor:
- Changing the subscription filter policy has a few minutes delay
- This ip filter is somehow blocking the console test messages
The messages not firing from the application were a separate problem related to PrivateLink.
answered 4 years ago
Relevant content
- Accepted Answerasked 21 days ago
- asked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago