Services · AWS Consulting
AWS consulting for organizations that are done with shared hosting.
LA nonprofits and mid-size companies are disproportionately behind on cloud infrastructure — still running on shared hosting plans, legacy on-premise servers, or whoever set up the VPS in 2015 and has since left the organization. When that infrastructure breaks, nobody knows how to fix it and the vendor is unreachable. ShipyardLA provides AWS consulting for organizations migrating off legacy infrastructure: cloud architecture design, migration execution, and infrastructure-as-code documentation that your team can actually use.
Modern infrastructure. Documented so someone else can maintain it.
Who this is for
Organizations whose infrastructure is a liability, not an asset.
- LA nonprofits running critical software on shared hosting that goes down during grant deadlines
- Organizations whose server was set up by a contractor who's no longer reachable and left no documentation
- Companies migrating a Rails or Elixir application from Heroku, shared hosting, or a single EC2 instance to a proper AWS deployment
- Teams that need cloud infrastructure for a new application built by ShipyardLA or another development firm
What I do
Infrastructure that runs reliably and can be maintained by someone other than the person who built it.
Cloud architecture design
AWS architecture scoped to your actual load requirements — not over-engineered for hypothetical scale you don't have. EC2, RDS, S3, CloudFront, Route 53. Designed for the team that will maintain it, not the engineer who built it.
Legacy infrastructure migration
Migration execution from shared hosting, Heroku, on-premise servers, or single-VPS deployments to AWS. Minimal-downtime migration planning — zero-downtime where the application architecture permits it. Data migration with verification — not a migration that crosses fingers on the cutover.
Infrastructure as code
Terraform or CloudFormation configurations that document your infrastructure in version-controlled code. If something breaks, you know exactly what to restore. If you need a new environment, you can spin it up in minutes.
Security and backup configuration
IAM role configuration, security group setup, automated backups, and monitoring. Built to proper security standards — not the minimum required to technically function.
How this is different
ShipyardLA treats documentation as a first-class deliverable on every infrastructure engagement. Infrastructure-as-code in version control, runbooks your team can execute, monitoring configured before handoff. You own the AWS account. You own the Terraform configurations. If something breaks at 2am, your team has what they need to respond — without calling me. Fixed-scope engagements mean no ongoing dependency unless you choose it.
How it works
Fixed scope. Fixed price. Clear ship date.
- 01
Infrastructure audit
I document what you currently run, identify the risks, and scope the migration or new deployment. Written architecture recommendation before any AWS spend changes.
- 02
Build and migrate
AWS environment built to spec. Migration executed with a verified rollback plan. Zero-downtime cutover where the application allows it.
- 03
Handoff with runbooks
Infrastructure-as-code repository, deployment runbooks, monitoring setup, and a training session for whoever maintains the environment. You own the AWS account and everything in it.
Book a 30-minute technical audit.
Walk away with a plain-language assessment of your current infrastructure risk and a realistic migration plan. No oversized AWS spend, no dependency on ongoing managed services unless you need them.