contractor

Ranter

BM32

2454

Comments

3

SortOfTested

20896

4y

Low end is someone who doesnt value their skills and you shouldn't either.

Upper end seems the high end of correct. They seem to have the timeline right and estimated 2 months at $200/hr.

I would scope a contract with deliverables and a time frame. I would say all of that should take less than 2 months if it's just what you describe.

Cost, 100 to 200 freedom bucks an hour sounds about right for a short gig and a top level resource. Low end is going direct, high end is through a firm assigning a resource.

Generally the longer the engagement the better the rate. Shorter engagements end up paying a fee assuming a dry spell at the end of it.
1

sariel

8531

4y

Terraform will be your friend
2

zymk

1150

4y

I hope this info might help,

I'm an AWS Certified Solutions Architect (Associate) and I personally charge about 80-125 an hour depending on how big the project is. If there's less than 160 hours of billable time on a project I would try to aim for 100-125, and if it's over 160 billable hours then I drop the price down to 80.

I work in AWS everyday and depending on how production ready your code is will determine how quickly you can setup infrastructure in AWS to serve it. Without knowing the finer details of your application code, or database requirements, or networking; it's a little difficult to say exactly how long it would take. Scripts shouldn't be too bad either. About 3-4 weeks would be a fair estimate. Make sure they understand AWS costing.

I'm working on a large project now to reduce my company's AWS bill. I've managed to save a little over 9k a month. You will want an engineer that can make sure your monthly bill is as low as possible. AWS gets really expensive, fast!
1

chowdercake

1555

4y

I have some knowledege with aws and most of you the things you mentioned may not even be required.

Like, you don't need zerossl nowadays cause let's encrypt provides it's own certbot for linux machines.

If you're going for auto scaling I'd recommend using spot instances (a lot cheaper 70% of on demand).

Cloudflare(free version) never gave me a problem with cdn, but if you're using s3 buckets then to host images then you can't use cloudfalre with it.
Your option will be using cloudfront(aws' CDN).

And yes, in my experience the prices are resonable
0

chowdercake

1555

4y

Exactly!
I learnt it hard way when I found out digital ocean takes 5$ while aws gives same instance for 10$~ (after free tier)

There're new options like t3.nano (2 cores and 0.5 gb ram) but haven't tried it on on-demand yet

And yea, data transfer rates are bitch.
Your cost 5 spot instances will be less than the monthly data transfer rates if you're servers hit traffic
1

SortOfTested

20896

4y

@molaram
In my experience it comes down to the storage strategy and data retention more than anything else. If they don't have true data lake, snapshot+aggregate and a pervasive archival strategy to allow for removal of old data to slower static storage, and have monster clusters where every record since the beginning of time is active indexed state data in second form normalization, AWS will eat their lunch.

Those same companies tend to do things like run reports from application databases and not segregate read stores from query stores, and think Kafka refers to existentialist literature.

Related Rants

Add Comment

question

aws