Open jonthewayne opened 4 years ago
hmm that's def a bug. Thanks for reporting. I'll look into it 😊
@jonthewayne this should now be resolved. Could you try it again on your end?
I am seeing this behavior as well. We have updated to serverless version 2.6.0 and it still happens.
On the most recent Serverless version, had this S3 bucket name as an input:
bucketName: welcome-dev.remember.us
The correct s3 bucket is created correctly:
http://welcome-dev.remember.us.s3-website-us-west-2.amazonaws.com
I also mapped a subdomain, and it points to a cloudfront dist that was also created.
The problem is that the cloudfront dist has the origin as
welcome-dev.s3.amazonaws.com
which is wrong. It's not using the whole bucket namewelcome-dev.remember.us
.