Amazon Web Services

“I had the chance to learn IaC and generally using AWS through a project... Now that's 2 things I can claim I have worked with in production.”

“It's not particularly difficult with how many AWS services are regional or global”

“We run our own gitlab instance in a central AWS account that has some infra buckets containing modularized Terraform”

“We run our test workload ... on one AWS ARM bare-metal machine at $1.7k a month.”

“I spent about a decade doing AWS serverless and co-wrote a Manning book on it”

“But migration to AWS from private data centers, our HashiCorp bill, and the severe lack of Nomad talent, have finally pushed us to k8s (EKS).”

“managed Kubernetes when it's available (AWS, Nebius, others)”

“we just switched to short-lived real AWS environments for integration tests. More expensive, but way fewer surprises in prod.”

“We moved to a combination of AWS and on-prem, and the overhead of providing what Heroku previously provided is quite large.”

“once we migrated to self hosted on AWS from a vendor”

“I've been coding in C# for nearly 20 years and have been using AWS technologies for nearly a decade”

“AWS for deployment, Jetbrains for development, all of ours logs to Datadog, Sentry, Snowflake, and more.”

“In the company before that it was serverless on AWS!”

“I often deploy it using OpenNext and SST in AWS.”

“Originally, it was using AWS but years ago it was decided that AWS was not cost effective”

“We've moved most of our Apps off AWS to Hetzner years ago”

“when we moved to metal instances in AWS, we gained like 20-25% performance”

“Also, you couldn't get a filer in AWS, once we moved there.”

“We run on AWS as our underlying infrastructure, largely because of our team's deep experience with it”

“downgrade our production servers from 4-core-16GB vms to 2-core-8GB on AWS”

“Today, Linkeme runs entirely on AWS. We've migrated to a serverless architecture using Lambda and Step Functions”

“We had evaluated and used a number of proprietary products and services from AWS, Hashicorp, CI/CD, and RMM vendors.”

“we migrated everything to AWS in under a week.”

“as well as AWS, Hetzner etc accounts linked with that company.”

“annotations (eg for granting and AWS role to a service) etc.”

“We run on Google Cloud, AWS, and our own hardware now since middle of this year”

“I have no need to run something any more robust than ECS in AWS for my workload.”

“When AWS started charging for IPv4 addresses I started switching to IPv6... I moved to another hosting service that didn't charge.”

“Still, we run most of our infra on AWS.”

“We mostly run APIs behind AWS API Gateway.”

“we setup a separate archive account on AWS for backups and also made an extra copy on GCP as our off prem equivalent”

“Both the container build service and the Actions runners are in the same AWS VPC”

“has built complex (is there another way?) AWS infrastructures etc.”

“we migrated from azure to AWS, and running a container on Fargate is significantly more work than Azure Container Apps”

“I work for a company that is trying to bolt this functionality onto all the AWS database products.”

“we also mostly deploy to ARM Linux on AWS.”

“We use AWS via terraform at work”

“we use the aws/azure because the model is much better”

“servers to AWS, and the workflow is the same.”

“We use Alibaba Cloud, GCP, and most of all AWS.”

“I was a journeymen CRUD developer/architect when I got hired with two years of AWS experience”

“Consultants are full time employees at AWS who get paid by the customer to do hands on keyboard work.”

“At an old job we did zero trust corp on a different AWS region and account.”

“Suffice it to say, we run out of AWS now.”

“I can't say anything but "Sorry dude, I'm not a clairvoyant... give me AWS access now"”

“I had an unplanned migration to AWS.”

“We were forced to migrate, then we migrated away to pure AWS a few month later.”

“worked thru Covid with zero downtime when we switched to hosted solutions from AWS and Google cloud.”

“A big plus is that Terraform works outside of AWS land.”

“with Ubuntu and Amazon Linux VMs as we run in AWS.”

“I learned a lot about AWS, but after about half a year we switched to Datomic Pro.”

“We picked AWS because it was the only thing that fit back in ~2015.”

“so that new servers in ASGs could install packages on top of based images.”

“our open source project for analyzing security logs on AWS”

“I consider myself to be an competent 'DevOps' engineer as long as it is on AWS”

“Cloud Tech (AWS) which also includes, lambdas, Iam management, dynamoDB, cdk or serverless”

“Having a managed DB service (with backups, point-in-time recovery, etc) would have us quitting AWS in an instant.”

“For AWS managed resources definitely use Graviton. But for spot instances in EC2 we've found better pricing”

“We're just making AWS services (run by experienced operators) significantly easier to consume”

“we found that prospective customers were reacting negatively to demos that were not on the same platform they would be running in production (AWS).”

“We had historically one big AWS account, we are now splitting it into more fine-controlled accounts and migrated under a "root" account following AWS best-practices”

“We had some AWS experience from running our backing services (RDS, Elasticsearch, Memcached, Redis) on AWS”

“On AWS we prefer using things like DynamoDB and that further locks us into AWS.”

“At work we run some (non-GPU) instances in every AWS region”

“I've got an AWS application that I'd love to to build preprod environments for (not in Kubernetes)”

“We migrated to AWS within a month. Since I was more familiar with AWS, that's the part I helped on.”

“We migrated around 20 services within a couple of days, coming from a mixture of all sorts of AWS services and Hetzner infra.”

“We run ClickHouse clusters in AWS / GCS using block storage in our cloud platform.”

“Used them a few years back, but I'm afraid we moved to AWS after a few too many reliability issues.”

“it was significantly cheaper to lease back those IPs from AWS, do absolutely nothing with them (in AWS), and advertise routes internally”

“running (along with PgSQL) on a shared AWS t2.medium instance, we migrated these to a GKE cluster”

“We even replaced all but one core AWS service in our application and moved everything else to Linode.”

“today we also offer the option to run on AWS.”

“we switched multiple times, from Azure to Google Cloud to AWS, chasing those startup credits.”

“mostly for cost efficiency (and adoption of k8s for even better cost)”

“running a dockerized Jenkins instance (and agents) in AWS”

“We've moved to AWS since, but we started our early cloud infra on Linode”

“For acquisitions where we can't retain IAM between AWS accounts, order a snowball or snowmobile between them”

“we migrated for our k8s stuff from AWS to self-manged Hetzner Cloud and save roughly 66%”

“We realized how great Dynamo was only after we migrated off AWS.”

“We moved to AWS.”

“We run entirely on the Cloud (no physical offices or data centers) and honestly, some minimal GCP/AWS best practices”

“We run on AWS east but you can spin most of the stack up locally with docker-compose.”

“Turns our AWS West 2 was down.”

“We're looking at nearly a 50% cost reduction versus the current m5 RDS and other EC2 instances.”

“Our customers know we use AWS and they go and check the AWS status dashboards and tell us there's nothing wrong”

“once you have infrastructure copies in four or five different environments and five or six AWS regions”

“I know that we run some services on us-east-1 and they never completely stopped working during the downtime”

“There are at least 6 cloud providers I can name that I've used which run their own data centers”

“We had hundreds of thousands of websocket connections to us-east-1 drop at 15:40... Luckily... we run in 6 other regions”

“At my $WORK we run all of our backend on AWS but anything I've touched has to also run locally.”

“based on my own benchmarking ... In AWS on x86, 1 vCPU is 1 hyperthread, so it's kind of half a core.”

“we moved to AWS.”

“we run some things in aws.”

“We were heavy EC2/RDS users, now we run their NX whitebox nodes with their KVM based hypervisor”

“I got to build everything from scratch, and I was 100% focused on infrastructure.”

“it let us take advantage of new AWS features on average much faster than CloudFormation.”

“we run in AWS and AWS can kill nodes a lot faster than we can haha”

“I was learning how to use AWS...which in a way was a lot simpler back then”

“my limited experience (in prod, with only like 50K a month bills) AWS and Azure are functionally identical.”

“how easily we could get runners autoscaling in our own AWS environment. We'd run tiny instances as the actual runner”

