velero-io/velero

Support for EBS snapshots and volume restoration on AWS Outposts

Open

#9,733 opened on Apr 16, 2026

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Go (1,550 forks)auto 404
Area/Cloud/AWSHelp wantednative-snapshot

Repository metrics

Stars
 (10,111 stars)
PR merge metrics
 (PR metrics pending)

Description

Feature Request

What would you like to be added?

Support for creating EBS snapshots and restoring volumes on AWS Outposts when using the velero-plugin-for-aws.

Why is this needed?

Users running workloads on AWS Outposts need Velero to create snapshots locally on the Outpost rather than in the parent AWS region, to comply with data residency requirements and to ensure that restored volumes are also placed on the Outpost.

Implementation

A PR has been opened in the velero-plugin-for-aws repository that adds an optional outpostArn parameter to the VolumeSnapshotLocation configuration:

  • vmware-tanzu/velero-plugin-for-aws#290

The Outpost ARN is resolved with the following priority:

  1. ARN from the volume/snapshot metadata (auto-detected by AWS when the resource resides on an Outpost)
  2. The outpostArn value configured in VolumeSnapshotLocation

No changes to the core Velero binary are required.

Contributor guide

Research direction
Review the linked PR in velero plugin for aws (issue #290) to understand the proposed implementation. Examine the AWS Outposts documentation for creating EBS snapshots locally. Test the plugin with an Outpost ARN configured in VolumeSnapshotLocation.
Tech stack
go
Domain
backendinfrastructurecloud
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
KubernetesAWSVelero
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60