AWS Resource Groups - KnowHow(s) - Series 2

Welcome folks !! Another learning series for AWS Resource Groups. AWS Resource Groups has been here for quite some years now and let us pick this up learning series as a pre-requisite knowing for future learnings.

  

Getting Started:

       To know about Why and How to use AWS Resource Groups

Pre-requisite:

• AWS Account & Login 
• Access to create few of the resources in AWS like S3, EC2, RDS etc( at least a couple of them is recommended for this learning)

What is AWS Resource Groups:
     Before even we understand what is Resource Groups let us understand Tags, as the former is an upstream of Tags. Tags are basically Key:Value pair of information which is used to identify or classify each resources in AWS. As name suggests, AWS Resource Groups are way of grouping the resources using Tags defined against resources


Why AWS Resource Groups:  
    Though Resources can be tagged(upto a maximum of 50 key-value pairs for a resource) grouping the resources based on a common need or purpose, helps in applying changes, automation against all of these resources at one stretch, clearly and efficiently. This enhances optimization of time and effort in the world of automation

All about AWS Resource Groups:

      Resource Group is about a collection of AWS resource groups in the same region. They are two types by which they can be queried/viewed, basically

•  Tag based
• Filters resource items based on the Tag(Key:Value) pairs defined in the AWS Resource group definition

• AWS Cloudformation stack based
• This type basically looks for identical resources from inside your AWS Cloudformation stack in the region and looks for grouping the resources from within that stack
• Stacks within the current region is what is looked for
• Only one Cloudformation stack can be looked into for grouping 

 AWS Resource Groups Use cases: 

1. Group resources like EC2, S3, RDS etc based on domain or teams or environments
2. Apply patches to resources based on criteria like sales domain or purchase domain EC2 or S3 resources
3. Gather logs from specific environment resources like PAT, QA or so