<p>Velero is installed in the cluster. At the installation velero was given credentials to s3 provider with <code>--secret-file</code> parameter and everything works fine. </p>

<p>Now I would like to create a new backup-location which will use buckets from a different s3 provider. When creating a backup location I pass to <code>--config</code> a key/value pair of <code>s3Url=...</code> But I can't seem to find a way to add a way to pass credentials to the new a3 provider. The <code>--secret-file</code> flag that worked at install is not accepted. </p>

<p>As the result when calling <code>backup create</code> with the new <code>--storage-location</code> the backup is created as failed. </p>

<p>My question is how I can give velero a way to authenticate itself with the new s3 provider? Is it even possible to create a new backup-location using s3 provider different that that used at velero install?</p>

BanzaiTokyo
<p>As far as I can see from <a href="https://github.com/vmware-tanzu/velero/labels/P2%20-%20Long-term%20important?page=2&amp;q=is%3Aopen+label%3A%22P2+-+Long-term+important%22" rel="nofollow noreferrer">Velero Issue Tracker</a>, they are working on fixing <strong><a href="https://github.com/vmware-tanzu/velero/issues/1064" rel="nofollow noreferrer">that issue</a></strong>, however it still hasn't been properly implemented.</p>
