I'm familiar with AWS in general, so the setup is not difficult. For people who struggle with IAM or role-based management, the setup can be challenging.

In cases where there is deep knowledge of creating a microservices architecture using AWS, a project can be executed quite fast. The only reason for using AWS is the aim for AWS Redshift as a data warehouse, the setup is not as easy.

The amount of time it takes to deploy depends on the project. We try to do our projects incrementally, so we start with one department and deploy all of the relevant data from that. It takes about two to three months to draft a minimum viable product, connect a couple of machines, and use Redshift to work with data consumed by analysis tools or reporting capabilities. It is possible to set up a data warehouse in one or two weeks.

There are different types of projects, and if we do it within a waterfall approach, it can take a long time.

When creating a data warehouse using Redshift, we first analyze the current situation and then sketch the architecture in AWS with the required ETL process to ingest and consume data, including the right processing to aggregate and enrich data according to business requirements. This is where all the customization comes in.

For deployment and maintenance for only one customer, I would say that three to six experienced people can handle the job. For maintenance work, in my opinion, there is only one person required for two or three hours a week maximum.

I would rate the setup as eight out of ten.

The initial setup is seamless. You just need an AWS account for the setup. I would rate my experience with the initial setup a nine out of ten, where one being difficult and ten being difficult to setup. 

The initial implementation of Amazon Redshift is simple. There was not anything difficult about getting started with the solution.

The initial setup wasn't very complex.

The setup was straightforward as I have a POC. It was a simple process.

The initial setup depends on who is doing it. In my opinion, it doesn't require much knowledge. Since we've been using it for a long time, it's much faster for me, but it might not be the same for others.

The initial setup is simple.

The solution is deployed on the cloud. The initial setup was pretty easy.

The initial setup is a complex process, especially for someone who is not familiar with nodes and configuring terms like RPUs. You need to consult the documentation to understand what an RPU is.

Moreover, Redshift can be difficult to maintain, especially the Redshift cluster instance.

Setup was difficult because I had to set up 25 connections with different users and passwords. The connections have been predefined, but there were still problems when trying to connect for the first time. I had some problems with some certifications that were malfunctioning. This might have had something to do with the functionality of my keyboard because if I pushed a random combination on the keyboard, it would delete the certificate from the folder and the connection wouldn't work. I think this is a problem with the remote desktop rather than with Redshift.

The initial setup is simple and we did not find it very complex at all.

The time it takes to deploy depends on how many tables you want to create, or how many tables will you merge the data with.

The tool's deployment is straightforward. You need to know what kind of clusters and nodes you want, how big they should be, and how much money you're willing to spend.

I would say Redshift needs a little more effort and expertise for setting up the kind of infrastructure one need. If you can do something with two-three people for Snowflake, you would need four people on Redshift. You need to have a little bit of knowledge of the AWS Cloud and AWS services to be able to use Redshift. A typical Redshift based Enterprise data work would need anywhere between 4 to 15 people.

It wasn't too complex because only a few people were needed to set up the solution.

The setup was quite complicated. For instance, if you use AWS Glue to automate loads into Redshift, setting up the security for the requirements between the two is complex. I've struggled a lot to set up the cluster on VPC and to get all the endpoints set up correctly with the right access and services. Especially from Glue's endpoints, I had to repeat the same process every time. It consumes a lot of time. In comparison, the CloudOps executives do the setup very quickly.

Amazon Redshift has a lot of documentation, but the setup is fine. Three years ago, the solution's deployment process took over a month or a month and a half.

Setting up Redshift is a little complex and requires some prior knowledge, whereas Azure's GUI is more intuitive and it's easier to navigate the steps.

The installation was easy.

Amazon Redshift is very easy to deploy, and deployment-wise, it's impressive. It only takes two to three minutes max to deploy.

The initial setup was straightforward. I rate it five out of five here.

Initial setup and configuration was pretty straightforward. First, we needed to create a Redshift cluster. Once the cluster was created, we created a database schema based on our need in the Redshift cluster.

We needed some help from experienced professionals for our initial setup. 

Setup was easy. This is a managed service, so you don't need to install anything. You just choose the size of the cluster and within 10 to 20 minutes, it's built.

I'm not using it day in, day out and I did not handle the initial setup. There is a team involved with that side of the product. I'm using it for the closing of the accounting cycle every month. I don't handle implementation tasks. 

The initial setup is very simple because it's a fully managed service and not much is required from the user's end.

The initial setup is easy. Just one or two clicks are needed to set up the solution.

It is not complex for a specialist because it is fairly well documented and systematic.

The specialists required by this product are what you will find in most enterprises. However, in a smaller organization, you might have to engage multiple parties with separate expertise to set it up correctly. For example, you will require somebody with experience in database migration to the cloud.

We went into the project with a design in mind and Redshift provided a great working platform. Our ETL tool helped us out in building the metadata and Birst built out many of the necessary tables.

Amazon Redshift is not as straightforward as other AWS tools but it is not that difficult.

I wasn't involved in the solution's initial installation. The deployment model is largely managed by our platform teams. Also, we have a team of engineers who constantly update and maintain the solution. Probably a team of engineers is specifically focused on improving our Amazon infrastructure.

The initial setup is straightforward. I do not recall, however, how long it took to deploy.

The deployment is very straightforward and it usually takes a couple of minutes. This is one of the reasons I like it.

As long as a person understands the AWS landscape, they can deploy it on their own. Otherwise, without realizing it, they might for example deploy a Redshift cluster that is not properly secure. Similarly, it could cost a lot of money if they don't know what they're doing. You don't need a very in-depth technical expertise, but you do need to understand how AWS works.

The initial setup was straightforward. The deployment took a few hours. 

The initial setup is straightforward, once you get used to it. There is a lot of documentation available.

The initial setup of Amazon Redshift is so simple and straightforward. We do not need to read or understand any of the technical documentation. Simply said, it’s a plug-and-play service or platform.

The big part when using Redshift is setting up the ETLs and doing the data cleaning. It was very hard when moving from MongoDB, because I had to re-discover our data schema (that had no spec). With that said, in both cases (moving from MongoDB and starting from scratch), I had a prototype up in about a day. By that I mean that I had the most important parts of my data loaded into Redshift and I could query it.

In my opinion, the setup was normal.

The setup was straightforward for those who know AWS.

Amazon Redshift is somewhat complex to deploy. The process could improve.

Your Redshift can be up and running with few clicks and in less than 5 minutes. A big benefit when you shift to cloud.

Setup of Redshift infrastructure is pretty straightforward. I’ve been told that setting up partitions can be tricky in order to ensure good performance.

Initial setup is very straightforward, very easy. No need of any side help.

In terms of the initial setup, as I said I've still not started using it, so I pray that it's going to be pretty easy for me to set it up.

The initial setup was straightforward.

The installation was straightforward and only required a few clicks.

The initial setup of the cluster was pretty straightforward. The following step, setting the right table configuration, was not so straightforward, though. It required an understanding of how the product works. Sort and distribution keys are required concepts to know about.

Redshift setup is easy. It's not an issue. 

The initial setup of this solution is straightforward.

The initial setup was straightforward.