phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

Fix Critical AWS Website Bugs

  • Posted:
  • Proposals: 66
  • Remote
  • #4514855
  • OPPORTUNITY
  • Awarded
CYTNHIA W.Taha M.Bright A.Óscar P.Hamza M. + 61 others have already sent a proposal.
  • 3

Description

Experience Level: Expert
My site is already hosted on AWS, feature-complete on paper, yet five key components refuse to work and our go-live is now less than two weeks away. Every failure is consistent and repeatable, so I’m looking for someone who can dive straight into production-level debugging and close these gaps fast.

The components that must be repaired:
• Email verification (custom-built)
• Dialer system (Twilio)
• Booking system (custom-built)
• Payment system (Stripe)
• Live functionality / real-time chat

All code will stay where it is—nothing leaves AWS—so you’ll need solid AWS console familiarity alongside everyday full-stack skills. I can provide repository access, architecture notes, and direct contact with the previous developer if needed.

Acceptance is simple: each item above must perform reliably under normal user load, pass my own end-to-end test scripts, and remain stable for 48 hours in staging before we flip the live switch. If any hotfixes are required after launch, I expect a prompt turnaround.

Please outline your approach, relevant AWS + Twilio + Stripe experience, and confirm you can commit to the 14-day window.

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • Sudhanshu K.

    Could you please confirm the current AWS architecture and tech stack (frontend, backend, database, and real-time service) and whether you can provide repository, AWS, Twilio, and staging access at the start of the engagement?

  • Eight Veer Ltd

    Hi Ashley, do the five failures share a common AWS execution path - for example the same backend/API, authentication/session layer, webhook handler, queue or WebSocket service or are they running as separate components?

    To start immediately, we need:

    - Repository + staging access
    - Relevant AWS/log access
    - Architecture notes
    - E2E test scripts
    - Error/reproduction details for each issue
    - Twilio/Stripe test access where required

    Once received, we can begin immediately.

  • Sahil D.

    Hi Ashley, quick question regarding the 48-hour staging validation: Are you using CloudWatch or an APM tool (like Datadog/Sentry) for log tracking, or should I set up custom error logging for the email, Twilio, Stripe, and live chat services to monitor staging stability?