The s3 connector has several limitations such as moving or renaming assets & handling metadata. Unfortunately, the S3 API prevents us to overcome these limitations. However, these functionalities are needed in SaaS. 

We want to use a new mixed connector which stores all the metadata in our datastore (JCR or Norsu) but the asset is stored in S3. Then, if an asset is moved or renamed, the S3 asset is not affected, only the metadata is affected.

We want to do a PoC implementing, extending the magnolia-dam-app-jcr to

• A new asset is stored in S3 but the metadata is in JCR.
• We use S3 links to render assets
• When an asset is deleted, the S3 asset is deleted too.