AWS to Shut Managed Blockchain, New Customers Cut Off Oct. 29

AWS sets two Managed Blockchain deadlines

The October cutoff concerns admission of new customers. The September 2027 date concerns service availability for existing users. Neither means that every current application must stop operating this month.

AWS has not disclosed an affected-customer count, the value of transactions supported by AMB or expected migration costs in its availability announcement. It also does not give a commercial explanation specific to the blockchain service.

That leaves an important boundary around the news. The retirement shows that this managed product is ending; it does not establish how much institutional blockchain use has grown or fallen, or whether demand caused the decision.

AMB entered production in April 2019 after a preview announced at re:Invent 2018. The original launch post described Hyperledger Fabric networks spanning multiple AWS accounts, with members running peers and sharing a transaction ledger.

AWS then launched Access and Query in July 2023. Access offered serverless Bitcoin connectivity alongside its dedicated Ethereum service; Query supplied standardized Bitcoin and Ethereum data without customers having to build the same transformations themselves.

The two launch dates help explain the range of affected workloads. A company using a private business network and a wallet service reading Bitcoin history may both rely on AMB, but their migration projects have little in common.

AWS’s replacement options still include running blockchain nodes on its cloud infrastructure. The notice therefore does not amount to a withdrawal of every AWS hosting option for crypto applications.

Bitcoin and Ethereum RPC access can move providers

An RPC endpoint is the address an application uses to ask a blockchain node for data or submit a signed transaction. AWS’s node migration guide covers Ethereum, Bitcoin and Polygon, with self-managed nodes or outside infrastructure providers as alternatives.

Because these services expose standard interfaces, many applications can retain their method calls while changing connection addresses, authentication and network controls. That makes RPC migration comparatively contained, although the replacement still needs the required historical data and connection features.

AWS says AMB Access Bitcoin does not manage customer wallet keys. Its migration does not transfer wallets or private keys. An application connectivity change and a movement of customer assets are separate events.

For self-hosting, AWS points to Blockchain Node Runners, its blueprint-based deployment project. The migration guide says customers would take responsibility for operating the nodes, including availability, security, upgrades and synchronization.

The operational trade-off is straightforward: removing a managed service can bring more control while placing more work on the application operator. Selecting another managed provider changes that balance again, rather than eliminating infrastructure dependencies.

AWS recommends comparing results at fixed blocks or confirmation depths and shifting traffic gradually. Checking only the newest block can produce misleading differences when nodes receive data at different speeds or the chain reorganizes.

The distinction between a network and its access infrastructure also appears in the site’s x402 payment coverage. An open payment protocol can still depend on hosted services, so protocol availability alone does not guarantee that a particular application remains reachable.

AMB Query and Hyperledger need deeper migrations

Indexed Query customers face a larger application change. AWS’s Query migration guide says an ordinary Bitcoin or Ethereum node does not supply every indexed history and balance capability that AMB Query provides.

The guide discusses QuickNode for synchronous application requests and Allium for flexible historical and analytical queries. It describes those options as non-exhaustive, rather than naming a compulsory successor.

Teams must adapt provider data to their application’s expected format and verify historical balances, transaction status and pagination. AWS warns that the alternatives are not one-to-one replacements for every response.

For a wallet history page, the practical test is whether the replacement returns the records the product needs, in the right order and without gaps. A responding endpoint alone would not demonstrate that the migration preserves the customer experience.

Private Hyperledger Fabric customers face another problem. AWS’s support notice describes rebuilding identities, configuration and network state, with participating organizations coordinating extraction, replay and validation.

The notice also offers a database destination for customers that only need retained records. That choice gives up blockchain-specific features such as endorsement policies and multi-organization consensus, so it changes the operating model as well as the hosting arrangement.

These differences make the earliest planning question more specific than which provider to hire: operators need to identify whether their dependency is a node connection, an indexed data service or the private network itself.

Source: Alternative.me. The Bitcoin-focused index read 72, or Greed, on October 2; it does not measure the reliability of AWS or any replacement provider.

The next fixed milestone is the October 29 cutoff for new customers. Existing users then face a September 2027 service end, with customer-specific migration schedules and costs still undisclosed. The work to watch is whether applications and private-network members validate replacements before their current access disappears.