AWS desk
Event date
Published
Last materially updated
No material update since publication
Reviewed by
Avinash Srinivasan, Founder and Lead Engineer
AWS
AWS Backup for Amazon EKS
MG-01

AWS Backup EKS Restore Resource Modifiers (November 2026): What Startups Need to Know

Our recommendation: Adopt YAML resource modifiers for cross-account or cross-Region EKS restores after a successful test restore, and retain manual updates as a fallback.

Affected: Teams restoring Amazon EKS backups, especially backups copied across AWS accounts or AWS Regions, are affected.

What did the vendor release?

On 12 November 2026, AWS announced support for resource modifiers when restoring Amazon Elastic Kubernetes Service (Amazon EKS) backups through AWS Backup. Resource modifiers transform Kubernetes resources during a restore so that the restored cluster can be adapted to its target environment.

This addresses a specific disaster recovery problem. When an EKS backup is copied across AWS accounts or AWS Regions, the restored cluster can retain references associated with the source environment. AWS identifies IAM roles, database endpoints and Amazon ECR registry URIs as examples.

Previously, teams had to find and update these references manually after every restore. The new capability lets teams define transformation rules once in a YAML file. AWS Backup then applies those rules automatically during the restore. AWS says this improves the reliability of cross-account and cross-Region disaster recovery workflows.

The capability is available in all commercial AWS Regions and AWS GovCloud (US) Regions.

Which startups are affected?

The clearest use case is a startup that restores Amazon EKS backups into a different AWS account or Region. Those workflows can involve Kubernetes resources containing references from the original environment.

IAM roles, database endpoints and Amazon ECR registry URIs are the concrete reference types identified by AWS. These are useful starting points for reviewing how a restored cluster is adapted to its destination.

Our recommendation: Prioritize this change if your disaster recovery runbook includes restoring EKS backups across accounts or Regions. Start by identifying the references your team currently changes after a restore. Separate values that belong to the source environment from the values required in the destination.

Our recommendation: If your current restore process already includes manual corrections, document each correction before building a modifier file. Use that record to decide which transformations should become repeatable restore rules.

Adopt it or keep the existing approach?

The previous approach required engineers to locate and update source-specific references manually after each restore. The new approach moves those transformations into YAML rules that AWS Backup applies automatically during restoration.

For a team planning cross-account or cross-Region disaster recovery, that creates a practical choice between maintaining manual post-restore edits and testing a defined set of automated transformations.

Our recommendation: Adopt resource modifiers when the same reference changes recur in restore rehearsals. Start with a small, documented set of transformations. Review the intended source and destination values before using the configuration in a recovery workflow.

Our recommendation: Keep the existing manual procedure until a test restore confirms that the modifier rules produce the intended result. Treat the YAML file as a reviewed operational configuration. Assign ownership and record changes alongside the disaster recovery runbook.

Our recommendation: Judge the change by the accuracy and repeatability of the restored environment, rather than by whether the restore operation finishes. Successful automation should preserve the destination configuration your team expects.

What to check before enabling it?

Our recommendation: Begin with an inventory of your EKS restore scenarios. Identify the source and destination AWS accounts, Regions and environment-specific references for each scenario.

Our recommendation: Read the AWS Backup documentation and launch blog linked from the AWS announcement. Confirm the supported transformation operations and the required YAML structure before preparing rules.

Our recommendation: Build an explicit mapping for the references that need to change. Review IAM role references, database endpoints and Amazon ECR registry URIs where they appear in your workloads. Have another engineer check the destination values against the intended recovery environment.

Our recommendation: Run a restore rehearsal in an isolated test environment. Inspect the restored Kubernetes resources and verify that the expected references were transformed. Check the relevant workload connections and image references as part of the rehearsal.

Our recommendation: Record the test outcome, the modifier file version and any remaining manual steps. Keep a rollback procedure that uses the previously documented restore process if the new rules produce an unexpected result.

Our recommendation: After the rehearsal, update the disaster recovery runbook with the approved YAML configuration, review responsibility and validation checklist. Repeat the test when the destination environment or its important references change.

Sources

  1. AWS Backup now supports resource modifiers for Amazon EKS restores (Amazon Web Services, 12 Nov 2026). Primary source.