AWS CloudFormation Action for GitHub Actions React Starter
This starter template contains a bootstrapped Create React App with a GitHub Workflow that deploys the app to the AWS Amplify Console using the AWS CloudFormation Action for GitHub Actions.
This project was bootstrapped with Create React App.
🔥 if you want to use a Create React App template, have a look at the Amplify + TypeScript template
Create a new repository from this template
Click the Use this template button above to create a new repository from this template.
This repository uses the template feature of GitHub.
You need your own AWS account to deploy the app to the AWS Amplify Console. Follow these steps if you do not have an account.
The AWS CloudFormation stack is deployed via AWS CloudFormation "Deploy CloudFormation Stack" Action for GitHub Actions.
When you create a new repository from the template, the GitHub Workflow is not setup. To setup the workflow, you need to follow these steps.
- Create a new personal token with full control of private repositories store it as encrypted secret
AMPLIFY_TOKENin the new repository. - Create a new IAM user in your AWS account with Programmatic Access and store the access key ID as
AWS_ACCESS_KEY_IDand secret access key asAWS_SECRET_ACCESS_KEYas secrets in your new repository. - (Optional) Configure a custom domain for your app by setting the
AMPLIFY_DOMAINsecret.
You need to run the Manual Deploy workflow to deploy it. You find the workflow by clicking Actions > Manual Deploy > Run workflow. When the popover opens, click Run workflow to trigger the deployment.
The manual triggers is a feature recently announced and avoids running the build process both on GitHub Action and AWS Amplify The stack is deployed to
us-east-1by default. Please change it to the region you want to deploy this to.
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. In the frontend environments is should show no builds. Click on Run Build to initialize the app.
This project was bootstrapped with Create React App.
Available Scripts
In the project directory, you can run:
npm start
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.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
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.
npm run eject
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.
Learn More
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
License
This library and the stack file are licensed under the MIT-0 License. See the LICENSE file.