Create a GitHub Personal Access Token

Follow these steps to create a GitHub personal access token for AWS Amplify deployment:

1. Log in to GitHub: Go to github.com and sign in to your account.

2. Access Developer Settings:

   • Click on your profile photo in the top-right corner
   • Select "Settings" from the dropdown menu
   • Scroll down and click on "Developer settings" in the left sidebar
   • Click on "Personal access tokens" → "Tokens (classic)"

3. Generate a New Token:

   • Click "Generate new token" → "Generate new token (classic)"
   • Note: You may need to confirm your password

4. Configure Token Settings:

   • Token name: Enter a descriptive name (e.g., "AI SaaS Amplify Deployment")
   • Expiration: Choose an appropriate expiration (30 days, 60 days, or custom)
   • Scopes: Select the following permissions:
     • ✓ repo (Full control of private repositories)
     • ✓ admin:repo_hook (Full control of repository hooks)

5. Create Token:

   • Scroll to the bottom and click "Generate token"

6. Copy Your Token:

   • IMPORTANT: Copy the generated token immediately
   • GitHub will only show this token once
   • Store it securely for use in your .env file

Create Repository from Template

After purchasing the AI SaaS Boilerplate, you'll receive access to the GitHub template repository.

1. Navigate to the template repository URL
2. Click the "Use this template" button
3. Create a new repository in your GitHub account
4. IMPORTANT: Make sure to check the "Include all branches" checkbox
5. Choose a name for your repository (e.g., "my-ai-saas-platform")
6. Select visibility (private recommended)
7. Click "Create repository from template"

Clone Your New Repository

Clone the repository you just created to your local machine:

git clone https://github.com/your-username/your-repository-name.git
cd your-repository-name

Set Up the Development Branch Locally

The template repository comes with both main and dev branches. After cloning, set up tracking for the development branch:

git fetch origin dev
git checkout -b dev origin/dev

This ensures your local dev branch properly tracks the remote dev branch. By default, the deployment will target the dev branch since the default configuration uses stage=dev.

Navigate to the CDK Directory

The repository has a monorepo structure with separate folders for frontend, backend, and infrastructure (CDK). Navigate to the CDK directory where we'll configure the deployment:

cd cdk

Set Your Application Name in CDK Context

Open the cdk.json file in the cdk directory and update the app_name property in the context section:

{
  "app": "python3 app.py",
  "watch": {
    // watch configuration...
  },
  "context": {
    // Various AWS CDK configuration flags...
    "@aws-cdk/aws-lambda:recognizeLayerVersion": true,
    // More configuration flags...
    
    "app_name": "ai-saas"  // Change this value to your preferred application name
  }
}

You can keep the default name ai-saas or change it to your preferred application name.

Create Environment Variables File

Create a file named .env in your project's cdk directory:

# Environment Stage
STAGE=dev
 
# AWS Configuration
AWS_DEFAULT_REGION=eu-west-2
AWS_ACCOUNT_ID=123456789012
 
# Domain Configuration (Leave empty for initial deployment)
DOMAIN_NAME=
 
# GitHub Configuration (Required for Amplify Deployment)
GITHUB_OWNER=your-github-username
GITHUB_REPO=your-repository-name
GITHUB_TOKEN=your-github-personal-access-token
GITHUB_DEV_BRANCH=dev
GITHUB_PROD_BRANCH=main
 
# Stripe Integration (Placeholders for now)
STRIPE_API_PUBLIC_KEY=pk_test_placeholder
STRIPE_API_SECRET_KEY=sk_test_placeholder
STRIPE_WEBHOOK_SECRET_KEY=whsec_placeholder
 
# Google OAuth (Placeholders for now)
GOOGLE_OAUTH_CLIENT_ID=placeholder.apps.googleusercontent.com
GOOGLE_OAUTH_CLIENT_SECRET=placeholder_secret
 
# Google Analytics
GOOGLE_ANALYTICS_ID=G-PLACEHOLDER
 
# OpenAI API (Leave empty for initial deployment)
OPENAI_API_KEY=
 
# AWS Bedrock Configuration
AWS_BEDROCK_REGION=us-east-1