Amazon EC2 Scalability POC Setup
Budget: $60 – $65 USD
I need a hands-on AWS engineer to stand up a small but realistic Proof of Concept that shows how an Amazon EC2 deployment will scale under load. The single objective is clear: validate horizontal scalability, measure the tipping points, and document the results so I can take solid data back to stakeholders.
Here is what I have in mind. You will design and spin up an EC2 architecture that can grow and shrink automatically, wire it to an Elastic Load Balancer, and light up CloudWatch (or your preferred monitoring stack) for granular metrics. The underlying operating system is still open—Linux, Windows, or Ubuntu all work for me—so feel free to choose whichever lets you demonstrate best practice more quickly.
I expect you to:
• Provision the environment (manual console work is fine for the POC, but scripts via CloudFormation or Terraform are even better).
• Generate representative load, ramp it up, and capture CPU, memory, network, and response-time data.
• Tune auto-scaling policies until we see predictable, repeatable scale-out and scale-in behavior.
• Deliver a concise report with graphs, observations, and your recommendations for production hardening and cost implications.
If you already have experience benchmarking EC2 fleets and can turn this around quickly, we should talk.
Here is what I have in mind. You will design and spin up an EC2 architecture that can grow and shrink automatically, wire it to an Elastic Load Balancer, and light up CloudWatch (or your preferred monitoring stack) for granular metrics. The underlying operating system is still open—Linux, Windows, or Ubuntu all work for me—so feel free to choose whichever lets you demonstrate best practice more quickly.
I expect you to:
• Provision the environment (manual console work is fine for the POC, but scripts via CloudFormation or Terraform are even better).
• Generate representative load, ramp it up, and capture CPU, memory, network, and response-time data.
• Tune auto-scaling policies until we see predictable, repeatable scale-out and scale-in behavior.
• Deliver a concise report with graphs, observations, and your recommendations for production hardening and cost implications.
If you already have experience benchmarking EC2 fleets and can turn this around quickly, we should talk.