POOLYAB MARKETSBTC Loading…ETH Loading…SOL Loading…Market data refreshes periodically
Blog

Amazon Managed Blockchain Ethereum: Features, History & 2027 Shutdown

Amazon Managed Blockchain stopped accepting new customers on October 29, 2026 and ends support on September 29, 2027. Learn what AMB Access Ethereum provided and how existing users can migrate safely.

Amazon Managed Blockchain Ethereum service announcement

Update: November 20, 2026. Amazon Managed Blockchain (AMB) is being retired. AWS stopped accepting new customers on October 29, 2026. Existing customers can continue using the service until September 29, 2027; after that date, AMB will no longer be accessible. This guide explains what AMB Access Ethereum provided, what its original Ethereum announcement meant, and how existing users can plan a safe migration.

Amazon Managed Blockchain Ethereum service announcement
Ethereum was added to Amazon Blockchain Services

What Was Amazon Managed Blockchain?

Amazon Managed Blockchain was an AWS service designed to reduce the infrastructure work involved in accessing and operating blockchain networks. Instead of asking every customer to build, synchronize, monitor, secure and maintain all node infrastructure alone, AWS provided managed blockchain resources and API access. The service supported public-network access for Ethereum, Bitcoin and Polygon, private network capabilities using Hyperledger Fabric, and a separate indexed-data product called Amazon Managed Blockchain Query.

For Ethereum developers, the relevant product was called Amazon Managed Blockchain (AMB) Access Ethereum. It provided managed Ethereum nodes that applications could use through standard Ethereum APIs. AWS documentation describes Ethereum nodes using the Geth execution client and Lighthouse consensus client, with access to both execution-layer JSON-RPC methods and consensus-layer APIs. The service was infrastructure for connecting applications to Ethereum; it was not a new blockchain, a replacement for Ether, or a private version of Ethereum.

This distinction matters. Ethereum remained a public, independently operated network. AWS supplied node infrastructure and an authenticated interface. Transactions still followed Ethereum protocol rules, and application developers remained responsible for their own smart contracts, application logic, accounts and private keys.

What Changed in the Original Ethereum Announcement?

When Ethereum support was introduced, the important development was that AWS customers could provision managed Ethereum nodes without building every part of the node environment themselves. Applications could connect to those nodes and use familiar Ethereum interfaces to read blockchain data, inspect contract state, submit signed transactions and build decentralized applications.

Older coverage of the launch mentioned the Ropsten and Rinkeby test networks. Those references are historical, not current setup instructions. AWS recorded that it stopped allowing new Ropsten nodes on February 28, 2023, and new Rinkeby nodes on August 10, 2023. AMB Access Ethereum ended Goerli support on April 1, 2024. Developers should not copy test-network names or node-creation steps from 2021 articles. Check current Ethereum and AWS documentation for the networks supported by any replacement environment.

Ethereum Mainnet also changed after the original announcement. The Merge moved Ethereum Mainnet to proof of stake in September 2022. AWS documented that its managed Ethereum nodes supported the change, but that did not make AMB a staking service: AWS documentation states that staking was not supported through AMB Access Ethereum.

How AMB Access Ethereum Worked

Managed Ethereum nodes

A node maintains and verifies blockchain data and provides an interface through which applications can query the network. With AMB Access Ethereum, customers could create dedicated Ethereum nodes in an AWS account and connect applications to them. AWS handled important infrastructure operations for the managed node service, while the customer still had to design the application, manage credentials, understand API behavior and decide how to handle transaction confirmation and failures.

Node access was useful for workloads such as decentralized application backends, smart-contract monitoring, NFT or token applications, transaction analytics and services that needed to read Ethereum state. A managed node could reduce the initial operational burden, but it did not remove the need to understand Ethereum, JSON-RPC, gas, confirmations, reorganization risk or application security.

Execution and consensus APIs

Ethereum has an execution layer, which handles transactions and smart-contract execution, and a consensus layer, which coordinates proof-of-stake consensus. AMB Access Ethereum exposed JSON-RPC APIs for execution-layer work and a Consensus API for supported Beacon Chain information. Developers needed to identify which API their application actually used. Replacing an execution JSON-RPC endpoint does not automatically replace a separate consensus-layer dependency.

HTTP, WebSocket and authentication

Applications could use HTTP connections for JSON-RPC requests and WebSocket connections for supported JSON-RPC subscriptions. AWS used Signature Version 4 (SigV4) authentication or AMB Accessor tokens, depending on the configuration. These authentication mechanisms are specific to the AWS service. A replacement node or third-party RPC provider may use a different endpoint format, API key, header or private-network access rule.

Do not put AWS credentials, Accessor tokens, private keys or provider API keys in browser code, public repositories or client-side applications. Store secrets in an appropriate secrets manager or protected server-side configuration. When migrating, remove old authentication code only after the replacement has been tested and the rollback period has ended.

What AWS did not manage for customers

