: Known Issues in Panorama Plugin for AWS 5.0.0
Focus
Focus

Known Issues in Panorama Plugin for AWS 5.0.0

Table of Contents

Known Issues in Panorama Plugin for AWS 5.0.0

The following list describes known issues in the Panorama Plugin for AWS 5.0.0.

FWAAS-6633

A firewall commit might not be triggered after the first cloud device group config push from Panorama.
Workaround
: Retry the cloud device group config push from Panorama

FWAAS-6542

Selecting a different template stack for an existing Cloud Device Group is not supported. Despite allowing this operation, the template stack is not updated.

FWAAS-6540

The Panorama plugin for AWS incorrectly allows you to select template stacks from different tenants for existing cloud device groups.
Workaround: Do not associate template stacks for the same cloud device group across tenants.

FWAAS-6536

The cloud decive groups of all tenants might not be displayed when
All
is selected from the
Tenant
drop-down on the
Cloud Device Group
page in the Panorama plugin for AWS.
Workaround: To view the cloud device groups associated with a particular tenant, select that tenant from the
Tenant
drop-down.

PLUG-12882

Fixed in Panorama plugin for AWS 5.1.1.
When using Panorama Plugin for AWS, the CloudFormation template stack deployment fails when creating
AWS::EC2::VPCEndpointServicePermissions
. To resolve this issue, include the parameter
AllowedPrinciples
in
AWS::EC2::VPCEndpointServicePermissions
. For example, the template should resemble:
"VPCEndpointServicePermissions": { "Type" : "AWS::EC2::VPCEndpointServicePermissions", "Properties" : {
"AllowedPrincipals" : ["*"],
"ServiceId" : {"Ref": "VPCEndpointService"} }, "DependsOn": ["VPCEndpointService"] },

Recommended For You