lyft / lyft/awspricing

Move to boto3 pricing API?

Open
#21 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
214
Forks
52
PR merge metrics
No merged PRs in 30d

Description

Hi,

I was looking for a wrapper for the boto3 pricing stuff and came across this, which pretty much does what i need but maybe with some caching mods for redis :)

Was wondering why this doesn't use the boto3 'pricing' api to get the data, and if it would offer a speedup and similar functionality if it did as it could do the queries directly rather than working on the downloaded data?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named; start by reviewing the existing downloaded-data implementation and boto3's pricing API capabilities. Done should be an evidence-backed comparison of speed, functionality, and caching implications, with a concrete migration scope if appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.