The experience with the initial setup depends on your familiarity with cloud computing. Personally, with these solution, I've had no issues in terms of deployment, troubleshooting, and conducting various activities. It's been smooth for me.

The initial setup of this solution is very quick and easy, and is all carried out online with guidance.

I think the initial setup was very easy. That's the power of using cloud technologies. You can create an EC2 instance in just a few minutes. It's set up, deployed, and automated very easily.

It takes only 10 to 15 minutes to initiate my instance. I work mostly in a development environment so I can manage it as just a development or staging environment. The production environment is managed by another team for security reasons.

I'm unsure of whether Amazon EC2 is easy or complex to set up.

I have experience with this product so the initial setup is easy for me. Some small businesses have their IT people, but others don't have the knowledge so I carry out an assessment for them. My medium sized clients have a couple of IT people who maintain the network side of things and the instances or the server aspect. If they have applications, then they have their own application people that take care of the application. Maintenance requires around three to five people. 

Amazon EC2's initial setup was complex. However, if we compare it to other virtual machines, Amazon EC2's setup is simple.

It's very easy to set up, and you can easily set up your sizing. 

The initial setup is very straightforward. It took five minutes for me to set it up. 

Installing EC2 is straightforward. You set your user access and build it. It only takes about 10 to 20 minutes next. A single person can deploy it.

The initial setup is straightforward. We need to select a machine size suitable for the AMI we want to use, as well as the desired storage capacity. Then, we can create an image and the solution will be ready for use in just five minutes.

The initial setup is not difficult at all. It is not overly complex. I'd rate the ease of setup eight out of ten.

The solution's initial setup is comparatively difficult. You need an admin or someone with experience with Amazon EC2 to operate it.

The initial setup is a little complex.

It's not easy to set up, but I'm making it easier. I maintain the solution myself. 

The initial setup is both straightforward and complex. The tool’s Microsoft base and microservices parts are complex while the other monolithic base is really good. The solution’s monolithic base architecture is simple and straightforward.

We use cloud permission for SaaS code and services for which there are templates. My team needs an hour to deploy the entire architecture for any new project. We are able to create insights for new projects.

We have templates on the cloud solution where my team checks the requirements. After pushing the parameters, we can create a new structure for the project in an hour or so. There is no need to manually create or increase anything.

The initial setup is more or less straightforward for a developer. For somebody who is not from a pure development background it obviously requires you to understand what a public IP address is. You need to understand what storage is and then how to use it. It's mostly for developers and administrators, not for a non-technical audience; for people who can configure a server and have technical background. 

The initial setup is actually very straightforward because if you follow the guidance given on AWS you can get everything done pretty quickly without any problems. The only way it gets difficult is when you try to configure things your own way. Of course, sometimes you need to do things your own way because you have certain requirements for that particular server. Then it could get complex.

It depends, again, on the server. If it's a Windows server it is very easy, like on the fly. If it is Linux, you might find it difficult to install some AM-AWS services. So that configuration may be tough. But if you're using the basic, it's pretty easy. 

But then you need to know what each of the instances are. You need to know what you're using it for and how these instance sites apply to your organization. You need an understanding of the basic information about AWS before you can just configure it. It's not like every person can just come in and configure it. It's easy to configure, but then it may not be what you need it for.

It is project dependent. Sometimes we follow the basic strategies. Sometimes we have to consider it based on the particular project which we're working on at the time.

The solution is straightforward to set up. It's not overly complex. We can deploy the solution in just ten to 15 minutes. It's very fast.

The maintenance is very easy. If we need help, we can always contact support for guidance. 

The initial setup of Amazon EC2 is easy.

The initial setup of Amazon EC2 is not difficult. We find out the requirements that are needed to then implement the solution to meet those needs.

It is straightforward. When I first brought up the EC2 instance, I was still learning, and it hardly took 5 to 10 minutes.

Gradually, it has improved. Initially, it was complex but it's pretty standard now. It will depend upon who is installing it, their experience, and their familiarity with that cloud provider. Given that we have two rounds of experience, we found it to be pretty straightforward. If someone is new to AWS, it will probably take more time.

The initial setup is straightforward. It is not overly complex. 

The setup was straightforward and easy. While the initial setup was simple, we had some problems with Glue scripts. We ran into some problems, but we found a way around them. 

It took around 20% of our staff to do this deployment and maintenance.

The setup is straightforward and it takes around an hour. 

