GitHub App vs PAT

Prefer the Amplify GitHub App

When you connect a repository in the Amplify Console, AWS walks you through installing the Amplify GitHub AppAmplify GitHub App
Amplify GitHub App - OAuth install that lets Amplify clone your repo and receive push/PR webhooks without a long-lived personal access token. on your user or organization.

That install:

• Grants Amplify permission to clone the selected repos
• Receives webhooks for pushes and pull requests
• Avoids storing a personal access token (PAT) in Amplify as the day-to-day credential

Private or public

Both work. The GitHub App must be allowed to access the repository:

• Public - easy to fork and screenshot; good for a published sample
• Private - fine for a personal lab; install the app with access to that private repo

Tip

For this walkthrough either visibility is valid. State which you chose when you create the sample so later screenshots match.

What not to do

• Do not paste a classic PAT into Amplify “for convenience” when the App connect flow is available
• Do not connect Amplify with Terraform for this lab - the lesson is the Console + App path