Bucket Access By default, access to a bucket is private. You can change this with the Public Access Override setting for a bucket. In addition, you can use a policy to make access available to: Specific IP addresses Public (any Internet user) By default, public use of a bucket, folder, or file is allowed only by certain paid (not trial) accounts. If your account does not have access to this feature, contact Wasabi Support at support@wasabi.com for assistance. Defining a Bucket Policy for Public Access As a precaution, a bucket intended for public access must have an associated policy. Before defining a policy, you may want to review the Policies feature and Bucket Policy information. The following is a sample policy that allows for public access to a bucket. Change the bucket name in the Resource section (arn:aws:s3:::YOURBUCKET, shown in the example below) to reflect

What are Object Tags? You can use tags to organize your objects (files). While folders are the first level of organization in a file system, tags add another dimension that can make objects easier to sort and find. Think of a tag as a keyword that you apply to an object. You can add up to 25 tags to an object. Each tag has two parts defined as a key/value pair: Key—must be a unique term used only once as a tag for the object Value—further describes the key For example:      Key=Tree / Value=Cherry      Key=Fruit / Value=Cherry The keys Tree and Fruit are unique terms. Both can be described with the same value (Cherry). Applying Tags Tags are applied to objects in several ways: When creating a bucket to apply tags t o all objects that you will upload into the bucket (as described below

Delete a Channel Account Id Removes a channel account with a specific id. URL (DELETE) /api/v1/channel-accounts/:id Query Parameters None Request Body None Response { "success": true, "code": "RES-I-####", "message": "Channel Account has been successfully deleted!", "data": null, "errors": null }

Wasabi addresses Controlled Unclassified Information (CUI) compliance by providing customers with the ability to to safeguard their CUI in accordance with Presidential Executive Order 13556 and 32 CFR Part 2002 . The CUI program requires that CUI be stored or handled in controlled environments that prevent or detect unauthorized access and limits and controls access to CUI within the workforce by establishing electronic barriers. Wasabi meets these requirements for handling CUI: Provides US Storage Regions Customers are responsible for creating and managing their users , access keys , roles , groups , and policies Customers are responsible for creating and managing their Root Users Supports Server-side encryption with customer-provided encryption keys (SSE-C ) Restricts access to the S3 bucket (s) containing CUI and downloads to customer-authorized users with valid access keys Customer Root Users are able to generate and download both administrative logs and bucket log s to review and track activity

Please note: As of the publishing of this article, the Wasabi Event Notification feature is only working in our us-east-1 region. Additional region support will be included in future updates. Wasabi has recently deployed a new feature called Event Notifications, which works with your current AWS account and utilizes the AWS SNS service to send notifications to a configured SNS target regarding selected events occurring within your Wasabi bucket. In order to configure Event Notifications on your Wasabi bucket, we need to first set up and configure a few things your AWS account: An IAM User with the proper permissions to perform actions against the AWS SNS service An SNS Topic A subscription to the above SNS Topic Once the above prerequisites are completed on the AWS account, we can then configure the following on your Wasabi account: Configure your AWS credentials with your Wasabi account (so that

You may create a user using the AWS CLI command aws iam create-user --user-name Bob When you do this, do not forget that you are referencing the iam endpoint rather than the s3 endpoint here. The command would look something like this: $ aws iam create-user --user-name mikeotestuser--endpoint-url=https://iam.wasabisys.com {     "User": {         "UserName": "mikeotestuser",         "Path": "/",         "CreateDate": "2019-09-18T16:04:37.031Z",         "UserId": "1PIFRFBITH1515N0TR3AL",         "Arn": "arn:aws:iam::100009912345:user/mikeo-test-iam"     } } $

By default, when a file is deleted from the source, WCN automatically deletes its replica from the bucket as well. You can set WCN to delete just the instance of the file on the source, but keep the copy on the bucket. In this case, to retrieve a file deleted only from the source, you have to manually synchronize the contents of the source and the bucket (see Synchronizing Data on the Source and the Bucket ). When you set WCN to delete just the instance of the file on the source, to delete it from the bucket as well you should access the bucket and manually delete the file. When using the default delete mode, keep in mind that the copy of the file on the bucket is deleted only after the specified time interval in the Data Replication policy elapses. Configure the Delete Mode Setting In the left pane

If you are a Wasabi Cloud Sync Manager (WCSM) user, this article is for you! Wasabi is excited to announce that all object replication functionality will be available in the Wasabi Console and API. As a WCSM user, this is what you saw: And this is what you will see with the Replications feature in Wasabi Console: What are the benefits of Replications moving to the Wasabi Console?  In addition to the convenience of having your replication management and storage in the same interface, you will have: Ability to filter replication jobs by object tags. Ability to filter replication jobs by a prefix. Improved performance.  Automatic bi-directional synchronization.  Ability to use replication with Wasabi's S3-compatible Wasabi API.  Replications in the Wasabi Console will be available to some customers starting December 1. Object replication is simple to use, requiring only a few clicks. Before you know it, your

Once the sub-accounts are created, the Acronis partner must map the Wasabi customer to the desired Acronis tenant. This enables the partner to create Wasabi buckets under the respective Acronis tenant and assign them to the backup locations. Follow the steps below to configure the mapping.  Navigate to the CUSTOMER MAPPING tab of the Wasabi App. This tab will list the sub-accounts and their mapping status. In the example below, a Wasabi sub-account is listed displaying a Not mapped status.  Click the checkbox next to the customer. Click + Map to existing customer tenant . In the Map existing customer dialog box, select the desired customer from the Select an Acronis customer drop-down menu.  Once the desired customer is selected, click Map . The Mapping will display the new status of the Wasabi sub-account and its mapped Acronis tenant. With the customer mapped, the partner can now navigate

Can I change the region of my bucket? When a Wasabi bucket s created, a specific region must be selected during the bucket creation process so that our system knows where to physically write the data for storage. For example, a region could be us-east-1 or eu-central-1. Once the region of the bucket is set, all data being written to that bucket will continue to be directed to the selected region for as long as the bucket exists. While you cannot move a bucket from one region to another, you may copy the data over and then remove the original bucket. What if my bucket already has data in it? If a bucket is already hosting data, then the data physically resides in our data center in the region the bucket was first created. In order to move that data from one region to another, the

If you have received your RCS overage invoice and need to pay this, you may now do this via the Payment Options tab of the Wasabi Management Console Billing Portal. The steps are easy and allow you to enter, add or edit your credit card on file. Then use the PAY NOW button in the Billing Portal to pay your Open invoice.  Adding Credit Card as RCS customer  Log into your account as usual After the you log in and are brought to the home page of the Wasabi Console, you should navigate to the ‘Billing tab’ on the bottom left of the console In the Billing portal you should see the open invoice If you select the arrow on the left side of the RCS invoice, overage invoice, one time fee invoice etc. It will show the details and an option in red to “PAY NOW” If you already

objects, but rather the result of hashing all the data object MD5s together (like the calculation done when multi-part objects are completed). Composed objects may not have user provided encryption keys. However, all data is stored encrypted at rest. There is a charge only for the metadata used in composed objects. The original data used in linked objects is charged at the normal rate until all composed objects that link to the original data object are deleted. Below is an example that composes a new object “TestCompose-Object-1” from three objects: “TestCompose-Data-1”, “TestCompose-Data-2”, and “TestCompose-Data-3”. PUT http://s3.wasabisys.com/my_bucket/TestCompose-Object-1?composeHTTP/1.1Content-Type:text/xml <ComposeRequest> <Component> <Key>TestCompose-Data-1</Key> </Component> <Component> <Key>TestCompose-Data-2</Key> </Component> <Component> <Key>TestCompose-Data-3</Key> </Component> </ComposeRequest> Appending to Objects AWS S3 does not offer

How do I use Veritas NetBackup with Wasabi? Wasabi has been certified for use with Veritas NetBackup.  Veritas NetBackup is a backup and recovery solution for cloud-ready enterprises. Follow the steps outlined below to integrate NetBackup with Wasabi Please Note:  The data restoration process is handled by your specific backup software application. As there are many potential variables that will affect your unique environment, it is strongly recommended that you seek the guidance of your backup software's technical support team in the event that you encounter difficulty, or have application-specific inquiries. 1. Reference Architecture 2. Prerequisites Veritas NetBackup v 8.3 and later An active Wasabi account   A bucket created in the Wasabi account 3. Adding support for Wasabi In order to use Wasabi with NetBackup v8.0 and above, two configuration packages need to be downloaded and installed on the NetBackup Server. This will display Wasabi

How do I use DropZone with Wasabi? DropZone is validated for use with Wasabi. This app is used on a Mac system to easily move/copy files to different services at fast speed. In order to use this with Wasabi, make sure you are using DropZone 2 or later. Earlier versions of DropZone do not have Amazon S3 support included. Start by Downloading DropZone using this link: https://aptonic.com/ . Once downloaded and Installed, Open DropZone and Click add a Grid. Select Amazon S3 to add Wasabi S3 connection. Enter Your Wasabi account details. Name: You can select any name for the connection Server URL: s3.wasabisys.com Access Key ID: Wasabi Access Key Secret: Wasabi Secret Access Key Bucket Name: Wasabi bucket name Folder: Directory inside the above mentioned bucket (optional) Note that this config example discusses the use of Wasabi's us-east-1 storage region. To use

Notification: We wanted to inform you that starting from March 13, 2023, Wasabi will alter its default security settings for customers who desire to create public buckets and objects. For newly created accounts, any buckets created after this date cannot be enabled for public access by the user via the console or CLI. Previously, buckets were always private by default, and trial accounts were unable to set their objects or buckets as public without prior request to support@wasabi.com .  For the majority of Wasabi use cases, public access is not required, and thus, no action is needed for most customers. We recommend that you make use of other options such as pre-signed URL's in order to share your documents (see How do I generate pre-signed URLs for temporary access with Wasabi? ). If, however, you have use cases that require public bucket access you may contact Wasabi

Why do I receive error message "the selected object storage does not support S3 Object Lock feature" in Veeam? When setting the Wasabi Veeam Object Lock Integration, you may encounter the error "the selected object storage does not support S3 Object Lock feature" when trying to set immutability inside Veeam Backup & Replication. This is an indication that Veeam was unable to validate Object Lock information about your bucket. Here is a list of things you can do in order to verify your setup is correct on Wasabi: Make sure that you have selected a bucket with the Object Lock feature enabled. Check that the Object Locking setting looks like the image below. It is not necessary to configure this, since Veeam Backup & Replication will automatically use Compliance object lock mode for each uploaded object. Veeam Backup & Replication uses an API call that will return information about the Object Lock setting

How do I use Masstech with Wasabi? Masstech is certified for use with Wasabi. The Masstech – Wasabi joint solution is described here . To use this product with Wasabi, please follow the configuration tips below. Ensure Masstech Virtual File System is installed and licensed. These instructions assume the virtual drive Z:/ is being used, but follow the instructions provided with the Masstech Virtual FileSystem installer to set the drive letter appropriate for your install. Open the Masstech Management Console. If there is not a shortcut installed, you can find the .msc in C:\Program Files\Masstech\VFS Open the Web interface in the console by left clicking on the VFS icon in the navigation tree. Then left click on the services icon (the 9 squares) The services banner will open. Left click on locations to setup Wasabi. Left click on Add New, and the wizard will start Enter a name and

From the Search Results page, you can use the Bulk Actions feature to apply custom data to one or more assets at a time. For more information on Bulk Actions, see Adding Assets With Bulk Actions . To select all assets on the page, click SELECT A BULK ACTION . Click SELECT ALL FILES ON PAGE . Optionally, to manage specific assets, check the box(es) in the lower right of each asset to manually select. Click SELECT A BULK ACTION . Click APPLY CUSTOM DATA . Click the drop-down menu to select a custom field. In the type field, enter a value for the custom field. This will apply the specified custom field value to all assets selected. Click APPLY FIELD VALUE . A message will confirm that the custom field value was successfully added to the asset(s).

I am unable to see the contents of my bucket in Wasabi Explorer or Cyberduck We have noticed an issue with some applications such as CyberDuck, MountainDuck, and Wasabi Explorer having issues displaying the contents of buckets that are using an all-numbered naming schema (i.e. "123456789"). For example, Wasabi Explorer will generate an "Failed to parse location-constraint." error: If you find that you are having similar issues with viewing the contents of your bucket, and your bucket name follows this schema, then please try one of the following steps to remedy the issue: Option 1: Rename the bucket to include additional character type We have found through testing that by renaming the bucket to include additional characters such as a letter or a dash can help remedy the issue. Please see the following screenshots for details on how to rename your bucket: In the Wasabi Console, click

When a new credit card is added to a Wasabi account, a small temporary authorization hold ($1.00) is sent to verify that the card is valid and hasn’t been reported lost or stolen. Wasabi doesn't proceed with the charge and the charge should disappear within three to five business days. The actual charge (which is based on the amount of usage) for your Wasabi services will be applied at the end of your billing cycle (which is 30 days by default) after you submit the card.  This auth hold process is comparable to the approach used by AWS and other leading service providers.