Comment on page
When creating a new bucket, you should apply the following tools and settings to help ensure that your Oort DSS resources are protected.
To ensure proper security measures in Oort, it is recommended not to share root user credentials with employees who require access. Instead, individual access keys can be created for each user to enable programmatic requests to work with resources in your account.
Access keys are composed of an access key ID and a secret access key, which must be used together for authentication purposes. Oort allows up to ten access keys per account, making it easy to manage user access and maintain security.
At Oort DSS, we understand the importance of controlling access to your data. With our platform, you can easily set access permissions for each bucket to ensure that only authorized users can access, download, or write to the contents of the bucket.
By default, all buckets are set to private access only, which means that only users with the appropriate permissions can access the contents of the bucket.
However, if you need to host a website using the contents of the bucket, you will need to enable public access. When you choose to allow public access, anyone on the internet can read or write objects in the bucket. We advise our users to exercise caution when making a bucket public, and to ensure that only the necessary objects are made accessible to the public.
Oort DSS recommends that you disable all public access, but before applying any of these settings, ensure that your applications will work correctly without public access.