Skip to content
v0.8.38GitHub

OVHcloudPolicy repair

Policy repair

Reapply the scoped access policies on existing OVHcloud buckets without touching their keys.

Applies to v0.8.38stable, released 4 November 2026Release notes →

Use --ovh-repair-policies when the buckets and keys already exist and you only need their scoped access policies applied again:

s3ctl \
--provider ovh \
--bucket netspeedy-archives \
--ovh-repair-policies \
--output json

Pass several --bucket values, or a batch file, to repair many bucket users in one run. For each bucket, s3ctl finds the container’s ownerId, checks the owner still looks bucket-dedicated, reapplies the OVHcloud container profile and imports a freshly generated S3 user policy. It doesn’t create, delete or rotate any keys.

To let a single bucket act as a replication target without changing any others, repair just that bucket with the replication profile:

s3ctl \
--provider ovh \
--bucket netspeedy-archives \
--ovh-storage-policy-role replication \
--ovh-repair-policies \
--output json

If a key may have been copied somewhere it shouldn’t be, repair the policy and then rotate, so the old key stops working:

s3ctl \
--provider ovh \
--bucket netspeedy-archives \
--ovh-rotate-credentials \
--output json

--ovh-repair-policies can’t be combined with --delete or --ovh-rotate-credentials.