Custom s3 configuration bucket names not supported

[mbruning24]

I have a serverless configuration that uses the v3 custom bucket configuration for s3 events shown here.

provider:
  s3:
    myBucket:
      name: 'some-custom-name-here'
      # etc...

functions:
  myFunction:
    events:
      - s3:
          bucket: myBucket
          event: s3:ObjectCreated:*

When the buckets() function is called in the start handler (here) to create the resources for s3rver, it just returns the string myBucket as the bucket name, which obviously in this case it is not.

Can we get some additional logic to check for bucket configurations at this.service.provider.s3[key] before just defaulting to the identifier?

[mbruning24]

For additional reproduction info, you can set up your serverless yml as above and run aws --endpoint http://localhost:8001 --profile <your_local_profile> s3api list-buckets and get the response

{
    "Owner": {
        "DisplayName": "S3rver", 
        "ID": "123456789000"
    }, 
    "Buckets": [
        {
            "CreationDate": "2022-04-07T15:16:47.737Z", 
            "Name": "myBucket" // should be "some-custom-name-here"
        }
    ]
}

[mbruning24]

Although, I just found an undocumented option that can work around this

custom:
  s3:
    # other config
    buckets: some-custom-name-here

This will work when you don't need the extra configuration (like cors, website, etc)

Still, it would be great just to pass along the configuration.

[ar90n]

@mbruning24
Thanks for your report! And I'm sorry for the poor documentation. I added the specification about buckets you said to README.md.

[bitsofinfo]

@mbruning24 @so... you can only define ONE custom bucket via "buckets:" option? is this a comma delimited list? array? just a single string?