AWS Deployment & Testing Setup

My web application is still in active development and I need it deployed on AWS with a reliable testing environment created alongside it. The codebase is ready to push; what I’m missing is the infrastructure and a workflow that lets my team ship features, see them running, and catch issues before we move anything to production.

Here’s what I’d like done:
• Configure an AWS stack (EC2 or Elastic Beanstalk, RDS/ Aurora if needed, S3, IAM, Route 53—the exact mix is flexible) and deploy the current build so it’s publicly reachable on its own sub-domain.
• Spin up a dedicated testing space that mirrors production settings closely enough for functional and regression tests. I’m open to your recommendation on whether this should be a separate staging or QA environment, as long as the path from commit to deploy is smooth.
• Automate the pipeline: connect our GitHub repo to CI/CD using CodePipeline, CodeBuild, or another tool you trust, with unit tests executed on each push and automatic promotion to the testing environment once they pass.
• Hand over clean documentation covering every AWS service used, IAM roles and permissions, environment variables, and the commands a new developer needs to redeploy.

Acceptance criteria
– App loads successfully from the assigned AWS URL with SSL enabled.
– Any commit to the main branch triggers a build that ends in the testing environment without manual intervention.
– Rollback instructions are documented and tested.
– I can run a single command (or click a button) to promote the testing build to production when ready.

If this sounds straightforward for you and you have recent AWS deployment experience, let’s get started—my repo is ready whenever you are.