Control your AWS spend
Last updated
Last updated
IDEA offers multiple ways to make sure you will stay within budget while running your Engineer & Design workloads on AWS
Assuming you are on-boarding a new team, here are our recommend best practices:
1 - .
2 - .
3 - .
4 - limit the queue ACLs to the project created step 3.
5 - .
6 - .
7 - Create a Budget to make sure the new team won't spend more than what's authorized.
8 - or for your queue.
Only allow specific individual users or/and LDAP groups to submit jobs or provision virtual desktops. .
Control what type of EC2 instances can be provisioned for any given queue.
Stay on top of your AWS costs in real time. Quickly visualize your overall usage and find answers to your most common questions:
Who are my top users?
How much money did we spend for Project A?
How much storage did we use for Queue B?
Where my money is going (storage, compute ...)
Etc ...
You can limit a your simulation jobs to only un on Reserved Instances if you specify force_ri=True () flag at job submission or . Your job will stay in the queue if you do not have any Reserved Instance available.
You can limit the number of or at the queue level.
Creating an AWS Budget will ensure jobs can't be submitted if the budget allocated to the team/queue/project has exceeded the authorized amount.