I'm trying to setup velero for multiple clusters in multiple AWS regions, although i'm using Github Actions and run backup in two different VMs, the EKS cluster at us-east-1
is taking backup without any issues, but not the cluster at ap-southeast-2
.
Below is my velero install command which i use and it's getting installed without any issues, but backup is failing for ap-southeast-2
cluster and in pod logs getting below error.
velero install \
--provider aws \
--plugins velero/velero-plugin-for-aws:v1.0.1 \
--no-secret \
--bucket $VELERO_BUCKET \
--backup-location-config region=$AWS_REGION \
--snapshot-location-config region=$AWS_REGION
Logs:
time="2021-08-02T13:57:30Z" level=info msg="Checking existence of namespace" logSource="pkg/cmd/server/server.go:337" namespace=velero
time="2021-08-02T13:57:30Z" level=info msg="Namespace exists" logSource="pkg/cmd/server/server.go:343" namespace=velero
time="2021-08-02T13:57:33Z" level=info msg="Checking existence of Velero custom resource definitions" logSource="pkg/cmd/server/server.go:372"
time="2021-08-02T13:57:37Z" level=info msg="All Velero custom resource definitions exist" logSource="pkg/cmd/server/server.go:406"
time="2021-08-02T13:57:37Z" level=info msg="Checking that all backup storage locations are valid" logSource="pkg/cmd/server/server.go:413"
An error occurred: some backup storage locations are invalid: backup store for location "default" is invalid: rpc error: code = Unknown desc = AccessDenied: Access Denied
status code: 403, request id: 1HE7G5DSTZ52KTZW, host id: z65l7EaF66KuZmIxYwWiysO2FaSU4udT39HmajfMii0wXxx6V4I3IoQ7RFwGQSPQAJBqCHcTPME=
Note: I have two buckets, one in us-east-1 for that region's cluster and ap-southeast-1 for Sydney region's cluster and both are public.