I have a ReactJS application that produces a dist folder when I perform an npm build. This can be uploaded to Amazon's S3 and everything is fine.

I'm looking to continuously deploy this application, so my thoughts were to deploy to s3://RANDOM_STRING/, producing:

RANDOM_STRING/js RANDOM_STRING/css RANDOM_STRING/index.html

I can't tell S3, to the best of my knowledge, to use a sub-directory as a web-root, so I looked into CloudFront and updating the origin to the directory. This takes a lot of time to update and actually can't be done through the aws-cli, so continuous deployment would be ruined.

I've looked at using file-loader to rewrite my url() calls to include the RANDOM_STRING into the deployment assets, but this feels pretty "ugly"

Does anyone have experience of this kind of deployment and could help me out?