> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdc-10.2-data-optimizer/pdso-install-landing-page/pdso-requirements/pdso-system-requirements/pdso-checklist-for-infrastructure-requests.md).

# Checklist for infrastructure requests

Perform the following tasks as needed to prepare your environment for Data Storage Optimizer:

* Request a Virtual Machine (VM) on Azure, AWS, or on-premises.
* Request IDs with remote access permissions to the VM on your cloud or on-premises.
* Request necessary access to systems, applications, and data sources.
* Request VDI or VPN access for Data Storage Optimizer data engineers to enable remote access to the VM.
* Request a database user account (service account) or logins for connecting to the data sources.
* Make sure the database user account has read-only permissions for the database objects.
* Make sure that your system owner or Database Administrator (DBA) has copied or extracted any required data or files.
* Obtain an SSL certificate from a certificate authority. If required by your organization's security policy, raise an infrastructure support request for an SSL certificate. The certificate authority will give you a key file and a certificate file.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdc-10.2-data-optimizer/pdso-install-landing-page/pdso-requirements/pdso-system-requirements/pdso-checklist-for-infrastructure-requests.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.