Spike: Evaluate using AWS manage solution for running an Eth node

[Jkd-eth]

User Story:

As the Passport team,
I want to have unlimited and cost-effective access to Ethereum transaction data,
So that we can efficiently run analyses and query the blockchain without incurring high third-party costs.

Acceptance Criteria

GIVEN the need for detailed blockchain data analysis,
WHEN evaluating different options for hosting an Ethereum archive node,
THEN we should decide on the most cost-effective and efficient setup for Passport.

Spike: We'll spend up to 2 days exploring and evaluating if AWS managed services is a feasible alternative

Exploration Goals

1. Evaluate Feasibility: Explore running an Ethereum a node using AWS managed solution(s)
2. Cost Analysis: Determine the monthly operating cost for both options: a) hosting our own node or b) just quering directly
3. Decision Making: Provide a go/no-go recommendation based on findings.
4. Next Steps: Outline subsequent stories and tasks if the decision is to proceed with running our own node.

Questions

• How much to host our own node?
• What is the cost to query?
• Can this easily replace the data we're getting from Alchemy?
• Does this scale to multiple chains (ARB, OP, Polygon, etc)

Product & Design Links:

Tech Details:

https://aws.amazon.com/managed-blockchain/
https://aws.amazon.com/managed-blockchain/pricing/?nc=sn&loc=3

Notes/Assumptions: