inmake DOCS
Docs / Cloud Instance / What gets set up

What gets set up

Databases, bucket, indexes and TTL the platform creates; the checklist; the states.

Every Connect and Re-check runs the same chain against your project and shows the result as a checklist.

What the platform creates#

When the key may (see Connecting for the roles), the platform creates what your project lacks, in your chosen destination:

  • the Firestore (default) database (Native mode),
  • the default Realtime Database instance,
  • the default Storage bucket (PROJECT_ID.firebasestorage.app),
  • the composite indexes and TTL policies the platform's queries need (for example the automatic expiry of abandoned carts),
  • the shim (The shim).

Creating a database takes a minute; the card shows "Creating the firestore (EU) — Re-check in a minute" meanwhile. Nothing that already exists is changed.

The checklist#

Row Needed for When it fails
Firestore, Realtime Database, Storage the data itself blocks Connected — created by the platform, or fixed with the printed role / API line
Indexes & TTL the platform's queries and expiry rules blocks — created through the key
Shim heartbeat writes in your project reaching the platform blocks until the shim runs
Shim deploy by platform the platform deploying the shim for you needs roles/iam.serviceAccountUser
Authentication, Auth config, Web apps, Sign-in providers, Analytics later features warnings only

States#

Chip Meaning
Not connected no cloud — projects use the shared cloud
Connecting… the chain is running or a create step is in progress
Blocked · reason a required row failed; the card prints how to fix it
Connected ready — new projects land in this cloud
Unreachable · reason the key was revoked, lost its roles, or the project is gone; its projects answer 503 org_unreachable until you fix it and Re-check (the platform re-checks hourly too)

The platform also re-checks unreachable clouds by itself every hour.