I would suppose that you could do similar attacks if someone used AWS S3 as a static site backend, then deleted the bucket, since S3 bucket names are global acr

I would suppose that you could do similar attacks if someone used AWS S3 as a static site backend, then deleted the bucket, since S3 bucket names are global across all AWS accounts. It would be very difficult to find a target, since it seems as though people tend to leave S3 buckets around forever (see the recent "Facebook" leak that was caused by a defunct company leaving public S3 buckets around w/PII).