Sam build failed when trying to create a S3 Express One Zone bucket about aws-sam-cli

[GavinZZ]

SAM Transform will ignore non-SAM resource during transform step and return the CFN resource as is. So this is not a SAM Transform issue and likely a SAM CLI issue. Going to transfer to the CLI repository.

[hnnasit]

Hi @Luna-LHY, thanks for reporting the issue. I tried to deploy the following resource and it deployed successfully:

MyBucket:
    Type: AWS::S3Express::DirectoryBucket
    Properties:
      BucketName: example-bucket--use1-az6--x-s3
      DataRedundancy: SingleAvailabilityZone
      LocationName: use1-az6

Could you check here if you are following the the correct guidelines for naming the bucket for AWS::S3Express::DirectoryBucket resource type? SAM CLI calls CloudFormation boto3 API's in the background to create the stack, so there is nothing different SAM CLI does for non-SAM resources.

[Luna-LHY]

Ah thanks for pointing out. I didn't realize we should input the full bucket name there. In S3 console, we only need to input the "Base name", and then it will automatically generate the full bucket name with Availability Zone suffix. So I thought that for cfn template it should be the same....

[Luna-LHY]

I'm still getting the same error after fixing S3 bucket naming pattern. I checked my template and I think the error is probably from Lambda event source. It looks like for S3 event, only AWS::S3::Bucket data type works :(

      Events:
        S3NewObjectEvent:
          Type: S3
          Properties:
            Bucket: !Ref MyExpressOneZoneBucket
            Events: s3:ObjectCreated:*
            Filter:
              S3Key:
                Rules:
                  - Name: suffix
                    Value: ".mp4"
                  - Name: prefix
                    Value: "input/"

Well, Amazon Q told me Lambda supports S3 Express One Zone bucket type as Lambda event, but I didn't find any doc about this.

[hawflau]

Hey @Luna-LHY I confirmed from Lambda Console that I couldn't add a DIrectory Bucket as a Lambda Event. So I guess it's not supported.

Closing the issue. Please re-open or create a new issue if you still have questions

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.