Hi team, We set up an elb access logging bucket through our medplum config like so:

"loadBalancerLoggingEnabled": true,
  "loadBalancerLoggingBucket": "medplum-logs-us-east-1",
  "loadBalancerLoggingPrefix": "elb-staging"

We see it in the Attributes section of our Load Balancer. However, when we go to this bucket, we get the error: Insufficient permissions to list objects After you or your AWS administrator has updated your permissions to allow the s3:ListBucket action... Even from the root account. Additionally - the bucket does not show up in our S3 console. - the bucket does not show up when we use the CLI:

aws s3 ls

(using same AWS credentials used to run medplum client) We know it exists though because when we try to make a new bucket with the same name, "medplum-logs-us-east-1" it says a bucket already exists with that name. We've manually made a new bucket for elb access logs like this: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/enable-access-logging.html However, we can't delete this bucket (no permissions). How does this bucket get spun up by the medplum config settings? It doesn't seem like our accounts were given the necessary access to it.

if you run aws s3 ls using the same AWS credentials used to spin up your cluster - can you see the bucket then?

No, we are still unable to see it when using the same AWS credentials used to spin up our self-hosted medplum instance