AMB provided node infrastructure, not custody of an application’s Ethereum wallet. Customers remained responsible for creating and protecting Ethereum accounts, signing transactions, managing private keys, reviewing smart contracts and deciding what transactions to submit. A managed RPC endpoint should never be treated as a wallet or as a guarantee that a transaction is safe.

Why Amazon Managed Blockchain Is Being Retired

AWS announced that it is ending support for Amazon Managed Blockchain. This is a service lifecycle decision, not the end of Ethereum or a shutdown of the Ethereum blockchain. Ethereum Mainnet continues to operate independently of AMB. What is ending is the AWS-managed product and its associated access functionality.

The dates are important for planning:

  • September 29, 2026: AWS published its service availability update announcing the sunset timeline.
  • October 29, 2026: AMB stopped accepting new customers.
  • September 29, 2027: AWS plans to end support. Existing customers can use the service until this date; after it, AMB functionality will no longer be accessible.

As of November 20, 2026, the service is therefore not an appropriate starting point for a new Ethereum infrastructure project. Existing customers have a limited transition period and should inventory their dependencies and begin migration planning rather than waiting until the final weeks.

The retirement notice covers the broader AMB service family, not only Ethereum. AWS provides separate migration guidance for AMB Access Ethereum, Bitcoin and Polygon; AMB Query; and AMB Access Hyperledger Fabric. The replacement path depends on which product and features an application uses.

Migration Options for Existing Ethereum Users

Option 1: Run an Ethereum node on AWS

Organizations that want control over their node environment can deploy their own infrastructure on AWS. AWS points customers to its open-source Blockchain Node Runners project, which provides infrastructure-as-code blueprints for supported blockchain node deployments. For Ethereum, the documented approach can use an execution client and a consensus client, with deployment choices suited to development, availability or historical-state requirements.

This option is not a like-for-like managed service replacement. Node Runners are an infrastructure accelerator, not an AWS-operated node service. The customer becomes responsible for availability, scaling, security, monitoring, software upgrades, backups, storage, synchronization and recovery. A self-managed node may offer more control, but that control comes with operational work and cost.

Option 2: Use a third-party blockchain infrastructure provider

A managed RPC provider can supply Ethereum endpoints without requiring the application team to operate its own full node fleet. AWS names providers such as Alchemy, QuickNode and Kaleido among possible third-party infrastructure options. These are examples, not an endorsement or a claim that every provider offers identical features, pricing, geographic coverage or service guarantees.

Compare providers against the application’s actual requirements: Mainnet and test-network coverage, HTTP and WebSocket support, JSON-RPC methods, historical-state access, request quotas, rate limits, data retention, uptime commitments, latency, authentication, billing and incident support. A low-cost endpoint may not include archive data or the request volume a production application needs.

Choose based on workload, not only price

A small application that makes occasional read calls may have different needs from a wallet backend, exchange, analytics platform or application that depends on real-time WebSocket subscriptions. Self-hosting can make sense when control, customization or predictable infrastructure is important and the team can operate nodes. A third-party provider can reduce operational responsibilities, but introduces provider dependence, pricing and quota considerations. There is no universal best replacement.

Practical AMB Ethereum Migration Checklist

  1. Inventory every dependency. Record the networks used, HTTP and WebSocket endpoints, JSON-RPC methods, Consensus API calls, request volume, batch behavior, historical-state requirements, confirmation rules and any application-specific assumptions.
  2. Choose the replacement architecture. Decide whether to self-manage an Ethereum node on AWS or use a third-party RPC provider. Confirm that the selected option supports the exact network and methods required by the application.
  3. Provision the replacement before changing production traffic. If self-hosting, wait for the node to synchronize fully. Confirm that the execution and consensus components are healthy where both are required.
  4. Update endpoint and authentication handling. Replace AMB endpoint configuration, SigV4 signing or Accessor-token handling with the replacement’s documented connection and authentication method. Keep credentials in a secrets manager rather than source code.
  5. Test equivalent requests. Compare block numbers, chain ID, block and transaction lookups, receipts, contract calls and any historical-state queries. Use fixed block heights or finalized data where possible; the latest block can differ briefly because of propagation delays or reorganizations.
  6. Test subscriptions and recovery. If the application uses WebSockets, check connection stability, reconnection, resubscription, event handling and load-balancer behavior. Do not assume an HTTP-only endpoint supports WebSocket features.
  7. Cut over gradually. Run read-only comparisons first, then shift a controlled share of traffic. Monitor errors, latency, throttling, block height, synchronization lag and application-level correctness.
  8. Keep a rollback window. Retain AMB as a fallback while the replacement is validated and the cutover is monitored. Define the rollback criteria and the date on which the old path will be retired.
  9. Decommission safely. After the rollback period, remove unused IAM permissions, revoke or delete AMB Accessor tokens, remove obsolete endpoints and delete old nodes as appropriate. Confirm that logs, backups and compliance records have been retained according to organizational policy.

