Add relations to Log Groups

[jcarter3]

Currently, Log Groups are being queried, but they are not tied to anything. Where possible, add a relationship to the appropriate Lambda, EC2, ECS, EKS, etc resource.

[lpearson-trek10]

Making a more complete list of resources:

• AWS Glue
  • Jobs - /aws-glue/jobs
  • Crawlers - /aws-glue/crawlers
• API Gateway - /aws/apigateway
• CodeBuild - /aws/codebuild
• ContainerInsights - /aws/containerinsights
  • EC2
  • ECS
  • EKS
• EventBridge - /aws/events
• Kinesis Firehose - /aws/kinesisfirehose
• Lambda - /aws/lambda
• RDS
  • Cluster - /aws/rds/cluster
• SageMaker
  • Endpoints - /aws/sagemaker/Endpoints
  • NotebookInstances - /aws/sagemaker/NotebookInstances
  • TrainingJobs - /aws/sagemaker/TrainingJobs

@jcarter3 I am sure there are more but I thought it might be helpful to enumerate some more of the possibles sources and from what I could find seem to be the default paths.

[jcarter3]

Awesome, thanks @lpearson-trek10! I'll work to get a mechanism in place to link these up then work through the list.

[lpearson-trek10]

@jcarter3 what did you have in mind for linking them up?

[jcarter3]

I was originally toying with the idea of a "post processing" step to do a second pass over the resources and add additional links. I think that might be the easiest way to do that for logs? But potentially also let you link lambda/ecs/ec2 env variables to ssm params