# Issues with configuring backup against S3 storage

**URL:** <https://forums.percona.com/t/issues-with-configuring-backup-against-s3-storage/34970>\
**Category:** Percona Operator for PostgreSQL\
**Created:** [November 12, 2024, 8:37pm UTC](https://forums.percona.com/t/issues-with-configuring-backup-against-s3-storage/34970 "2024-11-12T20:37:17Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![92fnko](https://avatars.discourse-cdn.com/v4/letter/9/a698b9/32.png) [@92fnko](https://forums.percona.com/u/92fnko)\
**Post date:** [January 13, 2025, 7:42am UTC](https://forums.percona.com/t/issues-with-configuring-backup-against-s3-storage/34970/10 "2025-01-13T07:42:07Z")

</div>

I was wrong. pgBackRest uses `host` as the default path style for S3 ([pgBackRest - Configuration Reference](https://pgbackrest.org/configuration.html#section-repository/option-repo-s3-uri-style)).

I also was under the impression that I could use `https://hostname:port` under `spec.backups.pgbackrest.repos.0.s3.endpoint` like many other apps, but the port needs to be in a separate parameter (`repo1-storage-port`, thanks @Superhammer).

We have now migrated to HTTPS, but I think @Superhammer is on to something… I also would appreciate it if the official documentation was more complete on these basic things…

The below works, but now the final boss - how do I import the necessary CAs to trust the connection ([Include CAs for backup](https://forums.percona.com/t/include-cas-for-backup/36076))?

```yaml
  spec:
    backups:
      pgbackrest:
        ...
        global:
          repo1-s3-uri-style: path
          repo1-storage-port: "9000"
          repo1-storage-verify-tls: "n"
        ...
        ...
        repos:
        - name: repo1
          s3:
            bucket: <REDACTED>
            endpoint: s3.domain.com # this is just an example
            region: minio
        ...

```

---

_[View the full topic](https://forums.percona.com/t/issues-with-configuring-backup-against-s3-storage/34970)._