This blueprint creates a React SPA (single-page application) project. The project uses the Typescript AWS Cloud Development Kit (CDK) to deploy to Amazon Cloudfront + Amazon S3.

A (SPA) single-page application is a web application implementation that loads a web document and updates it by using JavaScript APIs. Your customers can then use your website without loading entire pages from the server, which helps improve your website's performance and provides a more dynamic user experience.

The deployment pipeline deploys the SPA to an Amazon CodeCatalyst environment. The Amazon CodeCatalyst environment requires an AWS account connection for your Amazon CodeCatalyst space and a configured IAM role for your project workflow. After you create your project, you can view the repository, source code, and CI/CD workflow for your Amazon CodeCatalyst project. After your workflow runs successfully, you can access your deployed CDK application URL in the output of your workflow.

React - powered by Create React App

Amazon Cloudfront + Amazon Simple Storage Service (Amazon S3)

For access to the underlying hosting resources you can host a SPA on Amazon Simple Storage Service (Amazon S3) and Amazon CloudFront.

• Amazon CloudFront – Amazon CloudFront is a web service that speeds up distribution of your static and dynamic web content, such as .html, .css, .js, and image files, to your users. CloudFront delivers your content through a worldwide network of data centers called edge locations for lower latency and improved performance.

• Amazon S3 – Amazon Simple Storage Service (Amazon S3) is an object storage service. You can use Amazon S3 to store and retrieve any amount of data at any time, from anywhere on the web.

You can create a new account connection from the AWS accounts menu in your Amazon CodeCatalyst space. AWS IAM roles added to the account connection are used to authorize project workflows to access AWS account resources.

Expected role capabilities: CodeCatalyst*

This project contains the following folders:

• root - The web application
• cdk - The CDK project to deploy the application

This project has created the following Amazon CodeCatalyst Resources:

• A source repository
• An environment
• A workflow for verifying pull requests at .codecatalyst/workflows/onPullRequestBuildAndTest.yaml
• A workflow for deploying changes pushed to main at .codecatalyst/workflows/onPushToMainDeployPipeline.yaml

To cleanup the resources created by this project delete the stack that CDK deployed. To delete the stack use the AWS CloudFormation console in the AWS account you associated when you launched the blueprint. To find the stack name refer to the workflow, if you used the default stack name it will be DevelopmentFrontendStack-XXXXX.

If you want to deploy without using CI/CD workflows, after building the app in the root directory you can move the build folder to the cdk/frontend folder by running:

mkdir cdk/frontend && cp -r build cdk/frontend

And then follow the instrucitons in the cdk folder README file.

See the Amazon CodeCatalyst user guide for additional information on using the features and resources of Amazon CodeCatalyst

This project was bootstrapped with Create React App.

In the project directory, you can run:

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

Note: this is a one-way operation. Once you eject, you can’t go back!

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.

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.

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.

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

To view the app