Add support for EBS snapshots and volume restoration on AWS Outposts - #290
Open
skylane38 wants to merge 3 commits into
Open
Add support for EBS snapshots and volume restoration on AWS Outposts#290skylane38 wants to merge 3 commits into
skylane38 wants to merge 3 commits into
Conversation
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.73.0 to 1.79.3. - [Release notes](https://github.com/grpc/grpc-go/releases) - [Commits](grpc/grpc-go@v1.73.0...v1.79.3) --- updated-dependencies: - dependency-name: google.golang.org/grpc dependency-version: 1.79.3 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: skylane38 <santiagobernalgomez1@gmail.com>
When outpostArn is configured in the VolumeSnapshotLocation, snapshots are created on the Outpost and volumes restored from snapshots are also created on the Outpost. The Outpost ARN is resolved with the following priority: 1. ARN from the volume/snapshot metadata (auto-detected by AWS) 2. The outpostArn value configured in VolumeSnapshotLocation This allows Velero to back up and restore workloads running on AWS Outposts without any changes to existing backup/restore workflows. Signed-off-by: skylane38 <santiagobernalgomez1@gmail.com>
Signed-off-by: skylane38 <santiagobernalgomez1@gmail.com>
skylane38
force-pushed
the
feature/outpost-ebs-snapshot-support
branch
from
April 16, 2026 14:36
e6f6486 to
484e3ea
Compare
Member
|
Please create issue in velero repo and link to this PR. |
Author
Created the tracking issue in the Velero repository: vmware-tanzu/velero#9733 |
kaovilai
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
Adds support for creating EBS snapshots and restoring volumes on AWS Outposts
via a new
outpostArnparameter in theVolumeSnapshotLocationconfiguration.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 reduce latency.
How it works
The Outpost ARN is resolved with the following priority:
outpostArnvalue configured inVolumeSnapshotLocationThis allows Velero to work transparently for both standard-region and Outpost volumes.
Changes
velero-plugin-for-aws/volume_snapshotter.go: addedoutpostArnconfig key, struct field, and resolution logic inCreateSnapshotandCreateVolumeFromSnapshotvolumesnapshotlocation.md: documented the newoutpostArnparameterREADME.md: added "AWS Outposts Support for EBS Snapshots" section