Note: the reason I have 5 HTTP APIs is because of the 500 resources limit which I surpassed in 4 of them. ![]() Via cloudfront, I managed to get to work, but the other APIs return 404.Īnd is it worth migrating to REST APIs from HTTP APIs just to be able to use AWS WAF? And how could I do that via the Serverless framework? ![]() I tried creating a Cloudfront distribution, but since my original API Gateway has 5 different APIs deployed via the Serverless framework, each API has its own path mapping.įor example, the API no.1 is callable by. I spent 12 hours researching and trying to associate AWS WAF to API Gateway with no luck, since it's not supported with HTTP APIs but only REST. If you're posting a technical query, please include the following details, so that we can help you more efficiently:ĭoes this sidebar need an addition or correction? Tell us here public IP addresses or hostnames, account numbers, email addresses) before posting! ✻ Smokey says: collect and re-use rainwater to fight climate change! Note: ensure to redact or obfuscate all confidential or identifying information (eg. ![]() News, articles and tools covering Amazon Web Services (AWS), including S3, EC2, SQS, RDS, DynamoDB, IAM, CloudFormation, AWS-CDK, Route 53, CloudFront, Lambda, VPC, Cloudwatch, Glacier and more.
0 Comments
Leave a Reply. |