<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>AWS - Category - Ryland DeGregory</title><link>https://ryland.dev/categories/aws/</link><description>AWS - Category - Ryland DeGregory</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>[CC BY-NC-SA 4.0](https://creativecommons.org/licenses/by-nc-sa/4.0/deed.en)</copyright><lastBuildDate>Tue, 02 Feb 2021 18:32:54 -0500</lastBuildDate><atom:link href="https://ryland.dev/categories/aws/" rel="self" type="application/rss+xml"/><item><title>Map EC2 Snapshots to EBS Volumes and EC2 Instances</title><link>https://ryland.dev/posts/ec2-snapshot-instance-mapping/</link><pubDate>Tue, 02 Feb 2021 18:32:54 -0500</pubDate><author>xxxx</author><guid>https://ryland.dev/posts/ec2-snapshot-instance-mapping/</guid><description>&lt;p>When working with AWS Backup, it can sometimes (often) become difficult to correlate which EBS Volume or EC2 Instance generated each Snapshot (and subsequently is responsible for its cost), especially since the AWS Cost and Usage Report can include millions of line items for large enterprises.&lt;/p></description></item></channel></rss>