Cloud Bigtable and IAM; A brief introduction

The access controls for Cloud Bigtable can be configured at the project, instance, or table level.

At the project level, you can do the following:

1. Allow a user to read from any table in any instance of the project but not write to those tables.

2. Allow a user to read from and write to any table in any instance of the project.

3. Allow a user to manage any instance within the project.

At the instance level, you can do the following:

1. Restrict a user to be able to read from development but not production instances.

2. Allow a user to read and write to development instances and read from production instances.

3. Allow a user to manage development instances but not production instances.

At the table level, you can do the following:

1. Allow a user to read from a table but not write to the table.

2. Allow a user to write to a table but not read from the table.

Cloud Bigtable has permissions that allow access to resources, such as instances, application profiles, clusters, and tables.

The predefined roles for Cloud Bigtable include Admin, User, Reader, and Viewer.

Anyone with the roles/bigtable.admin role will be able to administer any instance in a project, including creating new instances. The roles/bigtable.user role allows for read and write access to tables. The roles/bigtable.reader role allows for read-only access to data in tables. Someone with the roles/bigtable.viewer role is restricted to accessing the GCP console for Bigtable.