You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. Thanks for this sample. I believe this will create a new s3 bucket for hosting static files and also create a cloudfront distribution for serving those files/contents. Please let me know if I'm mistaken.
Could you please provide an option so that I can deploy the lambda that will connect to an existing cloudfront?
I already have cloudfront distribution serving from existing s3 bucket. I'd prefer to keep that infrastructure since they have other configs made. Giving the option for using existing cloudfront will also be useful if contents are served from an origin other than s3 bucket.
The text was updated successfully, but these errors were encountered:
Completely agree. A common use case is that users of this repository already have infrastructure in place for CloudFront and S3, but they're looking to supplement the existing infrastructure with authentication via this module.
Hello. Thanks for this sample. I believe this will create a new s3 bucket for hosting static files and also create a cloudfront distribution for serving those files/contents. Please let me know if I'm mistaken.
Could you please provide an option so that I can deploy the lambda that will connect to an existing cloudfront?
I already have cloudfront distribution serving from existing s3 bucket. I'd prefer to keep that infrastructure since they have other configs made. Giving the option for using existing cloudfront will also be useful if contents are served from an origin other than s3 bucket.
The text was updated successfully, but these errors were encountered: