“When were the development and QA environments moving out of AWS?”
The message says there had been several questions about the move. It asks whether a plan existed. It does not include my answer, a deadline, or proof that the migration happened.
That limited record still captures an active infrastructure decision. Development and quality-assurance environments were running in AWS. The direction under discussion was to bring them back onto company-operated infrastructure in New York.
Development and QA environments are where engineers build and test changes before production. Their capacity, network access, data, and configuration affect how quickly teams can work and how accurately they can reproduce a problem. Moving them is not only a server task. Build jobs, test data, access controls, deployment tools, and dependencies all have to continue working.
The email also raises a practical cost and ownership question. AWS made it possible to add virtual machines without waiting for physical hardware. Company-operated infrastructure could offer different economics and tighter integration with the systems already in the data center. The right answer depended on workload, team needs, and how much operational work each option created.
Shutterstock was using both kinds of infrastructure during this period. Later in 2013, a public OpenStack presentation described a provisioning system that could send virtual-machine requests to OpenStack and dedicated-hardware requests through Foreman. It also described a virtual private cloud in AWS used alongside physical data centers. The February email is an earlier record of the team working through that mixed environment.
This skeleton should not claim the move was completed or that AWS was rejected. The source supports a narrower point: people expected dev and QA to move, they were asking for a schedule, and the operations team needed to turn that expectation into a clear plan.