-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optional private content bucket #26
base: main
Are you sure you want to change the base?
Conversation
With origin access identity + CloudFront, it most likely will not be necessary to keep it public.
@zchase and @sean1588 I tried to follow the build and test instructions but when I ran:
I am seeing errors like:
And a bunch more errors. Specifically: TS1005, TS1068, TS1109, TS1128. |
Hi @chadbean! Thanks for contributing this PR! What version of node are you running? I believe you need to be on node 16 in order for this to build successfully. |
Thanks, @sean1588. I tried to go through the steps again making sure I have the versions in place:
But I'm still seeing the same errors. Let me know if you have any other ideas and I can try them. Otherwise if there's a way to get this tested in fully in CI I'm happy to let that run instead of worrying about my local env. |
@sean1588 I was able to get the
Perhaps there is a dependency in the SDK that should have more strict pinning? Will continue with testing a bit later. |
@sean1588 I was able to go into each directory inside of
Is there another step I have to run or should the sitePath value in |
thanks @chadbean. sorry for the late response! Yeah you need to run |
Thanks for your contribution. I'll test this out as well. |
Which dir should I run |
@chadbean you need to run it in the website directory. This will generate the build directory. |
hey @chadbean, just wanted to check in and see if you were able to generate the build successfully. Let me know if you need any other assistance, happy to help! |
Thanks, @sean1588. I ran Since all the examples worked for me without AWS creds except this one, would you be able to help me test this?
|
@chadbean, yeah you will need access to an AWS account with credentials that can perform the actions needed to provision the infrastructure in order to use this component. I can pull your changes and get them tested. |
@sean1588 looks like there's a conflict now. I can try to fix that but once I do, I wanted to see if you'd be able to help test this? |
issues: #22
This adds optional support for setting the content S3 bucket to private. When using this bucket with CloudFront's origin access identity, it should not be required to set the bucket itself to public if we only need CloudFront to access it.