aws-scripts | Various scripts to make AWS management easier | AWS library

First thing I see is that you're missing the value for Filesystem dimension. Should be something like:

You should be looking at using CloudFormation template to launch and turn off any AWS Resources. Cloudformer is helpful for creating templates for existing resources.

If you still need to use the CLI, you can generate CLI Skeleton JSON that outlines all of the parameters that can be specified for the operation. you can then fill up the values and then create the load balancers

aws elb create-load-balancer --generate-cli-skeleton

in your line you are looking for

the python application inside your scripts folder

I guess this is not what you intended. Try this out:

CloudWatch scripts will get the instance's meta data and write it to a local file /var/tmp/aws-mon/instance-id, if the file or folder has incorrect permission that the script cannot write to file /var/tmp/aws-mon/instance-id, then it may throw error like "print() on closed filehandle MDATA at CloudWatchClient.pm line 167". Sorry for making assumption. A possible scenario is: the root user executed the mon-get-instance-stats.pl or mon-put-instance-data.pl scripts initially, and the scripts has generated the file/folder on place, then the root user switched back to different user and execute the CloudWatch scripts again, this error shows up. To fix this, you need to remove the folder /var/tmp/aws-mon/, and re-execute the CloudWatch scripts to re-generate the folder and files again.

This is the support answer that I get from the aws support on having the same issue may be it will help u too. Also do check your AWSAccessKey for the EC2 instance as well.

Cron doesn't use the login shell's environment variables, so ~ might not resolve to your current user's HOME directory as it would in your manual tests. Try replacing this with the absolute path (e.g., /home/sarul/aws-script-mon/mon-put-instance-data.pl and see if it runs the script correctly.

If you're using local AWS credentials in the user's environment or ~/.aws/config rather than an instance profile, you might need to add these credentials somewhere accessible by cron as well.

Also note that the postfix syslog entries indicate that a mail message of some sort is being queued - perhaps related to an error reported by the script invoked by cron.

Conda environments are used to have isolated setup in terms of Python version and installed libraries. There are not the place to put your own source code. So keep them in the default location ~/anaconda3/envs and do not version control this third party code. Put our own code in the directory /workspace/aws-scripts and use version control there. You can always re-create a conda environment by exporting all settings as a yaml file and using this file to create a new conda environment somewhere else.