- Newest
- Most votes
- Most comments
Hi,
Please refer to the document Using token based access to make JSON-RPC API calls to an Ethereum node which has examples that demonstrate ways to make Ethereum JSON-RPC API calls to an Ethereum node on Amazon Managed Blockchain using token based access.
I see that you are getting '403 error' to find the root cause and to answer your question, we require details that are non-public information. Please open a support case with AWS using the following link https://support.console.aws.amazon.com/support/home#/case/create
Hello!
I am not sure if you have resolved this error, but if you are using "token based access", these endpoints conform to the following patterns:
HTTP endpoint
https://your-node-id-lowercase
.t.ethereum.managedblockchain.us-east-1
.amazonaws.com?billingtoken=your-billing-token
For example, https://nd-6eaj5va43jggnpxouzp7y47e4y.t.ethereum.managedblockchain.us-east-1.amazonaws.com?billingtoken=n-MWY63ZJZU5HGNCMBQER7IN6OIU
WebSocket endpoint
wss://your-node-id-lowercase
.wss.t.ethereum.managedblockchain.us-east-1
.amazonaws.com?billingtoken=your-billing-token
For example, wss://nd-6eaj5va43jggnpxouzp7y47e4y.wss.t.ethereum.managedblockchain.us-east-1.amazonaws.com?billingtoken=n-MWY63ZJZU5HGNCMBQER7IN6OIU
Note that the node ID is case sensitive and must be lowercase where indicated, or a signature mismatch error occurs.
Also ensure that you are using the "Token" parameter for "your-billing-token", rather than the "Accessor ID". I have attached a screenshot for reference.
I hope this helps -- please let me know if you have any more questions. Have a great rest of your day!
Relevant content
- asked 2 years ago
- asked a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago