Infrastructure and deploy

AWS

The cloud many clients have already standardized on.

made by
Amazon

Magic Ship is one shop in Vancouver, BC, working remotely with clients worldwide. We are not a partner, reseller, or certified vendor of Amazon - we just build with this.

What AWS is

AWS is Amazon's cloud platform. The parts that come up in our work are ECS and Lambda for compute, RDS and Aurora for Postgres, S3 for object storage, and Bedrock for hosted model access that stays inside the account and region.

How we use it

When a client is already on AWS we deploy there instead of introducing a second cloud, usually a container on ECS or Fargate talking to RDS Postgres with pgvector enabled. Infrastructure is defined in code and the same stack runs locally under Docker Compose so the feedback loop stays fast. Bedrock is how we keep model traffic inside the client's account when procurement requires it.

Where it is the wrong choice

For a small internal tool, the IAM, VPC, and networking work costs more than the tool is worth; Fly.io or Cloudflare has it running the same day. We also do not take standalone cloud platform or cost-optimization engagements - our AWS work is deploying what we build.

Building something on AWS?

Send the problem rather than a job spec. You get an answer on scope, on fit, and on whetherAWS is even the right call for it.

Start a project

AWS and Amazon are trademarks of their respective owners, used here to say what we work with.