add Data Landscape & Egress Estimation stage #46
Merged
Conversation
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
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.
Summary
Adds an opt-in Stage #7 to the assessment pipeline:
--egresson eitherawsorazuremeasures data-bearing resources in the assessed scope and estimates the one-time internet egress fee for moving that data out of the provider. Runs after report generation, uses only the existing Reader / ViewOnlyAccess permissions, and cannot fail the main assessment — a Stage 7 failure exits with the newEGRESScode (9) while the standard reports are still produced.Marked alpha: sizes are point-in-time estimates from provider metrics (capacity metrics can lag ~48 h; provisioned disks count as upper bounds; backup vaults are not sized), and pricing is USD list prices only.
What ships
core/utils_egress_azure.pysizes Storage Accounts (with blob-tier split), Managed Disks, Snapshots, SQL Databases, Cosmos DB, PostgreSQL/MySQL Flexible Servers, and detects Recovery Services vaults;core/utils_egress_aws.pysizes S3 buckets (with StorageType tier split), EBS volumes, EBS snapshots, RDS instances (with Aurora flagged not-sized), DynamoDB tables, and detects AWS Backup vaults. Azure uses the Monitor REST API directly (no new SDK); AWS uses CloudWatchGetMetricData.reports/<ts>/egress.html(dashboard),egress.pdf(executive summary: Summary + Scope + Coverage + Data Landscape + Estimated Costs + Appendix listing the exact prices used), andraw_data/egress_estimate.json.egresspricingtable indatasets/data.db(effective-dated rows, per-row unit/zone/currency), so price updates ship without a code release. Every report folder captures its own point-in-time snapshot viaassessment.db, making re-renders fully reproducible and pinning the PDF appendix numbers per report.Impact on existing behavior
None.