The Resources page is where you can see a list of all your resources currently running on AWS. There's a walkthrough of its components in the Overview.
Tim applies several cost tags to each one of your resources. The purpose of the cost tags is to make sure that you can track spend back to their source and also automate your resources based on tag groups. The tags fall under several categories, including:
- Cost domain
Popular with finance teams, “cost domain” allows Tim to track resources by an internal cost center to make it easier for your finance team to do month-end reporting. "Cost domain" is analogous to "Cost center" or "Cost code".
Under the Status column on the Resources page, you will see one of three statuses:
Please refer to Resource Management to get a sense for the various actions that lead to the corresponding states.
A Policy is applied to a tag group or set of resources so that Tim can take your preferences into account when it makes cost-saving recommendations. Tim currently has three template policies that are based on various levels of aggressiveness:
standardis the default Policy. It offers Tim's best blend for cost-saving versus performance. This Policy is usually applied to Developer and Staging environments.
cautiouswhich offers Recommendations that are about 50% less aggressive than Standard. This Policy is usually applied to Production environments.
aggressivewhich offers Recommendations that are about 50% more aggressive than Standard.
Tim's aggressiveness will vary based on the Policy you apply. For example, a Standard Policy may recommend that a Developer resource group be Stopped after six hours of inactivity and Low Engagement, whereas an Aggressive Policy may recommend that a Developer resource group be Stopped after three hours of inactivity and Low Engagement. At this time, Tim will never perform an Action without your approval, no matter the Policy.
You can perform an action by clicking on the checkbox on the left column of the table and clicking either the Stop, Nap, or Terminate button. Within a Slackbot alert or recommendation, you will also see "Leave alone" as an option (this is a feedback loop to teach Tim to nudge you less often).
Clicking Stop will stop the resource but preserve the configurations. When you stop a resource or instance, it is shut down on AWS. The time it takes to stop an instance varies on the Type of resource.
Keep in mind that AWS still charges you for the storage of any Amazon EBS volumes tied to stopped instances. EBS volumes can become a substantial cost if left unchecked, so eventually terminating an instance when it has served its purpose is also important. Tim helps with this as well.
Currently, Tim does not support starting an instance from its UI or the Slackbot. You will need to go into AWS to restart a stopped instance. Once an AWS resource is restarted, it will show as 'running' again on the Resource page.
Each time you restart a stopped instance, AWS charges a minimum of one minute for usage. After one minute, AWS will charge only for the seconds you use.
Napping puts your selected resources on a one-off schedule where they will Stop and then Start again automatically. This is handy if your developers leave work (and it is okay to stop your resources), but you want to have their resources available the next day without delay. You can schedule your resources to nap for the following time periods:
- 6 hours
- 12 hours
- 18 hours
- 24 hours
Terminating a resource completely deletes it.
Deleted, terminated, or released resources can't be recovered.