# How to specify S3 bucket VersioningConfiguration in serverless.yml

**URL:** https://forum.serverless.com/t/how-to-specify-s3-bucket-versioningconfiguration-in-serverless-yml/7103
**Category:** Serverless Framework
**Created:** [January 21, 2019, 7:51pm UTC](https://forum.serverless.com/t/how-to-specify-s3-bucket-versioningconfiguration-in-serverless-yml/7103 "2019-01-21T19:51:47Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![thoward333](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/thoward333/32/2967_2.png) [@thoward333](https://forum.serverless.com/u/thoward333)
#### Post date: [January 21, 2019, 7:51pm UTC](https://forum.serverless.com/t/how-to-specify-s3-bucket-versioningconfiguration-in-serverless-yml/7103/1 "2019-01-21T19:51:47Z")

</div>

Disclaimer: I’m new to serverless. I’m trying to configure an S3 bucket that my function will use. I need it to be encrypted and keep versions. I assumed the property names would align to cloud formation docs, but I got an error (see below)

Here’s the yaml I’m trying to use:

> resources:  
> Resources:  
> MyBucket:  
> Type: AWS::S3::Bucket  
> Properties:  
> BucketName: my-bucket  
> BucketEncryption:  
> ServerSideEncryptionConfiguration:  
> - ServerSideEncryptionByDefault:  
> SSEAlgorithm: AES256  
> VersioningConfiguration: Enabled  
> LoggingConfiguration:  
> DestinationBucketName: my-bucket-logs  
> LogFilePrefix: access-

And I get this error:

> An error occurred: MyBucket - Encountered unsupported property VersioningConfiguration.

Is this feature supported in serverless.yml?

---

<div class="post-metadata">

### Author: ![buggy](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/buggy/32/177_2.png) [@buggy](https://forum.serverless.com/u/buggy)
#### Post date: [January 30, 2019, 5:36am UTC](https://forum.serverless.com/t/how-to-specify-s3-bucket-versioningconfiguration-in-serverless-yml/7103/2 "2019-01-30T05:36:29Z")

</div>

> [@thoward333](#):
>
> I assumed the property names would align to cloud formation docs

They do. According to the docs it should be

```yaml
VersioningConfiguration:
  Status: Enabled

```
