Connor
So during the lab, I was having some permissions issues, and updated the scopes for the instance. When the instance was stopped or restarted, I still received a 403. When i created a similar instance without any configuration changes, it succeeded. Does this imply the authentication token in the metadata service may not always be up to date with the configured permissions?