Skip to content

Commit cfc9bc3

Browse files
cyberchen98claude
andcommitted
docs: add missing screenshots for cloud-metadata and iam-role-assume pages
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1 parent 03a0936 commit cfc9bc3

File tree

3 files changed

+10
-0
lines changed

3 files changed

+10
-0
lines changed

cloud/iam-role-assume.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -144,6 +144,16 @@ After creating the sink or source, run a quick sanity check:
144144
| `AccessDenied` on S3 operations after assuming | The attached S3 policy is missing required actions | Add the missing S3 actions (see Step 1) |
145145
| `InvalidClientTokenId` | Incorrect IAM role ARN in the trust policy | Use the IAM role ARN from Cloud metadata |
146146

147+
## Managing allowed principals in RisingWave Cloud
148+
149+
To view and manage the IAM role ARNs that are authorized to access your project's resources via IAM Assume Role, go to your project in the [RisingWave Cloud Console](https://cloud.risingwave.com), click **Connection** in the left sidebar, and select the **Allowed Principals** tab.
150+
151+
<Frame>
152+
<img src="/images/cloud/iam-role-assume/connection-allowed-principals.png" alt="Allowed Principals tab in the Connection page of the RisingWave Cloud Console"/>
153+
</Frame>
154+
155+
Click **+ Add Principal** to add an IAM Role ARN that is allowed to access this project's resources.
156+
147157
## Related pages
148158

149159
- [Cloud metadata](/cloud/cloud-metadata) — retrieve the IAM role ARN for your project
170 KB
Loading
257 KB
Loading

0 commit comments

Comments
 (0)