Update index.md

docs/services/cloudservices/aws/documentation/aws-best-practice/index.md

@@ -31,8 +31,11 @@ As the main account administrator for CIROH subaccount, here are some best pract
 
 - **Tagging:** Implement a consistent tagging strategy for resources in all linked accounts. This allows for better cost allocation, resource identification, and easier filtering when managing resources across multiple accounts. Follow [How to tag resources on AWS](https://docs.ciroh.org/docs/services/cloudservices/aws/tagging).
 
-- **Cost allocation**: Allowed limit for **new** subaccount is $500/project per month. Monitor the usage throughout the month and if it reaches above $500/project, notify admin of the subaccount to take necessary actions. For projects expecting more than $500 per month usage, please email ciroh-it-admin@ua.edu in advance to get the approval from higher management.
-
+- **Cost allocation**: Allowed limit for **new** subaccount is $500/project per month. Monitor the usage throughout the month and if it reaches above $500/project, notify admin of the subaccount to take necessary actions. For projects expecting more than $500 per month usage, please email ciroh-it-admin@ua.edu in advance to get the approval from higher management. **Effective Sept 2024**, we transitioned to a new budgeting model (for existing
+users) that provides your CIROH AWS subaccount with a $10,000 budget for
+every 6-month period and monthly max limit of $3000. This change will give
+you more flexibility to plan and execute your research workloads without the
+constraints of a monthly cap.
 
 - **Resource quotas:** Set resource quotas for subaccounts to limit their spending and resource usage. This helps prevent accidental overspending and ensures efficient resource allocation.