Managedblockchain Diagnostics

Amazon Managed Blockchain Diagnostics

When to use

Any Amazon Managed Blockchain investigation — network creation, member/node management, Hyperledger Fabric, Ethereum, chaincode, or peer connectivity troubleshooting.

Investigation workflow

Step 1 — Collect and triage

aws managedblockchain list-networks
aws managedblockchain get-network --network-id <id>
aws managedblockchain list-members --network-id <id>
aws managedblockchain get-member --network-id <id> --member-id <member-id>

Step 2 — Domain deep dive

aws managedblockchain list-nodes --network-id <id> --member-id <member-id>
aws managedblockchain get-node --network-id <id> --member-id <member-id> --node-id <node-id>
aws managedblockchain list-proposals --network-id <id>
aws managedblockchain get-proposal --network-id <id> --proposal-id <proposal-id>

Step 3 — Detailed investigation

aws cloudwatch get-metric-statistics --namespace AWS/ManagedBlockchain --metric-name PeerNodeStatus --dimensions Name=NetworkId,Value=<id> Name=MemberId,Value=<member-id> Name=NodeId,Value=<node-id> --start-time <start> --end-time <end> --period 300 --statistics Average
aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventSource,AttributeValue=managedblockchain.amazonaws.com --max-results 20

Read references/guardrails.md before concluding on any Managed Blockchain issue.

Anti-hallucination rules

1. Always cite specific network IDs, member IDs, or API responses as evidence.
2. Hyperledger Fabric and Ethereum are fundamentally different. Never mix concepts.
3. Network governance uses proposals and votes. Never assume unilateral changes.
4. Chaincode must be installed on peers AND instantiated on channels.
5. VPC endpoint is required for node access. Never assume public access.
6. Spend no more than 2 minutes on any single hypothesis. Pivot if inconclusive.

14 runbooks