Repository hosting sample AWS CDK Pipeline for deploying changes Amazon CloudFront Distribution using CloudFront continuous deployment

Continuous Delivery of CloudFront Distribution Configuration Changes

1. Install NPM
2. Install CDK
3. AWS CodeBuild Repository

The following sections contain steps A through D with instructions to create a distribution, test distribution, and release distribution configuration changes using Amazon CloudFront Continuous deployment.

1. Clone this repository to make changes and commit to your code repository
2. Update the repository settings by editing lib/pipeline-input-variables.ts change the value of PIPELINE_CODE_REPO variable to point to your code repository name
3. Add environment (account and region) by editing bin/cf-cd-sample-app.ts follow comments in the file to uncomment and edit the right environment entry
4. Bootstrap CDK using command cdk bootstrap if not already done
5. Update/customize the other variables per applicable naming standards
6. Update the git remote to point to code repository by running git remote set-url origin <replace-with-your-repository-URL>
7. Commit your changes to code repository
8. Run command npm install to install dependencies
9. Run the command cdk deploy to deploy the pipeline

Executing instructions listed above creates a AWS CodePipeline and runs the pipeline. Running the pipeline will result in creating a Amazon CloudFront Distribution with S3 Origin.

1. Open AWS Console and navigate to AWS CodePipeline and validate that the pipeline was successful
2. Locate the distribution with description as mydistribution in Amazon CloudFront console and copy the Distribution domain name
3. Test the distribution by opening distribution URL in a browser or using command curl <distribution URL>
4. Opening the URL should display content of index.html

1. Make distribution configuration updates by editing lib/app-stacks/cf-distribution-config.ts file
2. Enable continuous deployment by edit pipeline-input-variables.ts file to update ENABLE_CONTINUOUS_DEPLOYMENT to true
3. commit code changes to repository

The above code commit will trigger the pipeline, which will result in deploying a staging distribution and deployment policy attached to the primary distribution created above in Step - B

Below steps assume that the SingleHeader traffic configuration is in place. Http header is not required to test SingleWeight traffic configuration

1. Validate that the pipeline is waiting for approval on Promote stage
2. Test the configuration changes by using command line curl -H "aws-cf-cd-test: blue" <distribution test URL> or through browser by adding additional http header aws-cf-cd-test: blue to the request
3. After completing testing, you can promote staging distribution configuration to primary distribution by approving the Promote stage step in the pipeline

Follow below instructions if you want to remove the Pipeline and stacks created by this sample. Please note that deleting a Pipeline doesn't remove the stacks created by pipeline and must be deleted using AWS CLI or AWS Console.

Please note that deleting stacks will remove the distribution. Do not run below steps on live distributions or distributions serving real users If you are running with ENABLE_CONTINUOUS_DEPLOYMENT set to true then follow steps Delete Deployment Policy and Delete Staging Distribution Stack before Delete Primary Distribution Stack

1. Open CloudFront Console and locate the primary distribution. Click on Primary distribution and scroll down to Continuous deployment section.
2. Remove the deployment policy from primary distribution by clicking on Delete button

1. Once deployment policy is removed, we will need to deploy primary distribution before we can delete staging distribution stack by disabling continuous deployment and running the pipeline
2. Disable continuous deployment by editing pipeline-input-variables.ts and setting ENABLE_CONTINUOUS_DEPLOYMENT to false
3. Commit the change to repository
4. Commit to repository will trigger the pipeline to deploy latest changes to primary distribution
5. Once the primary distribution is deployed, you can delete the staging distribution stack by running below command in through AWS CLI or from CloudFormation console
   1. aws cloudformation delete-stack --stack-name StagingDistribution-Change-cf-distribution-stack

1. run the following commands to delete the primary distribution stack or from CloudFormation console
   1. aws cloudformation delete-stack --stack-name PrimaryDistribution-Change-cf-distribution-stack

1. run the following command from repository root directory or delete the pipeline stack from CloudFormation console
   1. cdk destroy

1. Remove S3 Origin bucket and Site logs bucket using S3 Console

Cost for running this solution consists of Code Repository cost, CI/CD Pipeline cost, and Amazon CloudFront Distribution cost

1. If the pipeline fails during stack creation, then the stack must be manually deleted before retrying the pipeline steps
2. set account via CDK_DEFAULT_ACCOUNT for agnostic or explicitly set account number if you see error 'Pipeline stack which uses cross-environment actions must have an explicitly set account'

See CONTRIBUTING for more information.

This library is licensed under the MIT-0 License. See the LICENSE file.