Skip to content

This is to verify if the RunTask calls have succeeded or not and alert accordingly

Notifications You must be signed in to change notification settings

srinivasreddych/runtask-verification

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 

Repository files navigation

runtask-verification

Summary: This is to verify if the RunTask calls have succeeded or not and alert accordingly. For ECS Service events, we could just read them or create appropriate cloudwatch event rules to get triggered upon failure to launch tasks, whereas for Batch Jobs/ECS Scheduled tasks/native RunTask API calls, there is currently no straightforward way to get notifed if there are any issues (for ex: AGENT, No ContainerInstances found etc. The solution has SAM template to create CW rule, lambda function, IAM resources.

Commands to run:

These commands were tested on an ec2 instance aws cloudformation package --region us-east-1 --template-file runtask-verification.yaml \ --s3-bucket <<s3_bucket>> \ --output-template-file runtask-verification-transformed.yaml

aws cloudformation deploy --template-file /home/ec2-user/runtask-verification-transformed.yml --stack-name runtask-verification --parameter-overrides NameOfSolution='runtask-verification' --capabilities CAPABILITY_NAMED_IAM

Note:

  1. Replace s3_bucket with the desired s3 bucket in the format bucket-test (do not use 's3://' syntax)

About

This is to verify if the RunTask calls have succeeded or not and alert accordingly

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages