fix: correct issue where permissions were set on the server function …

…and not image optimisation function

README.md

@@ -76,7 +76,7 @@ Below are diagrams of the possible architecture combinations that can configured
 
 ### Single Zone
 
-![Single Zone Complete](https://raw.githubusercontent.com/RJPearson94/terraform-aws-open-next/v2.4.0/docs/diagrams/Single%20Zone.png)
+![Single Zone Complete](https://raw.githubusercontent.com/RJPearson94/terraform-aws-open-next/v2.4.1/docs/diagrams/Single%20Zone.png)
 
 #### Terraform
 
@@ -96,7 +96,7 @@ module "single_zone" {
 
 ```hcl
 terraform {
-  source          = "tfr://registry.terraform.io/RJPearson94/open-next/aws//modules/tf-aws-open-next-zone?version=2.4.0"
+  source          = "tfr://registry.terraform.io/RJPearson94/open-next/aws//modules/tf-aws-open-next-zone?version=v2.4.1"
   include_in_copy = ["./.open-next"]
 }
 
@@ -108,7 +108,7 @@ inputs = {
 
 ### Multi-Zone - Independent Zones
 
-![Multi Zone - Independent Zones](https://raw.githubusercontent.com/RJPearson94/terraform-aws-open-next/v2.4.0/docs/diagrams/Multi%20Zone%20-%20Independent%20Zones.png)
+![Multi Zone - Independent Zones](https://raw.githubusercontent.com/RJPearson94/terraform-aws-open-next/v2.4.1/docs/diagrams/Multi%20Zone%20-%20Independent%20Zones.png)
 
 #### Terraform
 
@@ -138,7 +138,7 @@ module "independent_zones" {
 
 ```hcl
 terraform {
-  source          = "tfr://registry.terraform.io/RJPearson94/open-next/aws//modules/tf-aws-open-next-multi-zone?version=2.4.0"
+  source          = "tfr://registry.terraform.io/RJPearson94/open-next/aws//modules/tf-aws-open-next-multi-zone?version=v2.4.1"
   include_in_copy = ["./docs/.open-next", "./home/.open-next"]
 }
 
@@ -162,7 +162,7 @@ _Note:_ If you use tools like Terragrunt or CDKTF, you can use the Single Zone m
 
 ### Multi-Zone - Shared Distribution
 
-![Multi Zone - Shared Distribution](https://raw.githubusercontent.com/RJPearson94/terraform-aws-open-next/v2.4.0/docs/diagrams/Multi%20Zone%20-%20Shared%20Distribution.png)
+![Multi Zone - Shared Distribution](https://raw.githubusercontent.com/RJPearson94/terraform-aws-open-next/v2.4.1/docs/diagrams/Multi%20Zone%20-%20Shared%20Distribution.png)
 
 #### Terraform
 
@@ -192,7 +192,7 @@ module "shared_distribution" {
 
 ```hcl
 terraform {
-  source          = "tfr://registry.terraform.io/RJPearson94/open-next/aws//modules/tf-aws-open-next-multi-zone?version=2.4.0"
+  source          = "tfr://registry.terraform.io/RJPearson94/open-next/aws//modules/tf-aws-open-next-multi-zone?version=v2.4.1"
   include_in_copy = ["./docs/.open-next", "./home/.open-next"]
 }
 
@@ -214,7 +214,7 @@ inputs = {
 
 ### Multi-Zone - Shared Distribution and Bucket
 
-![Multi Zone - Shared Distribution and Bucket](https://raw.githubusercontent.com/RJPearson94/terraform-aws-open-next/v2.4.0/docs/diagrams/Multi%20Zone%20-%20Shared%20Distribution%20and%20Bucket.png)
+![Multi Zone - Shared Distribution and Bucket](https://raw.githubusercontent.com/RJPearson94/terraform-aws-open-next/v2.4.1/docs/diagrams/Multi%20Zone%20-%20Shared%20Distribution%20and%20Bucket.png)
 
 #### Terraform
 
@@ -266,7 +266,7 @@ inputs = {
 
 ## Custom Domains
 
-For infomation on managing custom domains see the [domain-config documentation](https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.0/docs/domain-config.md)
+For infomation on managing custom domains see the [domain-config documentation](https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.1/docs/domain-config.md)
 
 ## Examples
 

modules/tf-aws-open-next-multi-zone/variables.tf

@@ -19,7 +19,7 @@ The possible values are:
 - SHARED_DISTRIBUTION
 - SHARED_DISTRIBUTION_AND_BUCKET
 
-See https://github.com/RJPearson94/terraform-aws-open-next/tree/v2.4.0?tab=readme-ov-file#deployment-options for a complete breakdown of the different deployment options.
+See https://github.com/RJPearson94/terraform-aws-open-next/tree/v2.4.1?tab=readme-ov-file#deployment-options for a complete breakdown of the different deployment options.
 
 EOF
 
@@ -177,7 +177,7 @@ Possible values for backend_deployment_type:
   - REGIONAL_LAMBDA
   - EDGE_LAMBDA
 
-See https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.0/docs/backend-server-deployments.md for a complete breakdown of the different backend options.
+See https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.1/docs/backend-server-deployments.md for a complete breakdown of the different backend options.
 
 **NOTE:** When backend_deployment_type is set to EDGE_LAMBDA, Terraform does not manage cloudwatch log groups; instead, the lambda service creates the log group when the function runs in each region.
 
@@ -252,7 +252,7 @@ Possible values for backend_deployment_type:
   - REGIONAL_LAMBDA_WITH_OAC_AND_ANY_PRINCIPAL
   - REGIONAL_LAMBDA
 
-See https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.0/docs/backend-server-deployments.md for a complete breakdown of the different backend options.
+See https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.1/docs/backend-server-deployments.md for a complete breakdown of the different backend options.
 
 If you do not want to provision the image optimisation function, you can set `create` to false.
 
@@ -416,7 +416,7 @@ Possible values for deployment are:
 - NONE
 - CREATE
 
-The module has a local copy of the x-forwarded host CloudFront function code by default. The code can be seen at https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.0/modules/tf-aws-open-next-public-resources/code/xForwardedHost.js. 
+The module has a local copy of the x-forwarded host CloudFront function code by default. The code can be seen at https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.1/modules/tf-aws-open-next-public-resources/code/xForwardedHost.js. 
 
 This code can be overridden by passing in the javascript function as a string to the `code` argument under the `x_forwarded_host_function` object. An example can be seen below.
 
@@ -428,7 +428,7 @@ x_forwarded_host_function = {
 
 The auth function is deployed if the server function backend_deployment_type is set to EDGE_LAMBDA.
 
-The module has a local copy of the auth function code, which will be deployed by default. The code can be seen at https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.0/modules/tf-aws-open-next-public-resources/code/auth/index.js. You can override this to supplying a zip file containing the lambda code with either a local reference or a reference to the zip in an S3 bucket.
+The module has a local copy of the auth function code, which will be deployed by default. The code can be seen at https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.1/modules/tf-aws-open-next-public-resources/code/auth/index.js. You can override this to supplying a zip file containing the lambda code with either a local reference or a reference to the zip in an S3 bucket.
 
 Possible values for the auth_function deployment are:
 - NONE 
@@ -930,7 +930,7 @@ Configuration for CloudFront distribution domain
 
 When the deployment is set to 'INDEPENDENT_ZONES' this can be overridden for each zone. If deployment is 'SHARED_DISTRIBUTION' or 'SHARED_DISTRIBUTION_AND_BUCKET' this configuration is used
 
-See https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.0/docs/domain-config.md for a complete breakdown of the different domain configuration options. 
+See https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.1/docs/domain-config.md for a complete breakdown of the different domain configuration options. 
 
 EOF
 
@@ -960,7 +960,7 @@ Configuration for continuous deployment config for CloudFront
 
 When the deployment is set to 'INDEPENDENT_ZONES' this can be overridden for each zone. If continuous deployment is enabled, updates to the origins, ordered_cache_behaviors and default_cache_behaviors are ignored
 
-See https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.0/docs/continuous-deployments.md for a complete breakdown of how to use continuous deployment. 
+See https://github.com/RJPearson94/terraform-aws-open-next/blob/v2.4.1/docs/continuous-deployments.md for a complete breakdown of how to use continuous deployment. 
 
 EOF