Cloud Resources Request for Water Prediction Node

[adean7]

1. Requester Information:
This should include the name and contact information of the person making the request.

• PI's Full Name:
• PI's Affiliated Institute:
• PI's Affiliated Email Address:
• Requester's Full Name: Alex Dean
• Requester's Affiliated Email Address: aldean1@ua.edu

2. Project Information:
Provide CIROH project name associated with this research work along with

• CIROH Project Number (as per smartsheet): P12
• CIROH Project Name: Water Node to Better Utilize Satellite Products, Applications and Services to Inform Decision‐Making in Water Prediction

3. Project Description:
Provide a brief description of the project and its goals. This can help the infrastructure team understand the context and purpose of the requested resources. If your project involves developing software or scripts, briefly describe the software you plan to develop.Please highlight how this project will be benefit from and/or provide benefit to other resources on the shared infrastructure.

The current Water Node is hosted on its own EC2 instance. I would like to request a new EC2 + ECS instance that way I can deploy and test changes to the new Water Node site without bringing down the old Water Node functionality. Once users / stakeholders have been briefed and are on board with the direction of the new Water Node, I will contact the appropriate parties to free up / bring down the EC2 instance related to the old Water Node. This will be an initial implementation to lay the groundwork of the Water Prediction Node processing, which will serve as the central hub for inland water modeling and research in collaboration with NOAA Coastwatch.

4. Resource Requirements:
Specify the compute, storage, and network resources needed for the project. Be as specific as possible about the number of resources required, and any specific configurations or capabilities needed. This information will help the infrastructure team determine the appropriate resources to allocate.

1. Two t3.medium instances (one for EC2 frontend, another for ECS backend)
2. EBS storage 30 GB for each instance

Options:

1. Cloud Provider Options:

• CIROH AWS
• CIROH Google Cloud Platform (GCP)
• CIROH-2i2c JupyterHub
• NWM BigQuery API Access Only

For detailed information about CIROH cloud accounts and APIs:

• AWS: CIROH AWS Account
• Google Cloud: CIROH Google Account
• CIROH-2i2c JupyterHub: CIROH-2i2c JupyterHub
• NWM BigQuery API: NWM BigQuery API

2. Required Services in the Cloud:

List of AWS Services

• EC2
• S3 – public, private, requester pay, bucket name suggestion?
• EBS (Amazon Elastic Block Store)
• EFS
• RDS
• VPC (Virtual Private Cloud)
• DynamoDB
• ECS
• EKS (Kubernetes Cluster)
• Lambda
• Others: please list

List of Google Cloud Services

• Google Compute Engine
• Google BigQuery
• Google Kubernetes Engine (GKE)
• Google Cloud Storage
• Google VPC
• Google IAM
• Google Cloud Functions
• Dataflow
• Other: please list

5. Working Group
Please select the working group associated with this project:

• Hydrologic Modeling and Prediction Working Group
• Hydroinformatics Working Group
• Community Resources Working Group
• Artificial Intelligence Working Group
• Model & Forecast Evaluation Working Group

6. Timeline

Project start date: 3/12/2026

Project end date: 3/12/2027

7. Security and Compliance Requirements:
If there are any specific security or compliance requirements for the project, please state them clearly below. This will help ensure that the necessary security measures are in place for the project.

8. Cost Estimation:
Include any cost estimates or requirements for the project. This will help the infrastructure team select the most cost-effective solutions for the project.
Only required for AWS and GCP access. Ignore for others.

AWS Cost Calculator: https://calculator.aws/#/
Google Cloud Pricing Calculator: https://cloud.google.com/products/calculator

Per AWS calculator: for two t3.medium instances, on demand utilization, with 30GB storage and 125Mbps throughput for each EBS -> 65.54/month

9. Approval:
Requests require management approval, which typically takes 2-3 weeks to process before access is granted.

[arpita0911patel]

This is approved by Steve. Ben - let's create a seperate subaccount waternode for this one to track the cost seperately each month.

[benlee0423]

@arpita0911patel
What would be the subaccount name you prefer? waternode looks ok to me.

[arpita0911patel]

Sure, we can go with that.

[benlee0423]

Subaccount Waternode gets created.