Building Security Conscious Video Streaming Infrastructure on AWS, Lesson 3: Prepare for Traffic Surges

External Traffic Fails to Reach EKS Pods with NLB Client IP Preservation

Why are my Yarn applications in Amazon EMR still in the Accepted state?

How do I find the top contributors to NAT gateway traffic in my Amazon VPC?

How do I troubleshoot stopped traffic when the network configuration hasn't changed in Amazon VPC?

I'm seeing inbound traffic in the VPC flow logs for my public NAT gateway. Is my public NAT gateway accepting inbound traffic from the internet?

as the title says:
* I operate AS328964 for our corporate
* since 15:16 GMT+2 2023-05-05 amazon in USA-WEST has stopped accepting traffic from my ipv4 prefix
* ipv6 prefix is being accepted
* traffic is delivered through my upstream provider
* all other regions and zones are accepting my prefix
* all my prefixes are RPKI signed

What I have tried:
* email sent to amazon peering team to resolve (no feedback)
* upstream has opened a ticket to resolve (with no success)
* AWS support twitter account directed me here :/

Amazon USA-WEST not accepting traffic from my ISP

Networking & Content Delivery

After RDS OS patched in an offline operation RDS Database is not accepting connection from outside the VPC

AWSIotDeviceProperty annotation does not accept updates from the shadow.

email sent by Amazon SES not accepted by gmail

How can I use AWS traffic mirroring to copy the traffic from my EKS cluster

Amazon USA-WEST not accepting traffic from my ISP

Relevant content