KKodaGuide
Guide/Connect cloud accounts

Connections

Connect cloud accounts

Connect Supabase, Google Cloud, or AWS in Integrations so Project Setup can link a backend. Credentials stay on this Mac and are never written into generated Swift.

01

Open Integrations

Integrations is the account-level place to connect cloud providers. After an account is connected here, open Set up the project backend to link it to one app.

  1. 1

    Open Integrations in the sidebar under Manage.

  2. 2

    Review the cards for Apple Developer, Google Cloud, AWS, and Supabase. Each shows Connected or Not connected.

    Integrations lists Apple Developer plus the backends Koda can deploy to: Google Cloud, AWS, and Supabase.
  3. 3

    Expand a card to consent, paste credentials, and connect. Credentials stay local to this Koda instance.

Good to knowApple Developer is for App Store uploads. Connect it when you are ready to Deploy your app. The other cards are for app data, secrets, and service proxies.

02

Connect Supabase

  1. 1

    Expand Supabase and review Consent & Access.

    Expand Supabase to consent, paste an Access Token, connect, and confirm your projects appear in the list.
  2. 2

    Check I consent to Koda acting on my behalf in Supabase.

  3. 3

    Create a personal access token in your Supabase account settings, then paste it into Access Token.

  4. 4

    Select Connect Supabase.

  5. 5

    Review the projects list to confirm Koda can see the expected workspace, then return to Set up the project backend to create or link a project.

03

Connect Google Cloud

  1. 1

    Expand Google Cloud and review the recommended permissions. Project discovery needs Resource Manager read access. Runtime deploy also needs scoped Cloud Run, Cloud Build, Artifact Registry, IAM, and Secret Manager permissions.

    Connect Google Cloud with a service account or access token. Credentials stay on this Mac and are used only for actions you trigger.
  2. 2

    Check I consent to Koda acting on my behalf in Google Cloud.

  3. 3

    Choose Authentication method: Service account (client email and private key) or OAuth access token.

  4. 4

    Select Connect Google Cloud. Koda saves the credentials locally and can then list projects in Project Setup.

  5. 5

    If billing is disabled, Koda shows a billing message with Open billing settings. Enable billing, then try again.

04

Connect AWS

  1. 1

    Expand AWS and review the recommended permissions. Linking an account needs STS GetCallerIdentity. Runtime deploy later uses scoped Lambda, API Gateway, Secrets Manager, DynamoDB, and IAM permissions.

    Connect AWS with an access key. Koda keeps the secret on this Mac and uses it for account linking and later Lambda deploys.
  2. 2

    Check I consent to Koda acting on my behalf in AWS.

  3. 3

    Paste the Access key ID and Secret access key from AWS IAM.

  4. 4

    Select Connect AWS. Koda validates the account and saves the keys locally.

  5. 5

    Return to Set up the project backend to choose the account and region for this app.

05

Disconnect safely

  • Use Clear, Clear Key, or the matching disconnect control on a card to remove Koda’s saved credentials. This does not delete projects in Supabase, Google Cloud, or AWS.
  • Reconnect after you rotate a token or key so future backend work continues to work.