Rename Operational_Instructions/AWS_and_Pinecone_Accounts_for_LiveRAG.md to Operational_Instructions/AWS_Accounts_for_LiveRAG.md

Operational_Instructions/{AWS_and_Pinecone_Accounts_for_LiveRAG.md → AWS_Accounts_for_LiveRAG.md}

@@ -1,20 +1,18 @@
-# AWS and Pinecone Accounts for LiveRAG
-
-## Using AWS Accounts
+# AWS Accounts for LiveRAG
 
 During the LiveRAG Challenge, participants may use two AWS accounts:
-- **Personal AWS Account** – This is your private AWS account, where you can apply AWS credits provided for the competition.
-- **TII-Provided AWS Account** – This account is managed by TII and grants access to the dense (Pinecone) and sparse (OpenSearch) pre-built indices.
+- **AWS Team Account** – This is your private AWS account for your team, where you can apply AWS credits provided for the competition.
+- **AWS LiveRAG Account** – This account is managed by TII and grants access to the dense (Pinecone) and sparse (OpenSearch) pre-built indices.  
 
 Using these accounts is optional but highly recommended to optimize both cost and effort.
 
-## Using Your Personal AWS Account with AWS Credits
+## Using Your AWS Team Account with AWS Credits
 
 Each participating group receives AWS credits for the duration of the competition.
 The credits are limited, and any usage beyond the allocated amount will be charged to your personal payment method.
 To ensure your credits are properly applied, follow the official AWS instructions [here](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/useconsolidatedbilling-credits.html).
 
-### Personal AWS Account Setup and Credit Application Steps
+### AWS Team Account Setup and Credit Application Steps
 
 1. **Create an AWS Account** – Sign up for an AWS account and add a payment method (typically a credit card). If you have an existing AWS account you may reuse it.
 2. **Apply AWS Credits** – Follow the instructions in the provided AWS documentation to redeem and apply your credits.
@@ -22,26 +20,12 @@ To ensure your credits are properly applied, follow the official AWS instruction
    - Use AWS Cost Management tools to monitor spending.
    - Set up billing alarms using AWS CloudWatch to receive notifications when costs exceed predefined thresholds.
 
-### Cost Optimization Recommendations
-
-TII and AWS have estimated the cost of a typical team’s infrastructure, including GPU usage, and AWS has provided credits accordingly.
-However, individual teams may have varying requirements, so cost management is essential:
-- **Shut down unused resources** – Always shut down GPUs and other compute instances when not in use.
-- **Experiment on smaller datasets first** – This approach speeds up iteration cycles and reduces expenses before scaling up to larger datasets.
-
-## Using the TII-Provided AWS Account
-
-The TII-provided AWS account is strictly limited to specific use cases, primarily for accessing pre-built indices. These include:
-
-- A **Sparse OpenSearch Index** hosted by AWS.
-- A **Dense Pinecone Index** hosted by Pinecone, with access credentials stored on AWS.
-
 
 ### Access and Setup Instructions
 
-To gain access and configure the TII-Provided AWS account, follow these steps:
+To gain access and configure the AWS LiveRAG account, follow these steps:
 
-1. **Receive Sign-In Details** – You will receive an email with login credentials from the organizers.
+1. **Receive Sign-In Details** – You should have received an email with login credentials from the organizers.
 2. **Sign In & Change Password** – Log in to the AWS console and update your password.
 3. **Create AWS Command Line Interface (CLI) Credentials** – Generate an access key and secret for CLI usage.
 4. **Configure AWS CLI Profile** – Run the following command to set up the CLI for this account and follow the instructions:
@@ -73,7 +57,12 @@ You're welcome to build your own Pinecone/OpenSearch, or other indices. We encou
 
 For instructions pertaining to building your own Pinecone index see [here](Pinecone_for_LiveRAG.md).
 
-## Summary of Key Recommendations
+### Cost Optimization Recommendations
+
+We have estimated the cost of a typical team’s infrastructure, including GPU usage, and AWS has provided credits accordingly.
+However, individual teams may have varying requirements, so cost management is essential:
+- **Shut down unused resources** – Always shut down GPUs and other compute instances when not in use.
+- **Experiment on smaller datasets first** – This approach speeds up iteration cycles and reduces expenses before scaling up to larger datasets.
 
 | **Action**            | **Recommendation**                                           |
 |:-----------------------|:-------------------------------------------------------------|