1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
What changes are you making to your CloudFront Distribution resource in your template? Are you attaching WAF separately to CloudFormation? If you modify a property affecting WAF, CloudFormation may overwrite it; if you modify a property which requires replacement, CloudFormation will replace your Distribution with a new one.
I'd recommend you use CloudFormation to associate AWS WAF with your Distribution. You can provide it using the WebACLId
property of the DistributionConfig
property in your template. If you don't want to manage the whole WAF through CloudFormation, I'd recommend making a Parameter in your template to allow you to specify the WAF ACL Id, and then use that parameter when setting the value in the Distribution resource.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- Come posso risolvere l'errore "Custom Named Resource already exists in stack" in AWS CloudFormation?AWS UFFICIALEAggiornata 2 anni fa
Hi James_S, WAF I don't use Cloudformation. It was created on consoles. Only Cloudfront was created by Cloudformation.
Maybe I will write Cloudformation for WAF. Thank for the advice. Best regard.