I don't think it's necessarily AWS.

I've got coworkers who are on campus, and can access AWS (and AWS-based sites) fine. Their connection to AWS is via the CENIC ISP, which peers directly to AWS.

Me, at home, on Comcast, I cannot connect to AWS-based sites, nor to the AWS console.

Seeing similar issues here with GCP and Comcast, seems to be the common link and not AWS.

I'm able to access the Google Cloud Console, while I'm unable to access the AWS Console.

Can you provide more details on what you're seeing?

This appears to be resolved. AWS posted an update to their status page, which matches some of the observations in this thread about it being ISP-specific:

[RESOLVED] External Connectivity Issues

Between 11:43 AM and 1:30 PM PST some customers may have experienced connectivity issues between an external provider outside of our network and AWS destinations. This issue impacted connectivity originating from California. Connectivity to instances and services within the Region was not impacted during this issue. All AWS Services have been, and continue to operate normally.

I'm on Comcast, can't even access Down Detector. Lots of websites seem down.

Seems like the issue is just for people on Comcast.

5G Verizon works but not Comcast

AWS dash is always the last to know

maybe is localized. not seeing our infra down

something something oauth2 something