A migration is not complete merely because a new endpoint returns a successful response. Production readiness also requires testing error handling, rate limits, historical queries, transaction submission, event subscriptions and the application’s behavior during node or provider interruptions.

Security and Reliability Considerations

  • Protect signing keys. Keep Ethereum private keys outside the RPC node and never send seed phrases to infrastructure providers or support agents.
  • Restrict node access. For self-managed nodes, use private networking, security groups and an authenticated proxy where necessary. Do not expose administrative RPC namespaces to the public internet.
  • Separate environments. Use distinct credentials and endpoints for development, testing and production. Confirm the chain ID before signing or submitting transactions.
  • Monitor synchronization. Track block height, lag, API errors, latency, disk capacity and restart events. An endpoint that responds but is far behind the network can still return misleading application data.
  • Validate transaction handling. Test signing and submission with a controlled procedure. A successful RPC response is not the same as final transaction confirmation.
  • Review provider terms. Understand quotas, billing, data retention, rate limits, support channels and the provider’s incident and security disclosures before moving production workloads.

For applications that also depend on indexed blockchain data, remember that AMB Query is different from a standard Ethereum node endpoint. AWS explains that AMB Query returns normalized, indexed blockchain data. A normal RPC node does not automatically reproduce those query capabilities; replacing AMB Query may require adapting data models, pagination, sorting and application logic.

Amazon Managed Blockchain vs. Replacement Approaches

ApproachMain advantageMain trade-off
Former AMB Access EthereumAWS-managed node infrastructure and AWS-integrated authenticationRetiring; existing access ends September 29, 2027
Self-managed Ethereum node on AWSControl over node configuration, deployment and operationsYour team operates, secures, upgrades and monitors the infrastructure
Third-party RPC providerManaged endpoints without operating your own node fleetProvider-specific pricing, quotas, features and service dependencies

The right choice depends on technical requirements, staffing, reliability objectives, compliance obligations and total operating cost. Compare the replacement against the actual application workload instead of assuming that every AMB feature has a direct one-to-one substitute.

Frequently Asked Questions

Can new customers still start using Amazon Managed Blockchain?

No. AWS stopped accepting new AMB customers on October 29, 2026. As of November 20, 2026, new projects should evaluate a self-managed node or a third-party infrastructure provider instead.

When will Amazon Managed Blockchain stop working?

AWS states that existing customers can continue using AMB until September 29, 2027. After that date, AMB functionality will no longer be accessible. Customers should complete and validate their migration before the end-of-support date.

Does the AMB retirement mean Ethereum is shutting down?

No. Ethereum is a public blockchain maintained by its distributed network of participants. The retirement affects AWS’s managed blockchain service, not Ethereum Mainnet or the ETH asset.

Will an application need to be rewritten to leave AMB Access Ethereum?

Not necessarily. AWS notes that AMB Access Ethereum uses standard blockchain RPC interfaces, so many applications can retain their RPC methods and request bodies while changing endpoints, authentication and network controls. However, applications must test client-specific behavior, response fields, errors, historical data, quotas and any separate Consensus API or WebSocket dependencies.

Does AWS hold the user’s Ethereum wallet or private keys?

No. AMB supplied node access. Customers remained responsible for Ethereum accounts, private keys, transaction signing and smart-contract activity. Moving an RPC endpoint does not transfer or migrate a wallet’s private keys.

Is a self-managed node automatically cheaper than a third-party provider?

No. Self-hosting includes compute, storage, bandwidth, monitoring, backups, engineering time, security maintenance and operational risk. A managed provider has its own usage pricing and limits. Compare total cost for the expected workload rather than only the advertised hourly or request price.

Can I still follow the old Ropsten or Rinkeby setup instructions?

No. AWS’s Ethereum documentation history records that new Ropsten nodes stopped in February 2023, new Rinkeby nodes stopped in August 2023, and Goerli support ended in April 2024. Old screenshots and testnet instructions in archived articles should be treated as historical information, not current deployment guidance.

Where should existing customers begin?

Start with AWS’s official Amazon Managed Blockchain end-of-support notice and its Node and RPC workload migration guide. Inventory the application’s actual dependencies, select a replacement, test it in parallel and keep a rollback plan until the new environment is proven.

Conclusion

Amazon Managed Blockchain made it easier for AWS customers to connect applications to Ethereum nodes without operating every part of the node infrastructure themselves. Its Ethereum support was useful for JSON-RPC access, smart-contract applications and blockchain data workflows, but it never replaced Ethereum itself or removed customer responsibility for accounts and application security.

The important update is the service’s retirement. New customers have not been accepted since October 29, 2026, and existing customers must plan to move before September 29, 2027. For teams using AMB Access Ethereum, the practical next step is to inventory endpoints, APIs, authentication, historical-data needs and subscriptions, then validate either a self-managed AWS node or a suitable third-party provider. Treat migration as an application and operations project, not simply a URL change.

Further reading on Poolyab: Learn about blockchain scalability and Layer 2 solutions, how smart contracts are coded, and smart contract auditing and security.

Continue reading

Related Articles