diosbejgli at gmail.com
Wed Oct 19 01:05:43 UTC 2022
The correct address for operational issues is peering-to at amazon.com .
Have you tried checking http://ec2-reachability.amazonaws.com/ to see if
you see green ticks everywhere, specifically the prefixes covering the IP
you're having trouble accessing? If so, the endpoint is probably blocking
your requests which is managed by the AWS customer.
On Wed, Oct 19, 2022 at 11:40 AM Justin H. <justindh.ml at 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.ml at 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
> >> I've sent an email to amzn-noc-contact at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NANOG