Following the documentation for deploying a CA PAM appliance in AWS or Azure:
the appliance is deployed in the corresponding VNET and given a Public IP to access.
However, in the network configuration for PAM, the gateway shows as 0.0.0.0 instead of the gateway for the Subnet where PAM has been deployed
This is normal: routing for PAM when deployed in these cloud platforms is taking care of by the underlying infrastructure, so no specification is needed here
CA PAM multiple releases
This is working as designed and no action must be taken