docs
GitHub CI/CD Deployment
Add Variables

Add Your Real GitHub Actions Variables 🔐

Now it’s time to add the actual values to GitHub Actions. If you’ve destroyed your resources using cdk destroy, make sure to redeploy them (this is a good opportunity to practice again 🚀).

Start by running cdk bootstrap to ensure everything is set up properly before proceeding and then cdk deploy.

Adding Variables

Let's start by adding variables.

Create Permission Set

⚠️ Use the same AWS_QUALIFIER as you did for cdk bootstrap --qualifier.

⚠️ Don't just copy paste above example values.

For example, use your own domain names and github values.

Common Variables:

  • AWS_QUALIFIER: A unique identifier to distinguish between resources or stacks within the same account.

  • AWS_REGION: Defines the AWS region where your services are deployed.

Production Variables:

  • PROD_DOMAIN_NAME: The domain name associated with the production environment.

  • PROD_SUBDOMAIN: The subdomain associated with the production environment.

  • PROD_ENVIRONMENT: Defines the environment type, set to production.

  • PROD_GITHUB_ORG: Defines the GitHub organization or user where the production repository resides.

  • PROD_GITHUB_REPO: Specifies the GitHub repository name for the production environment.

  • PROD_GITHUB_BRANCH: Specifies the GitHub branch from which the production environment will be deployed.

Staging Variables:

  • STAGING_DOMAIN_NAME: The domain name associated with the staging environment.

  • STAGING_SUBDOMAIN: The subdomain associated with the staging environment.

  • STAGING_ENVIRONMENT: Defines the environment type, set to staging.

  • STAGING_GITHUB_ORG: Defines the GitHub organization or user where the staging repository resides.

  • STAGING_GITHUB_REPO: Specifies the GitHub repository name for the staging environment.

  • STAGING_GITHUB_BRANCH: Specifies the GitHub branch from which the staging environment will be deployed.

Secrets/VariablesAdd Secrets