We have a couple of primary use cases. We have an internal password server that we use for one of them. The other use case is file transfer. We have set apart an in-house SFTP process and it is all there. ETL enterprise trends and the data transformation process also run on one of the servers.

We have databases that run on one of the EC2 docs. We have a direct database that runs AWS Postgres. We don't separate that, but we do have a part of the business that runs on the server as well.

My company has a couple of servers on EC2 that we manage across defined regions. We have roughly 11 servers currently in operation for live production services and around 5 staging environments.

We have Windows and Linux servers. I think there are less Linux servers than Windows at present. I would say there are two to three Linux centers and the rest are Windows. That's what we use. Of course we have detailed information of what we do but I can't go into too much information because our company is public.

I primarily use Amazon AWS and EC2 services. The primary use case is to spawn servers quickly with a particular hardware memory, CPU, and storage footprint. It gives me a hardware service quickly, I can get a virtual machine with Linux installed with a particular storage configuration. I can also configure the security and bring it up. 

Practically, it gives me a mini data center in one or two minutes. 

We need to bring a large number of servers to do our jobs. We do a lot of crawling jobs hosted in AWS. We have templates available to us to bring a pool of servers up and running, hardware as a service. 

In our use case, it's not the number of users using the solution, it's more the number of processes that respond. Based on the compressions and the jobs we do or sometimes we crawl, so the scaling is more in terms of the amount of data acquisition we do.

We've been using the solution basically for provisioning our development in a less production-heavy environment. 

I'm using this solution for my company. We use multiple versions according to our needs and different types of instances and OS, like Windows, Linux, or auto-based.

The solution is deployed on a private cloud.

We have collaborated with AWS on different new service launches and POC, but we are not partners officially. We are a third party.

We are using this solution for relational DB servers, application servers, and IaaS. We are also using it for SMTP and HTTP services, for compute services.

I build solutions in the infrastructure of my clients. I use Amazon EC2 in their AWS cloud. 

With EC2, there are many different operating systems that you can use. If we were to talk about the size, I use the T2 and T3 instances and central apps for production and for Windows.

We are using EC2 for a couple of things. We have integration with Control-M. We have on-prem integration with the on-prem Control-M systems, and we are using EC2 for that. We are also using EC2 for ECS as a worker node.

EC2 and VPC are two services that are quite interconnected. EC2 is the Amazon console that uses the host resources in the data centers to launch servers,  instances and services with VPC as the networking part. 

We are using EC2 only for our test and backup servers, not really as a proxy server. Few users are working with EC2. It's only 10 people.

We use EC2 to configure the Kubernetes environment clusters and to reconfigure Kubernetes by applications and microservices.

We are running all of our application services on Amazon EC2.

We had a client which has a legacy application that wanted to move to the cloud without a cloud-native solution. What they did was they moved to Amazon EC2 and asked for virtual machines. They had an Oracle database and licenses, they were all provided by the client, and then they all moved to the Amazon EC2 environment.

We use EC2 for test and dev environments.

Amazon EC2 is used if you are looking for a process serving cloud service.

I mainly use EC2 for hosting our application as well as some of the user data caching mechanism and mailing services.

We use EC2 for different kinds of websites that can be hosted, and for other directories.