Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-2531

Investigate: Lambda function to shuts down EC2s at 18:30 every day

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      We have many EC2's used for development purposes.

      EC2's with tag "Stack" equal to "Develop" are all used for development purposes only.

      To save money, we should change their status to "Stopped" at the end of very workday - 6:30 pm Easter Standard Time.

      Currently, Dr. Loraine manually does this - when she remembers to do it.

      We need an automated approach instead.

      A lambda function attached to the Loraine Lab account would probably be the best approach - it is simple and relatively easy to set up.

      For example, according to this documentation – https://aws.amazon.com/premiumsupport/knowledge-center/start-stop-lambda-cloudwatch/ – you can create a lambda function that would then be triggered by a timer configured in cloudwatch.

      Alternatively, you can do something like this - read: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/UsingAlarmActions.html#AddingStopActions

      For this task, investigate the best way to automate stopping ECs with Stack equal to Develop. It should be super simple and easy for Dr. Loraine to manage and maintain.

      Give an overview of the solution here.

        Attachments

          Issue Links

            Activity

            ann.loraine Ann Loraine created issue -
            ann.loraine Ann Loraine made changes -
            Field Original Value New Value
            Epic Link IGBF-2323 [ 18477 ]
            ann.loraine Ann Loraine made changes -
            Description We have many EC2's used for development purposes.

            EC2's with tag "Stack" equal to "Develop" are all used for development purposes only.

            To save money, we should change their status to "Stopped" at the end of very workday - 6:30 pm Easter Standard Time.

            Currently, Dr. Loraine manually does this - when she remembers to do it.

            We need an automated approach instead.

            A lambda function attached to the Loraine Lab account would probably be the best approach - it is simple and relatively easy to set up. There may be an even simpler and easier solution.

            For this task, investigate the best way to automate stopping ECs with Stack equal to Develop.

            Give an overview of the solution here.
            We have many EC2's used for development purposes.

            EC2's with tag "Stack" equal to "Develop" are all used for development purposes only.

            To save money, we should change their status to "Stopped" at the end of very workday - 6:30 pm Easter Standard Time.

            Currently, Dr. Loraine manually does this - when she remembers to do it.

            We need an automated approach instead.

            A lambda function attached to the Loraine Lab account would probably be the best approach - it is simple and relatively easy to set up.

            For example, according to this documentation -- https://aws.amazon.com/premiumsupport/knowledge-center/start-stop-lambda-cloudwatch/ -- you can create a lambda function that would then be triggered by a timer configured in cloudwatch.

            For this task, investigate the best way to automate stopping ECs with Stack equal to Develop. It should be super simple and easy for Dr. Loraine to manage and maintain.

            Give an overview of the solution here.
            ann.loraine Ann Loraine made changes -
            Description We have many EC2's used for development purposes.

            EC2's with tag "Stack" equal to "Develop" are all used for development purposes only.

            To save money, we should change their status to "Stopped" at the end of very workday - 6:30 pm Easter Standard Time.

            Currently, Dr. Loraine manually does this - when she remembers to do it.

            We need an automated approach instead.

            A lambda function attached to the Loraine Lab account would probably be the best approach - it is simple and relatively easy to set up.

            For example, according to this documentation -- https://aws.amazon.com/premiumsupport/knowledge-center/start-stop-lambda-cloudwatch/ -- you can create a lambda function that would then be triggered by a timer configured in cloudwatch.

            For this task, investigate the best way to automate stopping ECs with Stack equal to Develop. It should be super simple and easy for Dr. Loraine to manage and maintain.

            Give an overview of the solution here.
            We have many EC2's used for development purposes.

            EC2's with tag "Stack" equal to "Develop" are all used for development purposes only.

            To save money, we should change their status to "Stopped" at the end of very workday - 6:30 pm Easter Standard Time.

            Currently, Dr. Loraine manually does this - when she remembers to do it.

            We need an automated approach instead.

            A lambda function attached to the Loraine Lab account would probably be the best approach - it is simple and relatively easy to set up.

            For example, according to this documentation -- https://aws.amazon.com/premiumsupport/knowledge-center/start-stop-lambda-cloudwatch/ -- you can create a lambda function that would then be triggered by a timer configured in cloudwatch.

            Alternatively, you can do something like this - read: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/UsingAlarmActions.html#AddingStopActions

            For this task, investigate the best way to automate stopping ECs with Stack equal to Develop. It should be super simple and easy for Dr. Loraine to manage and maintain.

            Give an overview of the solution here.
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Assignee Chirag Chandrahas Shetty [ chirag24 ]
            ann.loraine Ann Loraine made changes -
            Link This issue relates to IGBF-2533 [ IGBF-2533 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Status To-Do [ 10305 ] In Progress [ 3 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Status In Progress [ 3 ] Needs 1st Level Review [ 10005 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Assignee Chirag Chandrahas Shetty [ chirag24 ]
            ann.loraine Ann Loraine made changes -
            Status Needs 1st Level Review [ 10005 ] First Level Review in Progress [ 10301 ]
            ann.loraine Ann Loraine made changes -
            Assignee Ann Loraine [ aloraine ]
            ann.loraine Ann Loraine made changes -
            Status First Level Review in Progress [ 10301 ] To-Do [ 10305 ]
            ann.loraine Ann Loraine made changes -
            Assignee Ann Loraine [ aloraine ] Chirag Chandrahas Shetty [ chirag24 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Status To-Do [ 10305 ] Pull Request Submitted [ 10101 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Status Pull Request Submitted [ 10101 ] Reviewing Pull Request [ 10303 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Status Reviewing Pull Request [ 10303 ] Merged Needs Testing [ 10002 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Status Merged Needs Testing [ 10002 ] Post-merge Testing In Progress [ 10003 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Resolution Done [ 10000 ]
            Status Post-merge Testing In Progress [ 10003 ] Closed [ 6 ]
            ann.loraine Ann Loraine made changes -
            Resolution Done [ 10000 ]
            Status Closed [ 6 ] To-Do [ 10305 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Status To-Do [ 10305 ] In Progress [ 3 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Status In Progress [ 3 ] Needs 1st Level Review [ 10005 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Assignee Chirag Chandrahas Shetty [ chirag24 ] Ann Loraine [ aloraine ]
            ann.loraine Ann Loraine made changes -
            Status Needs 1st Level Review [ 10005 ] First Level Review in Progress [ 10301 ]
            ann.loraine Ann Loraine made changes -
            Status First Level Review in Progress [ 10301 ] Ready for Pull Request [ 10304 ]
            ann.loraine Ann Loraine made changes -
            Status Ready for Pull Request [ 10304 ] Pull Request Submitted [ 10101 ]
            ann.loraine Ann Loraine made changes -
            Status Pull Request Submitted [ 10101 ] Reviewing Pull Request [ 10303 ]
            ann.loraine Ann Loraine made changes -
            Status Reviewing Pull Request [ 10303 ] Merged Needs Testing [ 10002 ]
            ann.loraine Ann Loraine made changes -
            Status Merged Needs Testing [ 10002 ] Post-merge Testing In Progress [ 10003 ]
            ann.loraine Ann Loraine made changes -
            Resolution Done [ 10000 ]
            Status Post-merge Testing In Progress [ 10003 ] Closed [ 6 ]
            ann.loraine Ann Loraine made changes -
            Assignee Ann Loraine [ aloraine ] Chirag Chandrahas Shetty [ chirag24 ]

              People

              • Assignee:
                chirag24 Chirag Chandrahas Shetty (Inactive)
                Reporter:
                ann.loraine Ann Loraine
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: