> For the complete documentation index, see [llms.txt](https://docs.alphaus.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphaus.cloud/ripple/more-info/change-ri.md).

# RI のアロケーション変更

Ripple ではユーザーの所有している RI を自動で検出して表示します。\
新たに RI が購入されると、画面上に通知が表示されます。

通知をクリックすると、 `RI管理` の画面に遷移します。\
`•••` >  `RIの編集` より、アタッチするAWSアカウントを変更できます。

RIの所有者を変更し、Ripple 側でデータの再集計をし、その後、請求書の発行作業をすると、変更後のデータで計算されます。AWS上のRIの所有者は変更されません。

{% content-ref url="/pages/-LaOw1w8TkxYHcK\_cPxf" %}
[毎月の請求書発行の手順](/ripple/guide/routine.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.alphaus.cloud/ripple/more-info/change-ri.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.