“All the infrastructure is defined in code, can be released onto a blank AWS account (or k3s instance) in minutes”

“Here is an AWS account and five developers, so make it happen.”

“we completely disable destructive operations from our AWS/Azure Terraform user”

“starting from colocated servers finally to docker and aws hosting with testing automation.”

“we launched WL3 with something like 1K rails boxes on AWS, running a few services”

“we migrated away from our $3k/mo AWS bill back in the day to save $2k/mo with DO.”

“we run Azure and AWS as well as bare metal”

“We migrated from aws to google cloud.”

“for the topics where we can predict the computing power for the next months, we migrated everything to baremetal.”

“I use the cheapest VM on AWS (I work on Azure now, but vendor lock in is real)”

“at work we use AWS machines with their own Docker environments for that.”

“I'm generally doing everything "server-y" or "Linux-y" on AWS these days anyhow”

“We use spot instances EXTENSIVELY.”

“When I left HERE it was also heavily using AWS, so it's a two-way relationship.”

“On our hosting platform we use AWS linux, which is based of Centos.”

“my subjective sense is that it isn't, but I regularly visit just a couple of specific sections in the AWS console”

“I trust Microsoft to safeguard our business data more than I trust our 7 person team w/ a $2000/m AWS budget.”

“We use AWS for some services as well so it is a specific part of the workload we run (not just WP)”

“I just glanced at our own airflow instance in AWS (not on this service).”

“This service handles about 2.5 billion requests per month from one AWS region.”

“We run several applications on Kubernetes using AWS (combined >2k req/s at peak time)”

“We still use AWS, but our usage has gone down dramatically.”

“My company migrated our ~2TB postgres db from heroku to AWS”

“you have your VPCs and your ELBs and compute and subnets and IGW and tidy little boxes containing them all to indicate this is everything in prod AWS account”

“we deploy them all in Docker containers on AWS basically.”

“We run docker on top of aws. So a vm-ish thing on top of a vm.”

“I have a websocket-scraper on an aws free tier that's dropping data into a sqlite file”

“Pay for a managed NAT gateway? No thanks I can do the NAT myself with iptables on a cheaper EC2 instance.”

“CF workers possibly wouldn't work cuz we run on AWS and would have to pay for bandwidth to and from CF”

“rolling your own using AWS SDK + spot instances + slack chatbot (our solution)”

“We would be more than happy to chat about how we migrated to AWS, the differences, benefits, down-sides, surprises.”

“Recently we migrated from github + Jenkins to gitlab + our own gitlab-runners in AWS.”

“you could deploy it to AWS... the service was only running in one platform in prod.”

“One of the reasons we moved to GCP from AWS”

“We moved to GCP from AWS because we thought it'd be cheaper.”

“ferrying images in and out of AWS adds up”

“How have I not been using them for multiple AWS accounts for like ever!”

“I've used Ansible on AWS for 2 years to build out over 50,000 servers, to set up the vpc architecture, control IAM roles”

“I've also used buildroot in both AWS and GCP to run workloads from read-only system images.”

“Been using AWS for 8+ years since their first inception of S3, then 6 years of GCP.”

“At my company, we use all major 3 clouds.”

“we're hosted somewhere in aws (not my expertise there - I get lost in the acronyms)”

“for everything that we run on my current job + for the things that I set up when freelancing... Including AWS only stuff like VPCs”

“we replaced the service with an AWS offering for $1000/mo.”

“We run on AWS. We log lots of stuff to CloudWatch.”

“We run them on stock Linux images deployed to AWS.”

“Going into AWS will nearly double our infrastructure costs, but our business is willing to pay for it”

“we run hundreds of PostgreSQL database clusters on Kubernetes (on AWS)”

“On AWS instances with EBS disks (most instances), disk is basically network.”

“I've seen AWS from inside and I helped build a small part of it.”

“After we migrated to AWS we made it easy for devs to launch a new isolated copy of the whole environment in EC2.”

“We now have somewhere in the neighborhood of 100kLOC running in AWS”

“we run our k8s stack on AWS”

