Amazon Elastic Compute Cloud (EC2)

My company is using EC2 for running their website, which includes java web service & angularjs client, which I'm building. I'm a developer, so, I don't have a lot of experience configuring the network. Fortunately, there are people with whom I'm doing it. I just need to define the security group to limit who can access our system. It is easy to setup load balancing & autoscaling.

EC2 is being used to host both development/testing and production instances of small-scale web applications (<3000 users). These applications vary in engine (Node, PHP, Python, etc.) and EC2 gives us a flexible, project-agnostic platform to deploy and test upon.

We use EC2 to pull down current master copies of our code for QA as well as reference tagged versions for our production clusters.

We have been hosting our SAAS Ecommerce platform since 2008 on Amazon EC2, back when there were only a handful of core services, EC2 , S3 and EBS. We have grown from hosting 300 Ecommerce websites to 1500+ in multiple regions, running 300 to 500 EC2 instances during peak periods.

Amazon EC2 has enabled us to expand into different countries with zero upfront cost, saved us from having to complete at least 2 full hardware refreshes and reduces our costs by allowing us to scale down infrastructure during non peak periods. As of Oct 2nd 2017 EC2 is per second billing, which will save us even more.

Amazon AWS is a trusted brand and has a proven track record providing infrastructure as service with the stability and performance needed to run any workload.

It's a really good product, that helps our organisation a lot to get great insight from all the data processes we are handling. It’s easy to get a good grasp of it and really fast forward to use. I can recommend it more for companies like ours that need to get more for their money [out of] their data

We use several dozen EC2 instances for immutable/disposable infrastructure that Docker containers can run on top of. We currently use it in several departments in addition to a private data center, but greatly favor EC2 and are in the process of moving data center servers over to EC2.The price we pay for EC2 is made up because we need less staff managing the infrastructure that we run.

We use EC2 and a host of related products to serve up 2 of our 3 SAAS products. EC2 gives us the ability to spin up servers around the world and tightly integrate with other AWS services like RDS and S3. Perhaps the most useful feature of EC2 is the ability to relatively easily create autoscaling clusters of servers to serve your products.

We are using Amazon Elastic Cloud (EC2) for our web applications and analytics work. Right now we have implemented it in few departments only but we are planning to implement it across the organization. EC2 is very helpful in providing infrastructure support for a growing business. Earlier we were relying on our in-house infrastructure team, but it's tough to grow infrastructure with your business growth. For a scalable infrastructure we decided to move to the cloud, and after considering many factors we find that AWS EC2 is best for our requirements.

We use EC2 for both our own virtual infrastructure as well as clients. We build, manage and maintain EC2 instances and VPCs. It is being used to solve the problem of hardware depreciation and upkeep. It also helps with uptime and availability and can offer higher promises than if we ran it in-house.

Used it extensively during our projects. Hosted our Webapps on Amazon Elastic Compute Cloud and also installed MongoDB on it. Used Ubuntu image.

We started off using it for just our web applications. We are currently in the process of moving it to across the entire org (IT to start using it). It addresses all typical problems. Makes everything easy and performant.

I've used EC2 for numerous use cases:
* Hosting Node.js applications of varying complexity, from borderline static sites (http://plugins.mongoosejs.io/) to more sophisticated apps (http://sixplus.com/)
* Hosting a Go-based CI tool that used the EC2 API to spawn build workers
* Hosting MongoDB instances
EC2 is my go-to tool for any sort of production server application. It's much more cost effective than in-house hardware at the scale I've been working at, primarily because EC2 instances have solid internet connections and don't change the IP of instances while they're running. However, I've started using Azure more as cloud computing is becoming a commodity and Azure gave us a better deal.

I've used EC2 for both personal projects, as well as evaluation for moving my company's infrastructure to EC2. I used EC2 for hosting a pretty standard Node/Mongo/Angular/Nginx application. In EC2 we put up a few servers - the API was on one, along with Angular, mongo was a second server and the nginx server served as a proxy. We chose EC2 because it was simple to get up and running and we already have experience w/ it.

This is our primary data store. We use it for both versioning our deployment builds as well as for storing static assets. This addresses the business problem of having a server to store assets as well as giving us the ability to store multiple versions of files that we deploy to production. Its bundling and easy interface make it an obvious choice.

The organization uses EC2 for any cloud computing we don't want to do locally. Specifically, my team uses EC2 to do large data processing jobs. We have Docker images of environments that have exactly the installations of languages and dependencies that we need for a specific task or set of tasks--from there, EC2 reads in data from the data source and writes data to some database or S3.

I utilize Amazon EC2 as a tool to rapidly and cost effectively deploy and upgrade network infrastructure for a wide range of businesses, and it has become not only an essential tool, but an entire business model within itself. In a nutshell, EC2 is a virtual server system, not unlike VMWare, that runs on hardware and bandwidth operated by Amazon Web Services, which allows me to configure and deploy a wide range of servers with a few clicks of a mouse for pennies of what it would cost to run a server in house. I am utilizing it for corporate infrastructure (Intranet), development environments, and full production environments, deploying everything from Active Directory, to Outlook Server, to full LAMP (Linux, Apache, MySql, PHP) and Windows IIS Web Servers for running internal Intranet services such as CRM, ERP, and Sales software suites to full external access web servers powering web sites, E-Commerce Platforms, and App servers. EC2 allows me to do anything I could do with a conventional hardware cost, at a fraction of the hardware, infrastructure, or IT management cost of a physical server.