Cloud NGFW for AWS Addressed Issues
Table of Contents
Expand all | Collapse all
-
- About Cloud NGFW for AWS
- Getting Started from the AWS Marketplace
- Cloud NGFW for AWS Pricing
- Cloud NGFW for AWS Free Trial
- Cloud NGFW for AWS Limits and Quotas
- Subscribe to Cloud NGFW for AWS
- Cross-Account Role CFT Permissions for Cloud NGFW
- Invite Users to Cloud NGFW for AWS
- Manage Cloud NGFW for AWS Users
- Deploy Cloud NGFW for AWS with the AWS Firewall Manager
- Enable Programmatic Access
- Terraform Support for Cloud NGFW AWS
- Provision Cloud NGFW Resources to your AWS CFT
- Usage Explorer
Cloud NGFW for AWS Addressed Issues
Cloud NGFW for AWS addressed issues.
The following issues have been addressed at this release of Cloud NGFW for AWS.
ID | Description |
|---|---|
FWAAS-3009 | Cloud NGFW allows you to use an S3 bucket as a logging destination
for the NGFW resources. In AWS regions outside the US, Cloud NGFW
expects you to use the S3 buckets created in the same AWS region,
where you deploy the NGFW resources. |
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-6536 | Cloud NGFW fails to display all cloud device groups when
you select All on the Tenants page. If you select an
individual tenant, all cloud device groups appear in the list. |