> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/ce-release-notes/prisma-tm-cloud-compute-edition-release-information/release-notes-34-01-132.md). # 34.01.132 (Build 34.01.132) The following table has the release details: | Build | 34.01.132 | | ------------ | ---------------------------------------------------------------- | | Code name | Quinn Update 1 | | Release date | June 22, 2025 | | Type | Maintenance release | | SHA-256 | 7103025e0e5636e0517ebdc225ae59790a2e47b2fda24c7a993200d981c17dff | This 34.01.132 build is a maintenance release for Quinn Update 1 (34.01). The upgrade paths applicable to build 34.01.126 apply to this build as well. Review the [34.01 (build number 126) release notes](https://docs.prismacloud.io/en/compute-edition/34/rn/release-information/release-notes-34-01) for the upgrade paths and other details on the Quinn Update 1 release. Review the [system requirements](https://docs.prismacloud.io/en/compute-edition/34/admin-guide/install/system-requirements) to learn about the supported operating systems, hypervisors, runtimes, tools, and orchestrators. ## Addressed Issues
No default outbound access for Azure Agentless Scanning

Microsoft Azure is retiring the facility to provide default outbound access. See the Microsoft announcement for more details.

This change will adversely impact Prisma Cloud’s ability to perform Agentless Scanning. To mitigate this issue, Prisma Cloud agentless scanners will employ Network Address Translation (NAT) gateway to access the console.

To enable Prisma Cloud agentless scanners to use the NAT gateway, the following additional permissions have been added to the onboarding Terraform template:

  • Microsoft.Network/publicIPAddresses/read
  • Microsoft.Network/publicIPAddresses/write
  • Microsoft.Network/publicIPAddresses/delete
  • Microsoft.Network/natGateways/read
  • Microsoft.Network/natGateways/write
  • Microsoft.Network/natGateways/delete

This fix ensures that Prisma Cloud Compute uses NAT gateway for agentless scanning.

Enhanced AWS resource-level permissions for copying Amazon EBS snapshots

Amazon AWS has announced enhanced resource-level permissions for copying Amazon EBS snapshots. Please see the Amazon announcement for more details. This change impacts Prisma Cloud agentless scanning of AWS compute instances.

To avoid issues that can arise from this change, the following statement has been replaced in the onboarding CFT:

"Condition": {
            "StringEquals": {
                "aws:RequestTag/created-by": "prismacloud-agentless-scan"
                }
            },
            "Action": [
                "ec2:CopySnapshot"
            ],
            "Resource": [
                "arn:aws:ec2:*::snapshot/*"
            ],
            "Effect": "Allow",
            "Sid": "PrismaCloudPrismaCloudAgentlessCopySnapshot8"
        }

With this statement:

{
            "Condition": {
                "StringEquals": {
                    "aws:RequestTag/created-by": "prismacloud-agentless-scan"
                }
            },
            "Action": [
                "ec2:CopySnapshot"
            ],
            "Resource": [
                "arn:aws:ec2:*::snapshot/${*}"
            ],
            "Effect": "Allow",
            "Sid": "PrismaCloudPrismaCloudAgentlessCopySnapshot8"
        },
        {
            "Condition": {
                "StringEquals": {
                    "aws:ResourceTag/created-by": "prismacloud-agentless-scan"
                }
            },
            "Action": [
                "ec2:CopySnapshot"
            ],
            "Resource": [
                "arn:aws:ec2:*::snapshot/snap-*"
            ],
            "Effect": "Allow",
            "Sid": "PrismaCloudPrismaCloudAgentlessCopySnapshot9"
        }

This change ensures that Prisma Cloud uses the enhanced resource-level permissions announced by Amazon AWS.

The statement changes won’t be shown in the status message as the status check is performed only on the action parameter in the statement; not the other parameters.

--- # 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.prismacloud.io/ce-release-notes/prisma-tm-cloud-compute-edition-release-information/release-notes-34-01-132.md?ask=&goal= ``` `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.