Error downloading: code 403 while update private Debian server

[vinay_datta]

set up details:
1. private Debian server

2. Artifact registry repo APT format

3. subnet is enables with Private Google Access

4. service account is provided with administrator access to Artifact registry

5. server given with full access to all cloud api access

https://cloud.google.com/artifact-registry/docs/os-packages/debian/configure#prepare-apt
i am following the above article to download the deb files from standard Artifact registry repo

please find the below sample cmds i followed

1. created a repo named: quickstart-apt-repo
2. Downloaded a sample Deb file in cloud shell : apt download apt-dpkg-ref
3. Set default repo in cloud shell: gcloud config set artifacts/repository quickstart-apt-repo
4. Set default location to : gcloud config set artifacts/location asia-south1
5. Run the gcloud artifacts apt upload to upload the package to the repository:
gcloud artifacts apt upload quickstart-apt-repo --source=apt-dpkg-ref_5.3.2_all.deb
6. Create a Debian VM.
7. Run gcloud init to initialize the Google Cloud CLI on your VM.
8. Update Apt: sudo apt update
9. Install the Apt credential helper on the VM to enable Apt to perform authentication: sudo apt install apt-transport-artifact-registry
10. check permissions of service account attached to the VM which sholud have editor access to Artifactory registry
11. Configure your VM to access Artifact Registry packages using the following command: echo 'deb ar+https://asia-south1-apt.pkg.dev/projects/xyz-ami-automation quickstart-apt-repo main' | sudo tee -a /etc/apt/sources.list.d/artifact-registry.list
12. Update Apt: sudo apt update

After the above update cmd i ended up with this error

Please help how to resolve this error

[lawrencenelson]

Hi @vinay_datta,

Welcome to the Google Cloud Community!

First, as initial troubleshooting steps, can you run through this document - Create standard repositories, and verify if you have configured the repository properly.

Thank you!

[armando_platik]

Leaving this here in case it helps somebody else later. I had a similar problem, if you have a VPC_SC perimeter then it is necessary to allow access for the remote to pull packages from upstream, view steps here: https://cloud.google.com/artifact-registry/docs/repositories/remote-repo#vpc