Task2 Automated deployment with cdk in python

.eslintignore

@@ -0,0 +1,4 @@
+node_modules
+public
+vite.config.ts
+serverless.yml

.eslintrc

@@ -0,0 +1,24 @@
+{
+  "root": true,
+  "parser": "@typescript-eslint/parser",
+  "parserOptions": {
+    "project": "./tsconfig.json"
+  },
+  "extends": [
+    "plugin:@typescript-eslint/recommended",
+    "plugin:react/recommended",
+    "plugin:react/jsx-runtime",
+    "plugin:prettier/recommended",
+    "prettier"
+  ],
+  "plugins": ["@typescript-eslint", "react", "prettier"],
+  "env": {
+    "browser": true,
+    "node": true
+  },
+  "settings": {
+    "react": {
+      "version": "detect"
+    }
+  }
+}

.gitignore

@@ -1,27 +1,33 @@
-# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+lerna-debug.log*
 
-# dependencies
 node_modules
-/.pnp
-.pnp.js
-
-# testing
-/coverage
-
-# production
-build
 .serverless
+coverage
+dist
+dist-ssr
+*.local
 
-# misc
+# Editor directories and files
+.vscode/*
+!.vscode/extensions.json
+.idea
 .DS_Store
-.env.local
-.env.development.local
-.env.test.local
-.env.production.local
-
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw?
 
-/.idea
-.vscode
+# cdk files
+.venv
+cdk.out
+__pycache__
+*.swp
+.env

README.md

@@ -1,45 +1,112 @@
-This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
+# AWS S3 & CloudFront Deployment
+
+## Deployed Application Links
+
+- **CloudFront URL:** [https://d1ahyogkj7onzu.cloudfront.net/](https://d1ahyogkj7onzu.cloudfront.net/)
+- **S3 Website URL:** [https://nodejs-aws-shop-react-438465144658-eu-west-1.s3.eu-west-1.amazonaws.com/](https://nodejs-aws-shop-react-438465144658-eu-west-1.s3.eu-west-1.amazonaws.com/) _(should return 403 Access Denied)_
+
+## Deployment Steps
+
+### Manual Deployment
+
+1. Created an S3 bucket and configured it for website hosting.
+2. Uploaded the MyShop! application manually.
+3. Configured CloudFront to serve the app securely.
+4. Invalidated CloudFront cache after making UI changes.
+
+### Automated Deployment with AWS CDK
+
+1. Created an AWS CDK stack to automate the deployment.
+2. The stack:
+   - Creates an S3 bucket.
+   - Configures a CloudFront distribution with OAI.
+   - Uses `BucketDeployment` to upload files automatically.
+   - Triggers CloudFront cache invalidation after deployment.
+3. Verified that `cdk destroy` removes all resources.
+
+## Important Notes!!!
+Always run bootstrap before the first deployment in a new AWS account/region
+
+- destroy and cleanup commands will remove AWS resources - use with caution
+
+- Use diff before deploy to review changes
+
+- quick-deploy is recommended for development iterations
+
+- Check doctor if you encounter any issues with deployment
 
 ## Available Scripts
 
-In the project directory, you can run:  
-You can use NPM instead of YARN (Up to you)  
+In the project directory, you can run the following npm commands:
+
+### Deployment Commands
+
+- `npm run deploy`
+  - Deploys the CDK stack to AWS without requiring manual approval
+  - Use this for initial deployment or updating existing resources
+
+- `npm run quick-deploy`
+  - Cleans the build directory and deploys the stack
+  - Useful when you want to ensure a fresh deployment
 
-### `yarn start` OR `npm run start`
+- `npm run destroy`
+  - Removes all resources created by the CDK stack
+  - Use with caution as this will delete all related AWS resources
 
-Runs the app in the development mode.<br />
-Open [http://localhost:3000](http://localhost:3000) to view it in the browser.
+### Setup and Maintenance
 
-The page will reload if you make edits.<br />
-You will also see any lint errors in the console.
+- `npm run bootstrap`
+  - Initializes the CDK toolkit stack in your AWS account
+  - Required before first deployment in a new account/region
 
-### `yarn test` OR `npm run test`
+- `npm run cleanup`
+  - Performs a complete cleanup of all resources and redeploys
+  - Useful when you need a fresh start
+  - Executes the following sequence:
+    1. Destroys the application stack
+    2. Removes CDK bootstrap resources
+    3. Cleans local CDK state
+    4. Bootstraps again
+    5. Deploys the stack
 
-Launches the test runner in the interactive watch mode.<br />
-See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.
+### Development and Debugging
 
-### `yarn build` OR `npm run build`
+- `npm run synth`
+  - Synthesizes CloudFormation templates from your CDK code
+  - Useful for reviewing what will be deployed
 
-Builds the app for production to the `build` folder.<br />
-It correctly bundles React in production mode and optimizes the build for the best performance.
+- `npm run diff`
+  - Shows the difference between deployed stack and current code
+  - Helpful before deploying changes
 
-The build is minified and the filenames include the hashes.<br />
-Your app is ready to be deployed!
+- `npm run list`
+  - Lists all stacks in the application
+  - Useful for verifying stack configuration
 
-See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.
+- `npm run doctor`
+  - Checks your CDK environment for potential issues
+  - Helpful for troubleshooting
 
-### `yarn eject` OR `npm run eject`
+### Cleanup Commands
 
-**Note: this is a one-way operation. Once you `eject`, you can’t go back!**
+- `npm run clean`
+  - Removes the CDK build output directory (cdk.out)
+  - Useful when you want to ensure a clean build
 
-If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.
+### Usage Examples
 
-Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
+```bash
+# First-time setup
+npm run bootstrap
 
-You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
+# Normal deployment flow
+npm run deploy
 
-## Learn More
+# Check changes before deployment
+npm run diff
 
-You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).
+# Complete reset and redeploy
+npm run cleanup
 
-To learn React, check out the [React documentation](https://reactjs.org/).
+# Remove all resources
+npm run destroy

cdk-infrastructure/.gitignore

@@ -0,0 +1,10 @@
+*.swp
+package-lock.json
+__pycache__
+.pytest_cache
+.venv
+*.egg-info
+
+# CDK asset staging directory
+.cdk.staging
+cdk.out

cdk-infrastructure/README.md

@@ -0,0 +1,58 @@
+
+# Welcome to your CDK Python project!
+
+This is a blank project for CDK development with Python.
+
+The `cdk.json` file tells the CDK Toolkit how to execute your app.
+
+This project is set up like a standard Python project.  The initialization
+process also creates a virtualenv within this project, stored under the `.venv`
+directory.  To create the virtualenv it assumes that there is a `python3`
+(or `python` for Windows) executable in your path with access to the `venv`
+package. If for any reason the automatic creation of the virtualenv fails,
+you can create the virtualenv manually.
+
+To manually create a virtualenv on MacOS and Linux:
+
+```
+$ python3 -m venv .venv
+```
+
+After the init process completes and the virtualenv is created, you can use the following
+step to activate your virtualenv.
+
+```
+$ source .venv/bin/activate
+```
+
+If you are a Windows platform, you would activate the virtualenv like this:
+
+```
+% .venv\Scripts\activate.bat
+```
+
+Once the virtualenv is activated, you can install the required dependencies.
+
+```
+$ pip install -r requirements.txt
+```
+
+At this point you can now synthesize the CloudFormation template for this code.
+
+```
+$ cdk synth
+```
+
+To add additional dependencies, for example other CDK libraries, just add
+them to your `setup.py` file and rerun the `pip install -r requirements.txt`
+command.
+
+## Useful commands
+
+ * `cdk ls`          list all stacks in the app
+ * `cdk synth`       emits the synthesized CloudFormation template
+ * `cdk deploy`      deploy this stack to your default AWS account/region
+ * `cdk diff`        compare deployed stack with current state
+ * `cdk docs`        open CDK documentation
+
+Enjoy!

cdk-infrastructure/app.py

@@ -0,0 +1,27 @@
+#!/usr/bin/env python3
+import os
+import aws_cdk as cdk
+from cdk_infrastructure.website_stack import WebsiteStack
+
+app = cdk.App()
+
+# WebsiteStack(app, "WebsiteStack",
+#     env=cdk.Environment(
+#         # account=os.getenv('CDK_DEFAULT_ACCOUNT'),
+#         # region=os.getenv('CDK_DEFAULT_REGION')
+#         account='438465144658',  # Replace with your AWS account number
+#         region='eu-west-1'              # Replace with your desired region
+#     )
+# )
+
+account = os.environ.get('CDK_DEFAULT_ACCOUNT', '438465144658')
+region = os.environ.get('CDK_DEFAULT_REGION', 'eu-west-1')
+
+WebsiteStack(app, "WebsiteStack",
+             env=cdk.Environment(
+                 account=account,
+                 region=region
+             )
+)
+
+app.synth()

cdk-infrastructure/bootstrap-config.json

@@ -0,0 +1,4 @@
+{
+  "version": "1",
+  "bootstrapBucketName": "cdk-bootstrap--"
+}

cdk-infrastructure/cdk-deploy-policy.json

@@ -0,0 +1,24 @@
+{
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "s3:*",
+                "cloudformation:*",
+                "cloudfront:*",
+                "iam:*",
+                "lambda:*",
+                "apigateway:*",
+                "logs:*",
+                "route53:*",
+                "ec2:DescribeAvailabilityZones",
+                "ec2:DescribeVpcs",
+                "ec2:DescribeSubnets",
+                "ec2:DescribeSecurityGroups",
+                "ssm:GetParameters"
+            ],
+            "Resource": "*"
+        }
+    ]
+}