Your prefix(es) may have been added to an AWS-managed WAF rule-set for whatever reason.
These rule-sets are used by the AWS WAF service which many AWS customers use. On Tue, Oct 18, 2022 at 8:39 PM Justin H. <justindh...@gmail.com> wrote: > Is it possible this is a geolocation issue? I'm not sure I've heard of > that causing a 403 Forbidden, but I'm also not too familiar with AWS. > > Justin H. > > William Herrin wrote: > > Sounds like "AWS Shield" but I couldn't begin to tell you who to contact. > > > > On Tue, Oct 18, 2022 at 4:51 PM Justin H. <justindh...@gmail.com> wrote: > >> I have a customer who's suddenly been getting 403's today on AWS hosted > >> sites. My google-fu seems to be failing me because I can't seem to find > >> any information on who manages that on their side or how to fix the > issue. > >> > >> I've sent an email to amzn-noc-cont...@amazon.com based on ARIN > >> contacts, but it doesn't seem to be a responsive address. > >> > >> Has anyone had to navigate this particular maze before? > >> > >> Thank you, > >> Justin H. > > > > > >