# Stratus Configurations -------------------------------------------------------------------------------- title: "General Settings" description: "Stratus is a robust cloud storage solution powered by Catalyst. You can store data of any format type in the form of buckets and objects." last_updated: "2026-09-02T11:24:40.107Z" source: "https://docs.catalyst.zoho.com/en/cloud-scale/help/stratus/stratus-config/general-settings/" service: "Cloud Scale" related: - Create a Bucket (/en/cloud-scale/help/stratus/buckets/create-bucket/) - Upload an Object (/en/cloud-scale/help/stratus/objects/upload-object/) - Java SDK (/en/sdk/java/v1/cloud-scale/stratus/overview/) - Node.js SDK (/en/sdk/nodejs/v2/cloud-scale/stratus/overview/) - Python SDK (/en/sdk/python/v1/cloud-scale/stratus/overview/) - Web SDK (/en/sdk/web/v4/cloud-scale/stratus/overview/) - iOS SDK (/en/sdk/ios/v2/cloud-scale/stratus/overview/) - Android SDK (/en/sdk/android/v2/cloud-scale/stratus/overview/) - Flutter SDK (/en/sdk/flutter/v2/cloud-scale/stratus/overview/) - REST API (/en/api/code-reference/cloud-scale/stratus/get-all-buckets/#GetAllBuckets) -------------------------------------------------------------------------------- # General Settings While you are creating and after you create a bucket, you can configure the following bucket settings: <br /> ### Versioning <br /> - This setting allows you to store multiple versions of any object in your bucket. - When you upload multiple versions of the object, Catalyst will generate a unique versionId for each of them upon upload. - Every latest version that you upload will become the default version of the object. The previously uploaded versions will need to be accessed using their unique versionId. - Consider you disable Versioning after uploading versions of the object when Versioning was enabled. All the object versions that had been uploaded so far will exist. However, if you attempt to upload a version of the same object under this condition (Versioning is **disabled**), the following behavior is expected: - The original object will be permanently deleted and replaced with the object you are uploading (**latest object**). - You will only be able to access the latest object and the saved versions of the object (using their respective versionId). - The diagrams below illustrate *Versioning* behavior: - When Versioning is **enabled**. <br /> Every new version of the object will be stored in the bucket and will be referred using its unique versionId generated by Stratus. - When Versioning is **disabled**. <br /> The original object and its versions will be retained in the bucket. - When you **upload an object version** after **Versioning has been disabled**. <br /> The original object will be permanently deleted and replaced with the object you are uploading (**latest object**), and you will only be able to access the latest object using the Object URL, and the saved versions (referred using their respective versionId) of the object. <br /> <!--### Caching <br /> - This setting allows Catalyst to cache some of the objects that you access using the **Caching URL** to make object retrieval easier. - Once you enable caching, it will take up to **two minutes** for it to enable, and a **Caching URL** will be generated by Stratus. - If you have enabled Caching for an *Authenticated bucket*, to access the cached objects using the **Caching URL**, you need to first **sign the Caching URL** using the **Sign Cached URL SDK**: Java, Node.js, and Python. The signing of the Cached URL needs to be done **every one hour**, and it can only be done by your **Administrator** or **Super Administrator**. - If you decide to **purge** (delete your cache), you have the option to either purge the cache of all the objects, or just of specific objects. - The default permission template you used to create your bucket will also be applied to the cache of the objects in your bucket. For example, if the permission template used to create the bucket is *Public*, then the cache of the objects will also be in the *Public* permission template.--> ### Data Encryption - You can enable this bucket setting to encrypt the data present in the bucket. - Stratus follows both encryption at rest and encryption at flight protocols. - Stratus applies the Advanced Encryption Standard (AES-256) encryption technique to encrypt the data in the bucket. ### PII/ePHI - You need to enable this setting if the bucket is going to contain sensitive or personally identifiable data. Doing so, will ensure you are storing these types of sensitive data in compliance with HIPAA standards. - When this setting is enabled, the object's operational logs will be present in the Application Logs present in the Audit Logs section. ### Enable a Bucket's Setting Note: By default, all these bucket settings will be disabled. Even when you migrate your bucket from a third-party platform to Stratus, these configurations will have to be re-configured. To enable one of the settings: 1. Click on the required bucket. <br /> 2. Click the **Configurations** tab. <br /> 3. Expand the **General Settings** section. <br /> 4. Click the ellipsis icon in the required setting's tile, then click **Enable**. <br /> 5. Click **Enable** in the prompt to confirm. <br /> The required setting will be enabled. <br /> ### Disable a Bucket's Setting To disable a required setting: 1. Click the ellipsis icon in the setting's tile, then click **Disable**. <br /> 2. Click **Disable** in the prompt to confirm. <br /> The required setting will be disabled. <br /> -------------------------------------------------------------------------------- title: "Signals Triggers" description: "Stratus is a robust cloud storage solution powered by Catalyst. You can store data of any format type in the form of buckets and objects." last_updated: "2026-09-02T11:24:40.108Z" source: "https://docs.catalyst.zoho.com/en/cloud-scale/help/stratus/stratus-config/event-triggers/" service: "Cloud Scale" related: - Create a Bucket (/en/cloud-scale/help/stratus/buckets/create-bucket/) - Upload an Object (/en/cloud-scale/help/stratus/objects/upload-object/) - Signals Help Documentation (/en/signals/) - Circuits Help Documentation (/en/serverless/help/circuits/introduction/) - Java SDK (/en/sdk/java/v1/cloud-scale/stratus/overview/) - Node.js SDK (/en/sdk/nodejs/v2/cloud-scale/stratus/overview/) - Python SDK (/en/sdk/python/v1/cloud-scale/stratus/overview/) - Web SDK (/en/sdk/web/v4/cloud-scale/stratus/overview/) - iOS SDK (/en/sdk/ios/v2/cloud-scale/stratus/overview/) - Android SDK (/en/sdk/android/v2/cloud-scale/stratus/overview/) - Flutter SDK (/en/sdk/flutter/v2/cloud-scale/stratus/overview/) - REST API (/en/api/code-reference/cloud-scale/stratus/get-all-buckets/#GetAllBuckets) -------------------------------------------------------------------------------- # Signals Triggers Catalyst Signals is a powerful event bus service that listens for the occurrences of pre-determined events and automatically executes associated Event functions, or the targeted Circuits. In Stratus, you can configure the required rule to trigger Catalyst Signals at the event of an: * Object Upload * Object Download * Object Update * Object Delete Note: Ensure that you go through the following help documentation to use this configuration effectively: * Catalyst Signals: Help * Catalyst Publishers: Help * Create a Rule in Signals: Help * Circuits: Help * Event Functions: Help ### Create Signals Rules in Buckets To create a Signals rule in Stratus: 1. Click on the required bucket. <br /> 2. Click the **Configurations** tab. <br /> 3. Expand the **Signals** section and click **Add Rule**. <br /> 4. Provide a name and description for the rule. <br /> 5. Select the action or actions that is supposed to trigger Signals from the **Action** drop-down. <br /> 6. Choose your required **Target Point**. Based on this selection, either an *Event Function* or a *Circuit* will be triggered when the selected actions occur. Note: * Before you choose a target point, make sure the required target event function or target circuit is configured and deployed to the catalyst console. Only if you deploy the required Target Point to the console will it be available in the Target Function or Target Circuit drop-down. * The Circuits component is currently not available to Catalyst users accessing from the EU, AU, IN, or CA data centers. Hence, users from these DCs will not be able to trigger Circuits using the Stratus component. <br /> 7. Choose the required event function from the **Target Function** drop-down. <br /> Note: * If you still have not coded and deployed the required Event Function, click the Create Event Function button. You will be directed to the Serverless section of the console, and follow the steps listed in this help documentation to create an event function. * If you have initialized the required function using the Catalyst CLI, ensure you deploy the function to the Catalyst console once you have coded your required business logic. 8. Click **Create**. <br /> The rule will be created, and the Signals rule will be enabled. <br /> 7. Choose the required circuit from the **Target Circuit** drop-down. <br /> Note: If you have not yet coded and deployed the required functions for the Circuit and created it, click the Create Circuit button. You will be directed to the Serverless section of the console, and follow the steps listed in this help documentation to create a Circuit. 8. Click **Create**. <br /> The rule will be created, and the Signals rule will be enabled. <br /> ### Edit a Signals Rule To edit a Signals rule: 1. Click the ellipsis icon next to the rule, then click Edit. <br /> 2. Make the required edits and click **Update**. <br /> The changes will be applied. <br /> ### Disable a Signals Rule To disable a Signals rule: 1. Click the ellipsis icon next to the rule, then click **Disable**. <br /> 2. Click **Disable** in the prompt to confirm your action. <br /> The rule will be disabled. <br /> ### Delete a Signals Rule To delete a Signals rule: 1. Click the ellipsis icon next to the rule, then click **Delete**. <br /> 2. Click **Delete** in the prompt to confirm your action. <br /> The rule will be deleted. <br /> -------------------------------------------------------------------------------- title: "Bucket CORS" description: "Stratus is a robust cloud storage solution powered by Catalyst. You can store data of any format type in the form of buckets and objects." last_updated: "2026-09-02T11:24:40.109Z" source: "https://docs.catalyst.zoho.com/en/cloud-scale/help/stratus/stratus-config/bucket-cors/" service: "Cloud Scale" related: - Create a Bucket (/en/cloud-scale/help/stratus/buckets/create-bucket/) - Upload an Object (/en/cloud-scale/help/stratus/objects/upload-object/) - Java SDK (/en/sdk/java/v1/cloud-scale/stratus/get-bucket-cors/) - Node.js SDK (/en/sdk/nodejs/v2/cloud-scale/stratus/get-bucket-cors/) - Python SDK (/en/sdk/python/v1/cloud-scale/stratus/get-bucket-cors/) - Web SDK (/en/sdk/web/v4/cloud-scale/stratus/overview/) - iOS SDK (/en/sdk/ios/v2/cloud-scale/stratus/overview/) - Android SDK (/en/sdk/android/v2/cloud-scale/stratus/overview/) - Flutter SDK (/en/sdk/flutter/v2/cloud-scale/stratus/overview/) - REST API (/en/api/code-reference/cloud-scale/stratus/get-all-buckets/#GetAllBuckets) -------------------------------------------------------------------------------- # Bucket CORS Cross-origin Resource Sharing (**CORS**), is a feature of Stratus that you can use to whitelist certain domains that require access to the objects stored in your bucket. You can authorize applications you have hosted using Catalyst AppSail, or even applications you have hosted on third-party platforms to access objects stored in Stratus. <br /> You can authorize and whitelist the required domains directly in the console and approve the domains to access objects from your buckets. This operation can be performed in the development environment and your configurations can be migrated to the production environment. ### Whitelist Domains Using Bucket CORS To authorize a domain for CORS: Click on the required bucket. <br /> 2. Click the **Configurations** tab. <br /> 3. Expand the **Bucket CORS** section and click **Add Domain**. <br /> 4. Enter the complete URL of the domain you need to enable CORS for, with the required **Request Method** (GET, POST, PUT, DELETE, or HEAD). <br /> 5. Click **Add** to whitelist the required domains. <br /> The required domain will be whitelisted and CORS will be enabled for the required domain. <br /> Note: CORS of a bucket can be edited by any user that has or has been granted Write permission for Stratus component in the project, using the Profiles & Permissions section. ### Edit Bucket CORS To edit bucket CORS: 1. Click the ellipsis icon next to the domain and click **Edit**. <br /> 2. Make the required changes and click **Update**. <br /> The changes will be applied. <br /> ### Delete Bucket CORS To disable or remove a domain from the whitelist: 1. Click the ellipsis icon next to the domain and click **Delete**. <br /> 2. Click **Confirm** to delete the domain. <br /> The domain will be deleted, and will no longer be whitelisted.