> For the complete documentation index, see [llms.txt](https://docs.impossiblecloud.com/impossible-cloud-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.impossiblecloud.com/impossible-cloud-help/impossible-cloud-storage-guide/cli-user-guide/aws-cli-for-cloud-to-cloud-migration-scenarios.md).

# AWS CLI for cloud-to-cloud migration scenarios

To begin, you will need to install the AWS CLI and configure it using your AWS Access Key and Secret Key. You can follow the instructions located [here](/impossible-cloud-help/impossible-cloud-storage-guide/cli-user-guide/aws-cli-installation-instructions.md) for guidance.

Once you have configured the AWS CLI, you must create an additional profile specifically for your Impossible Cloud Storage account. You can find detailed instructions on how to do this [here](/impossible-cloud-help/impossible-cloud-storage-guide/cli-user-guide/aws-cli-configuration.md).

Transfer all files from your source AWS bucket to a local directory by running the following command:

```
aws s3 --profile=your_source_cloud_profile cp s3://<source_bucket>/ <local_directory> --recursive
```

Finally, to transfer all of your files from a local directory to your new target bucket, run the following command:

```
aws s3 --profile=impossiblecloud --endpoint-url=https://eu-central-2.storage.impossibleapi.net cp <local_directory>/ s3://<destination_bucket>/ --recursive
```


---

# 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.impossiblecloud.com/impossible-cloud-help/impossible-cloud-storage-guide/cli-user-guide/aws-cli-for-cloud-to-cloud-migration-scenarios.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.