Both S3 buckets used by physrisk-lib for public hazard indicator data are currently
returning AllAccessDisabled when accessed anonymously:
$ aws s3 ls --no-sign-request s3://os-climate-physical-risk/
An error occurred (AllAccessDisabled) when calling the ListObjectsV2 operation:
All access to this object has been disabled
$ aws s3 ls --no-sign-request s3://os-climate-public-data/
An error occurred (AllAccessDisabled) when calling the ListObjectsV2 operation:
All access to this object has been disabled
Both buckets fail identically, suggesting an account-level issue rather than a
per-bucket permission change. This blocks all anonymous/public access to physrisk
hazard data, which is documented as the standard access method in the physrisk
README and readthedocs "Getting started" guide.
Tested: 2026-08-13, from local macOS environment, AWS CLI, no credentials.
Both S3 buckets used by physrisk-lib for public hazard indicator data are currently
returning AllAccessDisabled when accessed anonymously:
$ aws s3 ls --no-sign-request s3://os-climate-physical-risk/
An error occurred (AllAccessDisabled) when calling the ListObjectsV2 operation:
All access to this object has been disabled
$ aws s3 ls --no-sign-request s3://os-climate-public-data/
An error occurred (AllAccessDisabled) when calling the ListObjectsV2 operation:
All access to this object has been disabled
Both buckets fail identically, suggesting an account-level issue rather than a
per-bucket permission change. This blocks all anonymous/public access to physrisk
hazard data, which is documented as the standard access method in the physrisk
README and readthedocs "Getting started" guide.
Tested: 2026-08-13, from local macOS environment, AWS CLI, no credentials.