# Create a wasabi repo **URL:** \ **Category:** Support\ **Created:** [April 15, 2022, 3:59pm UTC](https://kopia.discourse.group/t/create-a-wasabi-repo/1048 "2022-04-15T15:59:55Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![cmartin](https://avatars.discourse-cdn.com/v4/letter/c/bb73d2/32.png) [@cmartin](https://kopia.discourse.group/u/cmartin)\ **Post date:** [April 15, 2022, 3:59pm UTC](https://kopia.discourse.group/t/create-a-wasabi-repo/1048/1 "2022-04-15T15:59:55Z")
Hi all, I’m new to kopia and I’m trying to create a new repo with Wasabi. For the life of me, I can’t find the right syntax to do so. I’ve tried several variants of the following without any luck. I’m using version 0.10.7 on linux for what it’s worth. Does anyone know the correct syntax to create a new repository with Wasabi? kopia repository create s3 --region [s3.us-west-1.wasabisys.com](http://s3.us-west-1.wasabisys.com) --bucket=mybucket --access-key=XXXXXXXXXXXXXXX --secret-access-key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ---
**Author:** ![cmartin](https://avatars.discourse-cdn.com/v4/letter/c/bb73d2/32.png) [@cmartin](https://kopia.discourse.group/u/cmartin)\ **Post date:** [April 15, 2022, 4:31pm UTC](https://kopia.discourse.group/t/create-a-wasabi-repo/1048/2 "2022-04-15T16:31:23Z")
I found the missing piece from another post. In case others ask this question, I needed the --endpoint option kopia repository create s3 -endpoint=[s3.us-west-1.wasabisys.com](http://s3.us-west-1.wasabisys.com) --bucket=mybucket --access-key=XXXXXXXXXXXXXXX --secret-access-key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ---
**Author:** ![Cyberboer](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/cyberboer/32/537_2.png) [@Cyberboer](https://kopia.discourse.group/u/Cyberboer)\ **Post date:** [November 28, 2022, 5:38pm UTC](https://kopia.discourse.group/t/create-a-wasabi-repo/1048/3 "2022-11-28T17:38:36Z")
Hi How has Kopia been treating you? Im looking at using it with wasabi as well on a Mint box and cloudberry and crashplan seems to be giving me a lot of issues lately with services failing to start. ---
**Author:** ![cmartin](https://avatars.discourse-cdn.com/v4/letter/c/bb73d2/32.png) [@cmartin](https://kopia.discourse.group/u/cmartin)\ **Post date:** [November 28, 2022, 6:20pm UTC](https://kopia.discourse.group/t/create-a-wasabi-repo/1048/4 "2022-11-28T18:20:19Z")
I’ve had zero issues with kopia since I got it working with Wasabi. Works great! ---
**Author:** ![dimejo](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/dimejo/32/287_2.png) [@dimejo](https://kopia.discourse.group/u/dimejo)\ **Post date:** [December 1, 2022, 2:35pm UTC](https://kopia.discourse.group/t/create-a-wasabi-repo/1048/5 "2022-12-01T14:35:51Z")
I’ve been using Kopia and Wasabi for a few months now and have had just 1 small issue. Kopia is reporting a repository size of 2.1 TB whereas Wasabi and rclone report 3.8 TiB. I don’t know if this is an issue with Wasabi or if Kopia is miscalculating this but besides this I’m really happy with the stability of this setup. ---
**Author:** ![Dan\_Medhurst](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/dan_medhurst/32/487_2.png) [@Dan\_Medhurst](https://kopia.discourse.group/u/Dan_Medhurst)\ **Post date:** [December 12, 2022, 10:39pm UTC](https://kopia.discourse.group/t/create-a-wasabi-repo/1048/6 "2022-12-12T22:39:21Z")
Wasabi has a 90 day retention on files / objects… so if they are deleted or changed before they’ve been stored for 90 days you’re still paying for that space for 90 days (which is why Wasabi is reporting more space used than Kopia) ---
**Author:** ![budy](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/budy/32/38_2.png) [@budy](https://kopia.discourse.group/u/budy)\ **Post date:** [December 13, 2022, 6:51am UTC](https://kopia.discourse.group/t/create-a-wasabi-repo/1048/7 "2022-12-13T06:51:46Z")
Have you checked, if you do include a lot of transient/cached/short-lived files in your snapshots? Seems to me, that this must be the case, since you’re packing quite a bit of “throughput” on your repo.