It may be that the configuration of the S3 bucket hacko-data-archive is configured with Public permissions, allowing access to resources such a using boto (AWS SDK for Python) to access static files #195.
Or maybe the access from an ECS-based container inherits some minimal access via AWS to be able to read data from certain parts of the bucket.
I don't remember - was this intentional? Do we consider all archived data backups (original raw files from outside agencies and bureaus, as well as the derived data from those raw sources) to be public domain assets?
It may be that the configuration of the S3 bucket
hacko-data-archive
is configured with Public permissions, allowing access to resources such a using boto (AWS SDK for Python) to access static files #195.Or maybe the access from an ECS-based container inherits some minimal access via AWS to be able to read data from certain parts of the bucket.
I don't remember - was this intentional? Do we consider all archived data backups (original raw files from outside agencies and bureaus, as well as the derived data from those raw sources) to be public domain assets?