1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
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.
답변함 4년 전
관련 콘텐츠
- AWS 공식업데이트됨 8달 전
- AWS 공식업데이트됨 8달 전