CU is using a non-ROSA cluster on OCP 4.12. When attempting to use OADP and Velero to create new backup snapshots, these fall into failed with the following outputs:

Line 4376: time="2024-08-21T13:02:28Z" level=error msg="Error getting volume snapshotter for volume snapshot location" backup=open-cluster-management-backup/resources-schedule-20240821130052 error="rpc error: code = Unknown desc = NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors" error.file="/remote-source/app/velero-plugin-for-aws/volume_snapshotter.go:67" error.function=main.getSession logSource="/remote-source/velero/app/pkg/backup/item_backupper.go:528" name=local-pv-4bb4747f namespace= persistentVolume=local-pv-4bb4747f resource=persistentvolumes volumeSnapshotLocation=test-1 Line 4387: time="2024-08-21T13:02:34Z" level=error msg="Error getting volume snapshotter for volume snapshot location" backup=open-cluster-management-backup/resources-schedule-20240821130052 error="rpc error: code = Unknown desc = NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors" error.file="/remote-source/app/velero-plugin-for-aws/volume_snapshotter.go:67" error.function=main.getSession logSource="/remote-source/velero/app/pkg/backup/item_backupper.go:528" name=local-pv-4c8ffe0e namespace= persistentVolume=local-pv-4c8ffe0e resource=persistentvolumes volumeSnapshotLocation=test-1 Line 4398: time="2024-08-21T13:02:40Z" level=error msg="Error getting volume snapshotter for volume snapshot location" backup=open-cluster-management-backup/resources-schedule-20240821130052 error="rpc error: code = Unknown desc = NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors" error.file="/remote-source/app/velero-plugin-for-aws/volume_snapshotter.go:67" error.function=main.getSession logSource="/remote-source/velero/app/pkg/backup/item_backupper.go:528" name=local-pv-da7e8490 namespace= persistentVolume=local-pv-da7e8490 resource=persistentvolumes volumeSnapshotLocation=test-1

This "NoCredentialsProvider" is inconsistent with what they are able to do elsewhere within the cluster, as all other actions that require communication with their S3 bucket are able to complete. Only when generating snapshots in this scenario is this occurring. Is there another location where credentials need to be defined for velero and are only used in the process of creating snapshots?