“I'm making sure all of my resources are spent on AWS and Microsoft services.”

“we have a different AWS account for each environment (production, staging, etc.)”

“we are an AWS shop and I'm the most experienced (and certified) AWS person”

“We use AWS, I'm not saying it's the "best" it's just what I'm familiar with.”

“I learned and brought in production the followings: AWS Cloudflare and Lambda (with Go)”

“I have been using AWS and GCP for a while now and was thinking about getting the certifications”

“We run a lot on aws. Services, databases, ...”

“Another internal use is an AWS infrastructure management tool that we built.”

“We use serverless-framework to interface with aws.”

“with AWS IAM auth, AWS is a trusted third party”

“We use a ton of AWS's services because AWS is already on-boarded for our enterprise.”

“We run three nodes right now on m5.xlarge instances.”

“The same codebase is used for hosted services that we run ourselves on Kubernetes running on AWS.”

“a recent Docker/AWS/ECR/ECS system I worked on, much of which seemed like a whole lot of useless work”

“For workers we run only Java and run everything on AWS.”

“Basically they just set up some VMs, security groups, a VPC etc and they treated AWS like an overpriced colo.”

“When we moved to AWS, there were plenty of folks who were let go because their expertise was in physical infrastructure”

“We transitioned out of AWS where we had relatively well managed instances of our stack managed with chef and terraform”

“we moved to Google Cloud (GCP) after exhausting AWS credits to utilise GCP credits.”

“we're conscious of having to pay all the AWS bandwidth costs considering the dataset is in the petabytes”

“Company moved to AWS within a quarter.”

“We ended up staying on the deprecated model until we moved to AWS (for unrelated reasons).”

“The only time I use Windows is on our AWS instance. On there, we run WSUS”

