-
Notifications
You must be signed in to change notification settings - Fork 4
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
Create CloudFront Function and Origin Request Policy #15
base: master
Are you sure you want to change the base?
Conversation
This will create a cloudfront function and request policy along with each distribution, as we're limited on the amount of associations. We _also_ have total limits on policies and functions, so we will likley need to follow this up with being able to link mulitple distributions to a single policy and function, and batch it every 100.
This is pending the max limits we can get from AWS |
'CookieBehavior' => 'whitelist', | ||
'Cookies' => [ | ||
'Quantity' => 3, | ||
'Items' => [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could the cookies list be made filterable to allow for custom cookies to be added to the list when the request policies are created?
I know if that list does ever change then we'd need to either manually update the policy via AWS console or possibly introduce another function for updating policies using the plugin for that use case. Just thinking about that first time policy creation given there can potentially be multiple policies to be created and would be good to have other cookies already included.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we'll need the ability to update the policies anyway. Having a filter would be a good idea too yes
…avoid rate limits.
This will create a cloudfront function and request policy along with each distribution, as we're limited on the amount of associations.
We also have total limits on policies and functions, so we will likley need to follow this up with being able to link mulitple distributions to a single policy and function, and batch it every 100.