> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/use/source-code/csp-changes.md).

# CSP changes

In release-6.0.0 SunbirdED is going with cloud agnostic. To achieve this SunbirdED has built the SDK to help all the service use same code base as much as it can.

1. Front-end SDK(Javascript) - SunbirdED team has created a node SDK that will be used by all the node services for implementing the cloud agnostic features. \
   \
   For more details please refer link\
   <https://github.com/Sunbird-Ed/client-cloud-services>
2. Backend SDK(JAVA) - SunbirdED Team has created a SDK in scala which is used by all the backend services to implement the cloud service features.\
   \
   &#x20;For more details please refer link\
   &#x20;<https://github.com/project-sunbird/sunbird-cloud-storage-sdk>
3. Large video(Chunk file upload) - The large video files are uploaded as chunks fron client-side(browser) itself. This logic will be different for each CSP provider. Hence for content editors, there is a [new library created](https://knowlg.sunbird.org/use/release-notes/release-5.5.0#crucial-note-regarding-csp-changes) to support this. So this logic will be specific to CSP provider and for any CSP if it is not supporting, please feel free to contribute to the library.\
   \
   &#x20;For more details please refer link\
   &#x20;<https://knowlg.sunbird.org/use/release-notes/release-5.5.0#file-upload-library>

SunbirdED has been tested in Azure Cloud provider and the application is working as expected.

&#x20;Environment Varibles - CSP&#x20;

### Environment Variables - CSP

```
cloud_service_provider
cloud_public_storage_accountname
cloud_public_storage_secret
cloud_public_storage_endpoint
cloud_public_storage_region

cloud_private_storage_accountname
cloud_private_storage_secret
cloud_private_storage_endpoint
cloud_private_storage_region
```

### CSP Implementation Table

Node SDK ([client-cloud-services](https://github.com/Sunbird-Ed/client-cloud-services))

<table><thead><tr><th>Cloud Provider</th><th width="174.33333333333331">Implemented</th><th>Tested</th></tr></thead><tbody><tr><td>Azure</td><td>Yes</td><td>Yes</td></tr><tr><td>AWS</td><td>Yes</td><td>No</td></tr><tr><td>GCP</td><td>Yes</td><td>No</td></tr><tr><td>OCI</td><td>Yes</td><td>No</td></tr></tbody></table>

&#x20;Java SDK ([sunbird-cloud-storage-sdk](https://github.com/project-sunbird/sunbird-cloud-storage-sdk))

<table><thead><tr><th>Cloud Provider</th><th width="174.33333333333331">Implemented</th><th>Tested</th></tr></thead><tbody><tr><td>Azure</td><td>Yes</td><td>Yes</td></tr><tr><td>AWS</td><td>Yes</td><td>No</td></tr><tr><td>GCP</td><td>Yes</td><td>No</td></tr><tr><td>OCI</td><td>Yes</td><td>No</td></tr></tbody></table>

Editor Plugin([sunbird-file-upload-library](https://github.com/Sunbird-Knowlg/sunbird-file-upload-library/tree/main))

<table><thead><tr><th>Cloud Provider</th><th width="174.33333333333331">Implemented</th><th>Tested</th></tr></thead><tbody><tr><td>Azure</td><td>Yes</td><td>Yes</td></tr><tr><td>AWS</td><td>No</td><td>No</td></tr><tr><td>GCP</td><td>No</td><td>No</td></tr><tr><td>OCI</td><td>No</td><td>No</td></tr></tbody></table>


---

# 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://ed.sunbird.org/use/source-code/csp-changes.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.