“we switched from AWS to GCP for cost reasons, and I implemented an abstraction (similar to go-cloud's) between S3 and GCS”

“We were running on AWS for 3 years before moving to GCP and have the same experience.”

“we just need AWS, payment processing (stripe) and a bank account.”

“Error message wasn't being passed from AWS to the user so infra would fail to build”

“but not really because it is hidden cost of our AWS pricing.”

“We still used autoscaling, but it was for responding to spikes and troughs in our own load, not failure scenarios.”

“We did 10 runs of each on a large AWS instance and averaged the results.”

“my last shop was heavily AWS based and relied on IAM”

“it was a few hundred dollars more per month in AWS fees”

“when we moved to AWS, our software was exquisitely resilient, with multiple levels of degraded functionality everywhere.”

“We run most of our stuff on AWS, but we use BigQuery for the data warehouse.”

“We're on AWS, so this is tangentially related.”

“The complexities arise when you then need to have Git exposed to the internet to allow AWS pipelining to operate.”

“we saw multiplicative increases... I only have numbers for once it was moved into AWS and onto different machines”

“We run our most critical services in at least 3 availability zones and we are moving the rest of our services soon as well.”

“You know what we run? Linux. On AWS. Using chef”

“It was necessary to integrate with AWS, test everything in prod and let people play with the product.”

“We run Kafka (and I believe Cassandra) on top of Centos/ZFS in AWS”

“Workload is mostly writing incoming metrics from many dynamic instances (AWS).”

“I've been using AWS for years and this is the first I've ever heard of this.”

“We run in AWS on our own brain dead "orchestration" system but we are looking to use something purpose built soon.”

“I made one of these 6 years ago for one of my clients using aws, on my todd and it's really not that complicated.”

“I have some previous experience managing deployment on AWS via AWS CLI and dashboard”

“we run all our sites on an all-AWS stack”

“We run it for our customers on their AWS clouds and even on enterprise infrastructure.”

“Our main stack is on Amazon AWS (West Coast)”

“We deployed K8S on AWS (I'm a dev at Appuri). Like Bilal mentioned we run pretty much everything on AWS”

“We had this happen with rackspace - hence we moved to Amazon”

“I come from a major background in AWS, ChaosMonkey in prod”

“We run a very large AWS infrastructure as a engineering team (no dedicated ops).”

“We run full AWS.”

“I have a number of services that can tolerate a small amount of downtime if they fail, during which I would spin up a replacement AWS server.”

“it's still not as fast as when we run memcached on AWS.”

“kube-up does a lot of tedious AWS configuration that I/we haven't documented.”

“which is 100% run on AWS.”

“and deploy to AWS (regular AMIs rather than any of that fancy docker stuff)”

“a dozen teams use it for many many production projects internally and in AWS”

“we have been using Dagobah for a simple cron on top of AWS.”

“We moved to AWS a while back but when we were a growing team on DO”

“we run on the cloud in AWS and SoftLayer”

“we deploy on AWS in prod, and spin up Heroku apps for sharing prototypes”

“We run on AWS with our own system that orchestrates Go binaries”

“We run 5 machines in aws.”

“We have mentioned that we run tens of thousands of instances across three AWS regions.”

“so we moved off of them to a pure AWS implementation.”

“we previously used Coherence to hold that data and we keep it in RAM within 32 instances of m3.large (on AWS)”

“All I had setup was a micro S3 instance I'd been using for some toy craigslist scraping”

“My colleagues deploy exactly the same release into AWS with thousands of machines.”

“We use this even in AWS for a site and it works really reliably”

“For that level of cost efficiency, you really need to use spot instances. A cluster of 100 m1.xlarge machines”

“I can't give a very complete answer as I've been using AWS to work on a side project for about a whole week.”

“to EJB 3.x and goes to the cloud we go (AWS).”

“We use multiple cloud providers (Digital Ocean and AWS being our primary), Play Framework, AKKA , Ansible for deployment, Shippable for our CI”

“the ecosystem has supported all of our needs: Postgresql, redis, rest, soap, 0mq, AWS”

“Yep, we run everything on AWS as of a few months ago.”

“I tried to switch again when we moved to Amazon, but sadly it wasn't an option so I went to Ubuntu instead.”

“it's still more economical for us to host our own servers”

“I've used AWS, DO, and most recently Rackspace Cloud for a big client.”

“We run our hypervisor on top of Amazon (first level guest)”

“I've supported clustered Oracle on AWS handing massive numbers of micropayment transactions”

“We use https to upload stuff to our amazon servers, and crunch the data, and bring it back to us using https.”

“I'm working on a large project running on AWS. We're building an n-tier architecture with many roles in auto-scaling groups.”

“We've been running on AWS for 2 years. We use a handful of their services including EC2.”

“I'm using the AWS stack for http://www.soundslice.com/”

“We run a large Kafka cluster on AWS, and it is one of our highest-maintenance services.”

“We currently run aerofs which is mostly really good - but sometimes we get into a situation (of our own making, we run it on an aws spot instance that can vanish)”

“Same goes for AWS. Besides snapshots we run old-school backups to ensure we can recover on old-fashioned bare-metal if necessary.”

“Right now we run everything in the US-East region, and we have all our services balanced across 4 availability zones.”

“We use Heroku and AWS to drive 100% of our platform, but we're also not mobile (yet).”

“At the startup where I work, we use Amazon. Start with a small or micro instance and put Cloudfront in front of it.”

“our disaster recovery worst-case scenario means recreating our services from scratch in any Amazon AWS datacenter on Earth”

“a tiny 3 machine "cluster" we run on AWS”

“In my organization's case, we run all of our infrastructure "in the cloud" - mostly AWS.”

“We run our servers on Amazon Web Services and use their elastic load balancer (which is were we terminate SSL).”

“Coming next week: How we moved off Heroku onto AWS after the Heroku outage.”

“As a large scale AWS user, I'm not sure I can agree with any of these recommendations.”

“feeding the news into the python back-end running on AWS”

“* Servers: AWS”

“File Hosting: AWS”

“We have assets on Amazon, Slicehost, and Linode.”

“Currently, we run the majority of our computing at AWS.”

“For big, burly projects, we use Amazon.”

“We run our service off Amazon's cloud system, which gives us a lot of flexibility.”