> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/sdk-tools-home/sdk-and-tools-home/sdks/ruby-sdks.md).

# Ruby SDKs

Use the IONOS Cloud Ruby SDK to automate IONOS Cloud from Ruby apps and scripts.

### When to use the Ruby SDK

* Automation scripts and internal tooling.
* Integrations with Ruby services.
* Prototyping workflows quickly.

### Prerequisites

* An IONOS Cloud account.
* API access for your tenant.

### Authentication

Use the same credentials you use for the IONOS Cloud API.

Use environment variables or a secret manager.

### Common workflows

* Provision and tear down environments.
* Manage networking and storage operations.
* Build small tools for developers and operators.

### Troubleshooting

* Check credentials, permissions, and API reachability.
* Add retries for transient network errors.

### Next steps

* Use the REST API for direct HTTP usage.
* Use an IaC tool for repeatable provisioning.


---

# 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.ionos.com/cloud/sdk-tools-home/sdk-and-tools-home/sdks/ruby-sdks.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.