Background:
I’m trying to cut the cost of my instance down in half. A t3.medium (2 vCPU, 4 GiB) costs about $.04/hour while a t3.small (2 vCPU, 2 GiB) costs about $.02/hour.

Closed 2 hours ago.

I have a terraform script which creates EC2 (bastion host) and emits out .pem file.

I have a cron job that is scheduled every Saturday and Sunday from an airflow scheduler. The job is such that it performs ssh to a particular instance and then executes a java -cp command to run execute a particular file from a jar which is already present on a particular path. To be specific, there are 5 cron job each of which run once every weekend on a fixed time.
The instance is absolutely free during the weekdays. I need a solution which can can help me reduce the cost of this instance, maybe the instance get stopped or terminated automatically on monday and start again on friday night. I don’t want to go with the lambda approach where I mention the instance id or any identifier which triggers the start and stop of the instance.

I have a cron job that is scheduled every Saturday and Sunday from an airflow scheduler. The job is such that it performs ssh to a particular instance and then executes a java -cp command to run execute a particular file from a jar which is already present on a particular path. To be specific, there are 5 cron job each of which run once every weekend on a fixed time.
The instance is absolutely free during the weekdays. I need a solution which can can help me reduce the cost of this instance, maybe the instance get stopped or terminated automatically on monday and start again on friday night. I don’t want to go with the lambda approach where I mention the instance id or any identifier which triggers the start and stop of the instance.

I am trying to create an EC2 instance on AWS in an automatical manner.
I am calling a HTTP method through an amazon endpoint using a HTTP client installed on my computer, which clearly is not on AWS.

I am trying to create an EC2 instance on AWS in an automatical manner.
I am calling a HTTP method through an amazon endpoint using a HTTP client installed on my computer, which clearly is not on AWS.

I have attached an EBS (elastic block storage) volume to two EC2 instances to achieve a requirement where one ec2 instance performs some actions and creates files in the volume in specific directory and other ec2 instance uses these file to do some further actions. However it is not working as expected, the files and directories created on from first ec2 are not showing in same volume when accessed through another ec2. It there anything I am missing. Please suggest how it can be done if its not the correct way.

I’ve generated the instance to be all defaults allowing all connections from any ip and im still not able to connect. My pem has 400 permission. All it tells me no matter what I try is that the connection timed out. Any guidance on where to start to sort this out would be greatly appreciated.

I’ve generated the instance to be all defaults allowing all connections from any ip and im still not able to connect. My pem has 400 permission. All it tells me no matter what I try is that the connection timed out. Any guidance on where to start to sort this out would be greatly appreciated.