https://github.com/exanubes/aws-code-pipeline-with-s3-deployment

Repository from exanubes.com for AWS Code Pipeline with S3 Deployment and Github Repository
https://github.com/exanubes/aws-code-pipeline-with-s3-deployment

aws aws-cloudfront-edge aws-code-build aws-code-deploy aws-code-pipeline cloudfront cloudfront-distribution github-webhook hosted-zones lambda-edge route-53 s3 s3-bucket s3-static-hosting

Last synced: about 22 hours ago
JSON representation

Repository from exanubes.com for AWS Code Pipeline with S3 Deployment and Github Repository

• Host: GitHub
• URL: https://github.com/exanubes/aws-code-pipeline-with-s3-deployment
• Owner: exanubes
• Created: 2022-02-19T10:15:50.000Z (almost 3 years ago)
• Default Branch: master
• Last Pushed: 2022-02-19T10:26:12.000Z (almost 3 years ago)
• Last Synced: 2024-04-17T02:33:01.762Z (9 months ago)
• Topics: aws, aws-cloudfront-edge, aws-code-build, aws-code-deploy, aws-code-pipeline, cloudfront, cloudfront-distribution, github-webhook, hosted-zones, lambda-edge, route-53, s3, s3-bucket, s3-static-hosting
• Language: TypeScript
• Homepage: https://exanubes.com/blog/aws-code-pipeline-with-s3-deployment-from-github-repository
• Size: 89.8 KB
• Stars: 4
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# AWS Code Pipeline with S3 deployment

Repository from [exanubes.com](https://exanubes.com) for [AWS Code Pipeline with S3 Deployment and Github Repository](https://exanubes.com/blog/aws-code-pipeline-with-s3-deployment-from-github-repository).

This repository is using AWS CDK v2 and is not compatible with AWS CDK v1 bootstrap stack.

## Commands:

Run the following commands for deploying and destroying the stacks

```

npm run cdk:deploy

npm run cdk:destroy

```

Both of these commands use the `aws-cli sts` service to get the account id and aws IAM role `exanubes-cloudformation-access` in order to dynamically provide role arn. Make sure you're using the account you want to deploy the stacks to and that you have the role created either with the same name or different name and change the scripts in `package.json`.