We are not looking to map the bucket root to the site root. We are looking to map a DNN folder to the bucket root, not a subfolder of the bucket. Right now all we can seem to do is map to a subfolder of a bucket, not the bucket itself. That limits the flexibility of how content is managed using other systems as well as making it impossible to use a common folder naming convention inside of the buckets.

The intent here is to use a provider to make the connection to the root of a bucket and have the contents of that bucket be completely managed from within DNN as well as other 3rd party applications without the need to create a subfolder used as the root by DNN in the bucket.

If all we did was manage and deliver the content from within DNN the current solution would work but that limits all of the other content management and deliver options we have.

Is there another way around this?