Recycle Bin Retention Rules

The Recycle Bin is like a safety net for your data in Amazon EBS. If you accidentally delete snapshots or AMIs, they aren't immediately gone. Instead, they go to the Recycle Bin for a specific time before being permanently deleted.

You have the power to bring back any deleted resource from the Recycle Bin as long as it's within the set time. Once you restore something, it leaves the Recycle Bin and becomes a fully functional part of your resources again. However, if you don't restore it in time, after the specified period, it's gone for good.

By using the Recycle Bin, you're adding an extra layer of protection to make sure important data doesn't get lost due to accidental deletions, helping to keep your business running smoothly.

How it's works

  1. Setting it Up:

    • You make rules in the AWS Regions to decide what kind of stuff you want to protect.
    • Rules say which types of things to keep in the Recycle Bin when they get deleted.
    • You also set how long to keep things in the Recycle Bin before they vanish for good.

  2. Types of Rules:

    • Tag-level rules: If you want to protect specific things based on their tags (labels), you use this. You pick certain tags, and anything with those tags goes to the Recycle Bin when deleted.
    • Region-level rules: If you want to protect all things of a certain type in a specific place (Region), you use this. It doesn't need tags; it covers everything of that type in that area.

  3. What Happens in the Recycle Bin:

    • When something is in the Recycle Bin, you can bring it back anytime.
    • It stays there until either:
      • You bring it back, and then it's ready to use.
      • The set time passes, and if you didn't bring it back, it's gone for good.

  4. What it Protects:

    • It looks after Amazon EBS snapshots (like saving a copy of your data at a certain time).
    • Also, it keeps an eye on Amazon EBS-backed Amazon Machine Images (AMIs – like a saved version of a computer setup).

Important Notes:

  • The rules also apply to stored snapshots, and if you delete one that matches a rule, it stays in the Recycle Bin for the rule's time.
  • Rules work even for disabled AMIs (ones not actively in use).

When it comes to safeguarding your valuable AWS resources, setting up retention rules in the Recycle Bin is a crucial step. This guide will walk you through the process of creating retention rules, ensuring that your deleted resources are securely stored before permanent deletion. Let's simplify this process step by step.

Step 1: Understand Required Parameters: To start, you need to specify the resource type you want to protect and the resources that fall under this rule. There are two levels to consider:

  • Tag-level Retention Rule: Identify resources based on tags. You can assign up to 50 tags to each rule, making it highly customizable.
  • Region-level Retention Rule: Protect all resources of a specific type in a particular Region without the need for tags.

Step 2: Set the Retention Period: Decide how long you want to retain the resources in the Recycle Bin after deletion. This period can range up to 1 year (365 days), providing flexibility based on your specific needs.

Step 3: Optional Parameters: You have the option to add more details:

  • Name and Description: Make it easier to manage by giving your retention rule a descriptive name and a brief description.
  • Retention Rule Tags: Use custom tags to organize and identify your retention rules effectively.
  • Locking Rules: Optionally, you can lock retention rules on creation, providing an extra layer of security. If you choose to lock, specify the unlock delay period (7 to 30 days).

Step 4: Creation Methods: You can create a Recycle Bin retention rule using either the Recycle Bin console or the AWS CLI. Choose the method that suits your preference.

Step 5: Walkthrough Using the Recycle Bin Console:

  1. Open the Recycle Bin console here.
  2. In the navigation pane, select "Retention rules" and click "Create retention rule."
  3. Fill in the rule details and settings as per your requirements.
  4. Choose to lock or leave the retention rule unlocked based on your security preferences.
  5. Optionally, add custom tags for better organization.
  6. Click "Create retention rule" to complete the process.

By following these simplified steps, you can efficiently create Recycle Bin retention rules, ensuring the safety and recoverability of your AWS resources.

Conclusion: Securing your AWS resources doesn't have to be complicated. With Recycle Bin retention rules, you gain control over the fate of your deleted resources. Follow this guide, and you'll be on your way to a more organized and secure AWS environment.

Recover Snapshot from Recycle Bin

Title: Restoring Snapshots from the Recycle Bin - Step-by-Step Guide

Instructions:

  1. Accessing the Recycle Bin Console: Open your web browser and go to https://console.aws.amazon.com/rbin/home/.

  2. Navigating to the Recycle Bin: In the navigation pane on the left, locate and click on "Recycle Bin."

  3. Locating Snapshots: The grid displayed on this page provides an overview of all snapshots currently residing in the Recycle Bin. Identify the specific snapshot you want to restore.

  4. Initiating the Restore Process:

    • Select the snapshot you wish to recover.
    • Click on "Recover" to begin the restoration process.

  5. Confirmation Prompt: When prompted, affirm your decision by choosing "Recover" once again.

Congratulations, you have successfully restored a snapshot from the Recycle Bin using the console!

https://www.youtube.com/watch?v=x2T5egBIdQg&list=PL6XT0grm_TfgtwtwUit305qS-HhDvb4du&index=33