Skip to content

Conversation

@TeneBrae93
Copy link
Contributor

@TeneBrae93 TeneBrae93 commented Mar 12, 2025

Summary

This PR updates the Pacu module for downloading EBS snapshots to explicitly pass the region to dsnap’s LocalSnapshot constructor. By doing so, dsnap is forced to create its boto3 session using the correct AWS region (e.g., "us-west-2"), rather than defaulting to "us-east-1". This prevents errors like ResourceNotFoundException when the snapshot exists in a non-default region.

Important

The Dsnap PR needs to also be approved for this to work properly - RhinoSecurityLabs/dsnap#29

dsnap’s init sees that region is provided and creates a boto3 session with that region (e.g., "us-west-2"). This ensures that all subsequent API calls—like list_snapshot_blocks—are directed to the correct AWS region where the snapshot exists.

In summary, this fix decouples the region from the potentially misconfigured Pacu session and guarantees that dsnap is querying AWS in the intended region.
fix trailing whitespace
@TeneBrae93
Copy link
Contributor Author

I believe the errors from the build process are due to it relying on the old version of dsnap; the dsnap PR will need to be approved first

@DaveYesland DaveYesland merged commit 1984f96 into master Mar 17, 2025
2 checks passed
@DaveYesland DaveYesland deleted the fix-dsnap-region branch March 17, 2025 19:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dsnap is not using Pacu supplied region when running ebs__download_snapshots

3 participants