Amazon AWS CloudSearch Reviews

It was an e-commerce website, which I think that it is self-explanatory how much you need to use photos how much you care about how long is to load a photo.

• Storage of photos and files which can be accessed anyplace, anytime, extremely quickly.
• More information (files) can be stored safely

CDN service, which reduces latency when accessing our web application it is a great earn in performance.

I think that currently it works very well. I mentioned the period of propagation on CDN servers. Sometimes, we update some photos or files and we don't see the update instantly. We need to wait for sometime, which is quite boring because we may be setting up a marketing campaign which is related to the product's photo and we need to wait to start.

Sometimes, with time to the propagation of the CDN.

Never any scalability issues.

Satisfactory.

The change was mainly because of the CDN servers.

It was quite easy because we have good knowledge, but the documentation of the product is excellent.

I would say that it is an investment.

Think about making good use of the tool, meaning: Look at your project or requirements and restructure thinking of the use of CloudSearch.

We have multiple teams in our organization that use the solution.

There are plenty of services from the database. There are many features that are valuable.

Scalability and agility are good.

The pricing is okay.

The quality of the solution is good.

The solution delivers well on optimization.

In terms of customization, it's quite good and can work with any other cloud platforms.

I don't have a deep knowledge of the solution and its compatibility, so I don't know if I can speak to what might be lacking.

Scalability and agility could be improved slightly, even though we find them good right now.

The solution should improve the recovery aspects that it has on offer.

I've been using the solution for two to three years now.

We also use Azure.

Since my role is restricted to security protocols, I don't have too much information on the deployment and implementation of this solution.

The solution is very cost-effective.

My role and responsibility is to check the services of the security platform in question to see if it fits the requirements. For example, there are members of our team who are looking to leverage some services from the public cloud, I just look at their business requirements and see what services they want to leverage on a solution.

Physically if there is something that is lacking in security that I can foresee, I explain the best practices to follow to enable additional security controls. This may be making stronger authentications, authorizations, or having stronger data security and encryption. 

I'd rate the solution nine out of ten.

Depending on an organization's requirements and budgets, cloud services would be recommended. A user must just decide what they need and stick to one thing.

We were able to build the core search functionality using this product.

• Document indexing
• Text-based search API
• Geospatial searches

Latlon data type only supports single value per document. All other types support multiple values. We faced issues with this because we had scenarios where, for each document, we needed to store multiple latlon values for different geographical locations.

No issues with stability.

Index cleanup is sometimes painful. No easy way to clean indexes or a bulk of documents. Full indexing or regeneration of entire indexes sometimes gets stuck. In one instance, we had to delete the entire index and re-create it.

This was the first implementation, we did not switch from any other product.

No setup required, as it is on cloud.

I was not involved with pricing and licensing, I was only involved in implementation.

I would suggest looking at Elasticsearch. I am currently using it and I feel it is more flexible and easy to use.

The best feature is its scalability in that Cloud is always on the fly. You can scale your requirements on the fly. Cloud also has other features but scalability comes first. This is one of the best features.

I think AWS is doing a good job. I don't think it needs much improvement. Security is a concern but they're working on it. I am not saying there is no security, but maybe they can bring in more controls.

I've been using AWS CloudSearch for three months.

The stability of the product is good.

As I mentioned, its scalability is its best feature.

We had a team of 15 - 20 people using it.

In terms of support, it's good - it's a market leader. Most of the issues are documented, so you really don't need support except for out of the ordinary stuff.

The initial setup is simple.

I'd definitely recommend Amazon AWS CloudSearch. On a scale of one to ten I'd rate it an eight.