Use Cases for the AWS Discovery
Currently, we have introduced four types of the Amazon Web Services (AWS) discovery: AWS by Web Services Discovery, Basic AWS by WebServices Discovery, AWS via AWS Config Discovery, and AWS Event Based Discovery. You might wonder in which case to use these types of the AWS discovery. Let’s explore!
This discovery is based on the APIs of all supported AWS services. It discovers the low-level AWS services including AWS API Gateway, Auto Scaling Group, CloudFormation, CloudFront Distribution, DynamoDB, Elastic Compute Cloud (EC2), EC2 Container Registry (ECR), EC2 Container Service (ECS), Elastic Load Balancing (ELB), Lambda Function, Simple Storage Service (S3) Bucket, Relational Database Service (RDS), and Virtual Private Cloud (VPC), using different authentication types in AWS Protocol.
Use case: You want to discover all supported AWS resources but not in real time, or when AWS Config is not turned on (as it is an extra cost to use).
This discovery discovers EC2 instances and IP addresses. The Basic AWS by WebServices job only consumes a Basic unit and is useful for identifying EC2 instances where only inventory discovery is necessary.
Use case: You only need inventory details for servers, so this discovery will identify the EC2 instances in your AWS accounts and thus you know which servers to run the Universal Discovery inventory jobs against.
This discovery uses the Amazon SDK for Java to access AWS Config service and shows the state and configuration of your cloud environment based on Amazon technologies. It discovers all AWS services that AWS by Web Services Discovery supports except ECR and ECS. Also, AWS Config service and AWS SQS service might cost extra fees. You can configure AWS Config to only capture the AWS resources you want to know about.
Use case: You want flexibility in the discovery of some specific AWS resources or regions instead of all AWS resources.
This discovery uses the Amazon SDK for Java to access AWS Simple Queue Service (SQS) service to detect the changes of AWS resources, and represent those changes as quickly as possible in UCMDB. You can see the blog “Another Event Based Discovery - AWS Event Based Discovery” for more details.
Use case: You want to see the changes of AWS resources in near real time so you don’t miss discovering resources that come and go quickly.
So choose the suitable AWS discovery for your environment and enjoy!