Maintain existing endpoint and cache when modifying architecture type
With the release of the Object Lambda architecture, customers have the ability to enable an architecture which supports larger images. Modifying an existing distribution to use this architecture will cause a deletion and recreation of the CloudFront distribution associated with the deployment. This will result in a change to the domain name, as well as the cache being cleared. The following workaround can be used to modify the architecture type while avoiding this deletion.
Note
This workaround is not officially supported, and may run into instability. This workaround requires that both stacks are maintained in order to maintain functionality. Any updates to the original stack may undo some of the changes performed here. You may experience downtime
-
Follow the process for deploying a new Dynamic Image Transformation for Amazon CloudFront stack. Refer to deploy the solution for additional guidance on this step.
-
Modify the Enable S3 Object Lambda template parameter to select your desired architecture.
-
Set Use Existing CloudFront Distribution to
Yes -
Set Existing CloudFront Distribution Id to the ID of the Image Handler distribution for your existing stack.
-
Set the remaining template parameters to the same values used in the original deployment.
-
Deploy the stack.
-
Upon completion of the deployment, follow the instructions in Attaching an Existing CloudFront distribution to attach the CloudFront distribution referenced to the newly deployed resources. This will require that you overwrite the existing values on the distribution.
