Source anchor AWS Workspaces to publishers?

Thank you in advance - as a security measure, I was wondering if rather than bypassing traffic to AWS Workspaces from Netskope, might it be possible instead to source anchor traffic from our AWS Netskope publishers and configure IP restrictions from the AWS-end, such that access to our Workspaces tenant was restricted to our AWS/Netskope publishers? We’d ideally only like for access to AWS Workspaces to be driven from Netskope client-driven endpoints.