2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
2
One option you have is to configure your Canary to use a specific request header or cookie, then look for the presence of that in a custom WAF rule. You could either allow the traffic and not process any other rules, or you could add a label, which you could then use in a scope-down statement to bypass the rule(s) that are currently blocking your Canary
0
You can put all your canaries in the VPC and then whitelist your NAT Gateway IPs from Web ACL. https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries_VPC.html
répondu il y a 4 mois
Contenus pertinents
- Réponse acceptéedemandé il y a un an
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 6 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Thanks for the reply. By any change do you have an example of how to insert a custom header in the Canary code, I have very little knowledge of NodeJS.
Kind Regards.