> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/data-security-documentation/cortex-data-security-data-sources-and-connectors/administration-and-troubleshooting/manage-instances/update-cloud-permissions-after-cortex-release-updates.md).

# Update cloud permissions after Cortex release updates

This topic provides guidance on how to manage permission updates for your cloud instances following new feature releases or bug fixes. It outlines how users are notified of required permission changes and provides step-by-step instructions for granting necessary permissions to ensure continued functionality and security.

{% hint style="warning" %}

* Ensure that the user account used to modify permissions has the necessary privileges within both the Cortex platform and your cloud environment, for example, AWS or Azure.
* You received a notification regarding a new version available that requires permission updates, or viewed a **Needs Update** status in the **Data Sources & Integrations** page.
  {% endhint %}

Procedure

1. Navigate to the **Data Sources & Integrations** page.
2. Do the following to identify instances requiring updates:

   1. For the relevant instance, locate the **Update Status** column.
   2. Filter or sort by this column to quickly identify instances marked as **Needs Update**. The message on the page indicates the number of instances that need updating.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Instances requiring updates will not change their connection status, for example, Connected, Warning, Error, Disabled, due to the pending permission update.</p></div>
3. Do the following to access the connector's permissions section:
   1. Click the name of the specific cloud connector instance that requires permission updates. The connector's detailed view appears.
   2. Within the connector's detailed view, locate and select the permissions section.
4. Review missing permissions. In the permissions section, the missing permission names or changes in permission scope is indicated.
5. Follow the on-screen instructions to grant the required permissions, or refer to the specific permission names or scopes provided.
6. After making the necessary permission adjustments, click **Save** or **Apply Changes** within the connector's configuration.
7. Return to the **Data Sources & Integrations** page and verify that the updated status of the instance shows as up-to-date, or the update is in progress.
8. Monitor the instance's health and functionality to confirm the changes have taken effect and the connector is operating as expected.

   If you encounter issues during the permission update process, check the generated health alerts for more specific details.


---

# 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://cortex-docs.paloaltonetworks.com/data-security-documentation/cortex-data-security-data-sources-and-connectors/administration-and-troubleshooting/manage-instances/update-cloud-permissions-after-cortex-release-updates.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.