Home>
We created a WebACL in AWS WAF to apply IP restrictions in CloudFront.
When trying to set from CloudFront Distributions/General/AWS WAF Web ACL on the console screen of CloudFront, only "None" is displayed.
The WebACL Region is set to "Global (CloudFront)".
If i specify the target CloudFront in Associated AWS resources when creating WebACL by another method,
Looking at AWS WAF Web ACL from the CloudFront console screen, it is "None",
In fact, IP restrictions are not working well.
Do you know where the cause is?
You have just created a WebACL and no other rules have been set up ↓ (CloudFront is not linked at this point)
-
Answer # 1
Related articles
- aws - unicorn error log location
- aws - about nxdomain error when issuing ssl certificate in bitnami
- aws - i don't know how to save lightsail with cron editor
- aws - aws:about server construction
- aws - every time when uploading laravel application with aws codedeploy, error occurs in env
- aws - i want to pull docker image with aws cli (no basic auth credential error)
- aws - is there a way to exclude the "aws-sdk" module when deploying to lambda from cloud9?
- aws - aws authentication error for serverless framework
- aws - [aws] i want to connect to an rds instance using an ec2 instance as a springboard with ssh
- aws - i want to connect to an aws instance with ssh, but it times out
- aws - acm certificate cannot be linked to aws cloudfront
- aws - i want to calculate the processing time on aws
- aws - should i change session management from default cookie to redis when using laravel 6x for redundancy with elb?
- aws - i don't know the identity of aws rds
- aws - about aws login
- aws - i can't access the eks sample guestbook
- aws - about errors in aws waf
- aws - i have a question about aws lambda
- aws - [aws ses] i want to know why e-mail cannot be sent to the docomo e-mail address
Trends
Reproduced.
Apparently it seems to be a problem on the AWS side.
It looks like the AWS WAF console has been renewed, but the resources created there seem to be treated differently from the resources created in the traditional AWS WAF console.
Apparently, CloudFront can only refer to resources created with the traditional console ...
Although it will be supported on the AWS side in the future, it seems that there is no choice but to create a resource with the conventional console and apply it.
Click Switch to AWS WAF Classic to return to the traditional console.
This is a problem that should be requested from AWS ...