What is our primary use case?
We use it for storing and sharing any files that need re-authentication and access controls. We also use it for archiving a lot of stuff that we have – like our platform codes or specific passwords, SSH keys, and private keys. This way, we store them securely and share them properly within the services.
We use it as part of our object storage solution, and there are times when we also use it for infrastructure-as-code purposes. We can run the infrastructure stack from the bucket.
It's also being integrated with our DevOps processes – we link code in the bucket for continuous deployment and similar tasks.
How has it helped my organization?
We use it for backups and disaster recovery. It depends on the budget and requirements. Disaster recovery can be expensive for some, so they sometimes opt to use a bucket for DR purposes instead.
What is most valuable?
One key feature is that you can make buckets private, requiring pre-authentication and using a specific URL for access. Additionally, the buckets are encrypted by default. The flexibility of public or private buckets and how you grant access are vital security features.
So, a strong security model is the best part of the solution. Moreover, I find the bucket itself quite user-friendly.
What needs improvement?
Sometimes, there are glitches with applying policies. Even when the policy is correct, it might not work consistently. We need to troubleshoot to see if it's a user error or if the policy itself needs adjustment. It usually works after refreshing, but that inconsistency is a minor complexity.
For how long have I used the solution?
It is part of a project. We run the stacks from the bucket.
What do I think about the stability of the solution?
I haven't encountered any major difficulties with Object Storage itself.
What do I think about the scalability of the solution?
Currently, we don't store a massive amount of data, like images, so we're not really focused on the scalability aspect at the moment.
It's easy to manage. You can grant access to specific people, ensuring the data doesn't get into too many hands.
How are customer service and support?
I haven't had any issues requiring significant support.
How would you rate customer service and support?
How was the initial setup?
The installation is easy. It's not complicated. Maintaining the bucket itself is easy.
What about the implementation team?
People required for the process depends on the amount of data we're storing and how many buckets we have in use.
What was our ROI?
It hasn't had a significant impact. We mainly use it for backups, like code backups, infrastructure-as-code, and storing important keys.
We already have encryption and strict access policies in place, so it feels secure. We have a team that handles these aspects, but I don't think it has a major overall cost impact.
What's my experience with pricing, setup cost, and licensing?
Disaster recovery (DR) can be expensive. It depends on individual requirements. Some users with smaller DR needs might opt to use a bucket for backup if they want to save costs.
The pricing for Object Storage could be a bit lower. It's our primary storage solution, so a slightly more affordable price would be better.
What other advice do I have?
I'm still learning about other cloud platforms like AWS and Azure, which have very clean and user-friendly interfaces. Since I have more experience with Oracle, I might be a bit biased. But taking into account my technical understanding of how OCS works, it's very easy to use.
There are just occasional glitches where results don't appear as expected and need a refresh, which is the only barrier. So overall, I'd rate it a nine out of ten.
I would advise others to be aware of the pricing structure so that they can plan the buckets and storage space accordingly. Also, the ease of access and the ability to create separate private and public buckets are important factors to consider.
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
