Closed sarink closed 1 week ago
Thanks for logging this, and for the concise explanation of what you're trying to do ⭐ We'll have a look into it.
any update on that one? I have the same issue with Bucket v2
Please remember to upvote the issue if it is important to you as it helps our team prioritize!
Having a quick look again here, I believe it's entirely possible to host a static website on S3 with Pulumi. Please check out the https://github.com/pulumi/examples/blob/master/aws-ts-static-website/index.ts example. This example involves a CloudFront configuration which is recommended, but may not be required.
Please have a look at https://www.pulumi.com/registry/packages/aws/api-docs/s3/bucketwebsiteconfigurationv2/ that is definitely required in a complete setup.
What happened?
It is impossible to create a route53 alias that points to an s3 bucket.
The expected result is achieved immediately by manually creating the record in the UI.
Steps to reproduce
Expected Behavior
I expected a route53 alias in my custom zone to be created which points to the s3 bucket
Actual Behavior
Output of
pulumi about
Additional context
Attempting to do this: https://aws.amazon.com/blogs/aws/root-domain-website-hosting-for-amazon-s3/ but it doesn't seem possible with pulumi
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).