The initial setup is very easy and takes about half a day. We're also able to configure some scripts for auto setup. We used one DevOps person from our team to implement the solution. We have automated most things so there's no requirement for maintenance. The solution doesn't require constant monitoring. 

The initial setup is very straightforward. 

The setup is very easy. It's not overly difficult. 

I'm part of the setup and support team. 

The initial setup is definitely complex. 

The initial setup of Amazon EC2  it's not straightforward. You need an Amazon AWS engineer to use it because there is a steep learning curve. It's not very difficult to find someone with AWS skillsets. 

After four years of use if we want to log and create an EC2 instance it is very easy. Once you have a solution architect or you have an Amzon AWS engineer on your team, it's easier to do.

The initial setup is straightforward.

It works immediately. It's fast.

The initial setup wa straightforward and took around two weeks before configuration.

The initial setup is simple with a few moderate complexities, but it's ok.

The initial setup of Amazon EC2 is straightforward. It only took us a few minutes to complete.

The initial setup of Amazon EC2 was straightforward and did not take long approximately 20 minutes. We deployed the solution manually.

The initial setup is straightforward. We follow an internal document for deployment and it takes around 15 minutes to implement.

Setting up EC2 is straightforward. It takes a few minutes, and you can do it by yourself.

The product's setup is easy. 

The initial setup is very straightforward.

The deployment typically takes about two days. It does not take long. It can be handled by one department. We run it 24/7 and have it at about five financial institutions.

The initial setup is easy. The product is cloud-based. If I am buying the solution for many CPUs, it might take two to three hours. It will take four to five hours if I'm deploying with fewer resources.

The deployment process is pretty simple. We can go to the EC2 dashboard and create an instance if we have an AWS account subscription. The product would guide us with the help of dropdowns. It will ask us how many resources we want, how much storage we want, which security group we want to integrate, and what kind of Access Control we want to integrate. There’ll be a lot of questions, and we just need to select the answers.

The amount of time it takes to install depends on how you configure and how many instances of EC2 you want.

We go right to Amazon and create a machine. It takes ten to 20 minutes, so the process is pretty fast in terms of setting up. 

The initial installation was straightforward.

I am pretty technical, so I kind of knew how to do it. I also use Hydra. When comparing both platforms, I would say that AWS is just a bit more confusing or complex. 

As long as you are prepared with the groundwork, the implementation is okay. You need to have the specifications ready in terms of what kind of environment you want to create. 

Once you know what kind of environment you want to create it takes about five to ten minutes. That's all.

We only have one person that handled the deployment and maintenance. It was a pretty easy build, so it doesn't even really take up a person's full time.

We don't even really have any maintenance overhead. For us to actually deploy one particular individual or a resource for a full FTE isn't necessary. This is due to the fact that the infrastructure, the framework commission, has a lot of things that are already taken care of from a maintenance perspective and from a monitoring perspective. It's an easy job that isn't time-consuming.

We'll continue to use the solution in the future. We may expand its usage.

Starting up an EC2 instance is easy, starting an API gateway is also easy, so is setting up a lambda function and a dynamo store. The problem is, what you have just done, from looking at AWS presentations and tutorials, is a bad way of doing things in AWS. You pick up quickly that ideally everything should be scripted using cloud formations, or beanstalk, or serverless, or swagger, etc., and here is where the complexity lies. To do anything properly for an enterprise company, currently its very difficult. What tools do you use? Will they still be around in six months?

The tool's setup is a bit complicated. You need to have some amount of technical knowledge to install it. The deployment gets completed within three months. We need to first connect to the instance and generate a token. Post that we need to connect to the additional server and then to the cloud. 

The first deployment was very complicated, but over time it became easier. 
You have to understand the logic. The initial deployment took around two hours but after that we were able to deploy more quickly. It's preferable to use an integrator if you're in a production environment with many customers. 

I like the setup with Azure more than Amazon EC2 because I am more comfortable there.

Initial setup is always a little bit complex, because we use many services, such as database instances, DNS zones, load balancing setup between multi-zones and so on.

The initial setup was simple. Deployment was fast. We could do it in about 75 minutes. It might even take as little as five to ten.

We have about five people handling deployment and maintenance. Mostly, they're architects.

Setup was fairly straightforward. Using the console provides an easy to understand graphical user interface. The command-line and API options tend to be slightly more difficult to use due to the learning curve.