Attachment__3-DRAFT_PROEJCT_AREA_1-USACE_CWBI_1.docx

Project Area 1: Civil Works Business Intelligence (CWBI) U.S. Army Corps of Engineers

STATEMENT OF WORK (SOW)

Cloud Professional Services 01 November 2024 Version 1.0

CUI

CWBI Cloud Professional Services

Table of Contents

Contents

1. Project Area 1 Title Civil Works Business Intelligence Cloud Professional Services

2. Project Summary The U.S. Army Corps of Engineers (USACE) Civil Works Business Intelligence (CWBI) program seeks cloud professional services to operate, maintain, and develop systems, data, applications, and information related primarily to its Civil Works mission. The USACE Civil Works mission is varied and wide-ranging and provides benefits for navigation, flood risk management, hydropower production, environmental stewardship, recreation, irrigation and municipal water supply, emergency response and recovery, and other critical services to the Nation. CWBI requires trained and accredited cloud engineers to execute technical tasks associated with its existing Amazon Web Services (AWS) GovCloud environment to ensure its growing user base has continuous access, responsive capability, innovation, scalability, reliability, and cost-savings opportunities. The cloud professional services contractor must be capable of operating and maintaining the existing environment and supported modules, as well as develop, modernize, and enhance the environment based on USACE, CWBI, and partner input. The contractor will be responsible for working with the CWBI Program Management Office (PMO), CWBI System Engineering Team, CWBI Cybersecurity Team, USACE CIO/G-6, USACE module owners, contractors, and others. The contractor will contribute to the CWBI mission to integrate Civil Works data in a Cloud-smart environment that standardizes data organization and management, ensures cybersecurity, delivers innovative technology solutions, rationalizes the environment, and enhances decision-making. This includes the achievement of the following goals and objectives.

Goal 1. Integrate and advance the delivery of the USACE Civil Works mission.

· Host civil works data using a shared Cloud-smart environment.

· Enable data discovery, ontology, visualization, and mobility.

· Fulfill data statutory and regulatory requirements.

· Rationalize Civil Works data and modules.

· Enhance geospatial environment and capability objectives.

Goal 2. Prioritize data and achieve VAULTIS1 principles in benefit of the USACE Civil Works mission.

· Prioritize data as an essential part of the Civil Works mission.

· Enhance data quality, accuracy, and usefulness.

· Modernize operations data.

· Link Civil Works data assets.

· Enhance data documentation.

· Prepare to share.

1 Visible, Accessible, Understandable, Linked, Trustworthy, Integrated, Secure (VAULTIS)

· Protect and secure data.

· Support knowledge graphing.

Goal 3. Secure USACE Civil Works data.

· Maintain Authority to Operate (ATO).

· Participate in Continuous Monitoring and Risk Management Framework 2.0 process.

· Follow DoD Secure Cloud Computing Architecture (SCCA).

· Educate all to be "cyber fluent".

· Report cybersecurity event results to appropriate stakeholders and remediate as

· requested.

Goal 4. Strengthen the CWBI program foundation.

· Perform Continuous Process Improvement (CPI).

· Ensure customer satisfaction.

· Advance internal communications.

· Advance external communications.

CWBI provides the umbrella structure, support, and guiding procedures to accomplish the migration and enhancement of systems, applications, and data into a common cloud environment. A consolidated approach allows the USACE Civil Works mission to 1) enhance cybersecurity by placing applications and data in an environment where the Risk Management Framework controls are inherited from the Service Provider and is collective for all applications; and 2) transfer the risk associated with building, owning, and maintaining the physical IT, network, storage, and computing capacity. CWBI provides support for applications and data sets not otherwise funded with Direct Appropriation. CWBI also enables application rationalization to ensure each cloud-approach is aligned with Army data strategy, and advances security, mobility, visualization, readiness, and relevance. CWBI is led by a Program Management Office (PMO) that is aligned with USACE’s enterprise project management approach, and an Advisory Board, Field Advocacy Team, and Board of Directors that provides direction and priorities for data, technology, and security in support of USACE campaign plan goals.

3. Background

3.1. Purpose

CWBI is a combination of Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). It has an Informational Impact Level 4 level (IL4) ATO that is aligned with DoD policy and guidance. The contractor will be responsible for all technical tasks associated with operating, maintaining, and developing the GovCloud environment at the IL4 level. CWBI actively supports more than 130 Civil Works modules (see Figure 1) that are organized into business functional areas that include budget management, climate preparedness and resilience, districts, emergency management, enterprise geospatial management, environmental, flood risk management, geotechnical, hydropower, infrastructure, logistics, natural resource management, navigation, planning, project location management, regulatory, tribal, and water management. CWBI requires certain data and systems to be accessible to the public, while other data and systems should be internally accessed by USACE or certain partners specifically.

Figure 1 - CWBI Business Functional Areas and Modules

3.2. Assumptions

· USACE will manage compute/storage requirements and funding through a separate Department of Defense (DoD) initiative.

· USACE will provide each contractor with a government laptop and Common Access Card (CAC) so it can access the GovCloud environment and CorpsNet.

· The contractor will have necessary DoD IL4 cybersecurity and Information Technology (IT) certificates and training to service the environment.

· The contractor will have familiarity with DoD cybersecurity, cloud, and IT standards and requirements.

3.3. Current Environment

CWBI currently has a development (DEV), test (TEST), and production (PROD) cloud environment utilizing separate AWS GovCloud accounts. The environment is tied to the Army Enterprise Cloud Management Agency (ECMA) for compute and storage requirements. CWBI uses the Army ECMA CloudTracker web site to track cloud storage and compute costs. The environment is connected to the Army Endpoint Security Solution (AESS) and the DISA Boundary Cloud Access Point (BCAP). The cyber security service provider (CSSP) is the US Army Command, Control, Communication, Computers, Cyber, Intelligence, Surveillance and Reconnaissance (C5ISR) organization, but CWBI also maintains its own cybersecurity contract and has dedicated cybersecurity staff to support. CWBI documents its risk management framework and security control plan using U.S. Air Force Platform One (P1) Confluence collaboration tools. CWBI also utilizes P1 Jira for its help desk and change management workflow. Jira tickets are used to track all change requests within the CWBI cloud environment, and each contractor will require access to P1 to understand change management requirements.

CWBI’s latest architecture diagram is found in Appendix B.

· 64 Servers and / or Virtual Instances for:

· Combination of primarily Elastic Cloud Compute (EC2) & Elastic Container Service (ECS) used for application hosting

· 47 EC2 instances in primary production account

· 39 ECS clusters running in primary production account

· Code Pipeline used to manage deployments to ECS clusters from Elastic Container Registry (ECR)

· AWS Appstream used as virtualized desktop computing environment

· Most application services are not leveraging redundancy, mirroring or high availability

· Environments separated into different Development, Test, and Production accounts

· Amazon Web Services

· Amazon API Gateway

· Amazon AppStream 2.0

· Amazon Athena

· Amazon Aurora MySQL

· Amazon Aurora PostgreSQL

· Amazon Cloud Directory

· Amazon CloudWatch

· Amazon CloudWatch Logs

· Amazon Data Firehose

· Amazon Detective

· Amazon DocumentDB

· Amazon DynamoDB

· Amazon EC2 Auto Scaling

· Amazon EC2 Image Builder

· Amazon Elastic Block Store

· Amazon Elastic Compute Cloud (EC2)

· Amazon Elastic Container Registry (ECR)

· Amazon Elastic Container Service (ECS)

· Amazon Elastic File System (EFS)

· Amazon Elastic Kubernetes Service (EKS)

· Amazon EventBridge

· Amazon FSx

· Amazon GuardDuty

· Amazon Inspector

· Amazon MQ

· Amazon RDS (MariaDB)

· Amazon RDS (MySQL)

· Amazon RDS (Oracle)

· Amazon RDS (Postgres)

· Amazon RDS (SQL Server)

· Amazon Redshift

· Amazon Route 53

· Amazon SageMaker

· Amazon S3 Glacier

· Amazon Simple Email Service (SES)

· Amazon Simple Notification Service (SNS)

· Amazon Simple Queue Service (SQS)

· Amazon Simple Storage Service (S3)

· Amazon Virtual Private Cloud (VPC)

· Amazon WorkSpaces

· AWS Backup

· AWS Certificate Manager (ACM)

· AWS CloudFormation

· AWS CloudShell

· AWS CloudTrail

· AWS CodeBuild

· AWS CodeCommit

· AWS CodeDeploy

· AWS CodePipeline

· AWS Config

· AWS Cost and Usage Reports

· AWS Cost Explorer

· AWS Directory Service

· AWS Elastic Beanstalk

· AWS Fargate

· AWS Firewall Manager

· AWS Glue

· AWS Identity and Access Management (IAM)

· AWS IAM Identity Center

· AWS Key Management Service (KMS)

· AWS Lambda

· AWS License Manager

· AWS Network Firewall

· AWS Organizations

· AWS Private Certificate Authority

· AWS PrivateLink

· AWS Secrets Manager

· AWS Server Migration Service (SMS)

· AWS Shield

· AWS Snowball

· AWS Storage Gateway

· AWS Systems Manager

· AWS Transit Gateway

· AWS Trusted Advisor

· AWS Well-Architected Tool

· Elastic Load Balancing

· Network Load Balancer (NLB)

· VM Import/Export

· Custom Coding / Scripts

· Web Application Firewall (WAF)

· Fargate container-based WAF

· ADFS Single Sign-On (SSO) for all systems, accounts

· All AWS Infrastructure as Code (IaC)

· AWS Continuous Integration (CI) / Continuous Deployment (CD) pipelines

· Storage Systems

· Primary storage mechanisms leveraged are:

· Elastic Block Storage (EBS) (85 volumes in primary production account)

· Simple Storage Service (200 buckets in primary production account)

· Snapshots used as backup and recovery mechanism for EC2 instances

· Networks

· Currently there are approximately 277 authorized users with elevated privilege access in the account.

· Potential end users include 37,000+ USACE employees as well as public use of the 20+ external facing CWBI modules

· Transactional Traffic, such as Web Transactions, Database Transactions or Application Transactions

· Primary production and test accounts separated into 14 VPCs

· System intra-connectivity managed via VPC peering (65 VPC peering connections in primary production account)

· NIPRnet address spaced VPC peered with DISA BCAP and network traffic to NIPRnet/CorpsNet facing modules routed through BCAP

· Network traffic to External/Public facing modules routed through public-facing internet gateway

· Access to compute services from each environment by the Cloud Engineering, ISSO and development teams primarily routed through SSH bastion

· Primary Web Application Firewall implemented via containerized Apache deployed via ECS cluster. Evaluating implementation of AWS WAF v2 as replacement for this self-hosted WAF

· Server Operating Systems

· Windows 2019

· Oracle Linux 8

· Ubuntu 20.04

· Databases

· Primarily using Amazon RDS

· 63 instances in primary production account

· Platforms include Oracle Enterprise Edition, PostgreSQL, Aurora PostgreSQL, Aurora MySQL, SQL Server, DynamoDB

· There are several EC2 databases present due to feature compatibility, targeting migration to RDS in FY25/FY26

· Middleware

· Ansible

· Caris

· ESRI ArcGIS Enterprise

· Keycloak

· Keyhole / Holebase

· Microsoft Office

· Rundeck

· Tableau

4. Professional Service Requirements

USACE CWBI requires reoccurring cloud professional services to implement and maintain cloud technologies to drive Civil Works operations and improve efficiency. These services should provide targeted guidance and technical expertise to help CWBI manage its cloud- based infrastructure flexibly and cost-effectively on a continuous basis. A summary of required cloud services is listed below in alphabetical order.

Architecture and Design:

· Design scalable, reliable, and cost-effective cloud solutions.

· Create / maintain blueprints for cloud infrastructure, considering factors like security, performance, and high availability.

· Design cloud-native applications, selecting appropriate services (e.g., compute, storage, databases), and optimizing resource utilization.

· Adopt serverless computing and microservices architecture.

· Automate processes and procedures to gain efficiencies and save money.

· Implement data lifecycle management and intelligent tiering processes.

· Ensure Infrastructure as Code approaches are enforced and remain automated to expedite pipeline delivery.

· Ensure that legacy systems undergoing modifications to adapt to a service-enabled architecture will include the design of anti-corruption layers to support the transitional period.

· Build to the highest abstraction of cloud services to meet functional, technical, performance and cost goals. These services include commercial SaaS, PaaS, Database Management as a Service, and so forth, to accelerate testing, accreditation, and fielding to CWBI.

· USACE CWBI enterprise common services, data services, and all DoD Secure Cloud Computing Architecture (SCCA) components when developing, migrating to, and hosting systems/applications in the commercial cloud.

Artificial Intelligence and Machine Learning:

· Design efficient ML solutions with minimal code.

· Manage data and models collaboratively.

· Transition from experimental models to production-ready solutions.

· Deploy and maintain ML models.

· Create efficient data pipelines for model training and deployment.

· Ensure model performance and reliability.

· Address ethical and fairness aspects throughout the ML development process in partnership with CWBI PMO.

Backup and Restore Systems and Capability:

· Backup CWBI systems and data daily.

· Maintain Recovery Time Objective (RTO) of 4-hrs to 24-hours.

· Maintain Recovery Point Objective (RPO) of 4-hrs to 24-hours.

· Retain backups per CWBI Data Strategy and Record Survey Management requirements (up to 3-years).

· Automate backup schedules.

· Create and store volume snapshots.

· Test backup processes to ensure they are valid, and system and data assets can be successfully restored.

· Simulate disaster scenarios to verify data recovery processes.

· Restore systems after major incidents (e.g., hardware failure, cyberattack).

· Monitor backup jobs for errors or failures.

· Notify CWBI PMO of backup issues.

· Implement cloud-to-cloud backups, where necessary.

· Enable versioning and take snapshots of virtual machines and storage resources.

· Ensure backups adhere to data privacy and retention regulations.

Assessment and Strategy:

· Assess existing infrastructure, applications, and business processes.

· Prepare a comprehensive cloud strategy that aligns with CWBI goals and objectives.

· Evaluate cloud adoption approaches.

· Identify cost-saving opportunities.

· Recommend the most suitable cloud-smart solutions.

Data Analytics and Data Services:

· Setup and maintain data lakes, data warehouses, and analytics platforms in the cloud.

· Design and implement solutions for processing, analyzing, and visualizing large datasets.

· Aid CWBI in implementation and automation of data lifecycle policies to ensure data storage is optimized.

· Support module owners and developers with ensuring data can be delivered as a service.

· Ensure that all new and existing applications, systems, or services deemed non-legacy shall expose their data and functionality through service interfaces (for example, OpenAPI specification).

· Ensure data is encrypted during transit and storage.

· Maintain all data within the legal jurisdiction of the United States IAW DFARS 239.7602-2(b).

· Ensure that all data is exposable and consumable through external service data interfaces that are versioned, published, secured, and discoverable to other capability developers and consumers. The contractor shall utilize the modular open systems approach (MOSA) as defined by the Government. (https://www.dsp.dla.mil/Programs/MOSA/)

· Ensure that All Army data sources are developed with built-in data exchange capabilities. Data mapping shall also be implemented to increase efficiency and ease of use of data assets as they are being translated or transformed. At a minimum, programs and initiatives are required to comply with Global Force Management Data Initiative; International Standards for dates; Geopolitical Entities, Names and Codes, Common (GENC); Joint Consultation, Command and Control Exchange Data Model; or Resource Description Framework standards and schemas.

· Ensure that there will be no other form of Inter-Process communication allowed: no direct linking, no direct reads of another data store, no shared-memory model, and no backdoors whatsoever. The only Inter-Process communication allowed is intra-system data exchanges or service interface calls over the network.

· Comply with publishing all application programming interface (API) information/metadata within the Civil Works Data Catalog (https://data.sec.usace.army.mil).

Database Administration:

· Deployment of RDS and EC2 based database instances using IaC.

· Work with the CWBI System Engineering Team to:

· Setup and configure databases on the CWBI cloud platform.

· Support database performance and health monitoring.

· Setup alerts for performance issues, security breaches, and resource utilization.

· Implement robust backup and recovery plans.

· Schedule regular backups, test restoration procedures, and ensure data integrity.

· Management user access, authentication, and authorization.

· Enforce security policies, handle encryption, and protect sensitive data.

· Scale databases horizontally or vertically.

· Setup replication, failover, and load balancing to achieve high availability.

· Avoid overprovisioning and unnecessary expenses.

· Adhere to DoD regulations and USACE policies.

· Maintain audit logs and track changes based upon program requirements.

· Design and test disaster recovery strategies.

· Ensure data availability.

DevSecOps and Continuous Integration/Continuous Deployment (CI/CD):

· Adopt and maintain agile DevSecOps practices within CWBI cloud environment.

· Set up CI/CD pipelines, automate deployments, and improve collaboration between module partners and CWBI teams.

· Standardize cloud migration process by utilizing Infrastructure as Code (IaC), defined pipeline processes, and common scripting.

· Work with CWBI PMO, Cyber Security Team and module development teams to streamline IaC deployment process through environments (Dev-Test-Production).

· Maximize the use of CWBI’s GitHub Enterprise and Platform One (P1) tools and services where technically and economically feasible.

Directory Services:

· Provide role-based access controls through identify and access mechanisms for rights and privileges to Cloud services.

· Support Common Access Card (CAC) authentication to the configuration interfaces of Cloud services.

· Create, modify, and delete user accounts, ensuring proper access permissions per DoD standards.

· Configure authentication methods for secure access.

· Define roles and permissions to control user access to resources.

· Enforce security policies, monitor access logs, and handle security incidents.

· Integrate external cloud directory services, where applicable.

· Manage user accounts as a lifecycle (onboarding, changes, offboarding).

FinOps:

· Optimize cloud spending.

· Analyze usage patterns, recommend cost-saving measures, and monitor resource utilization.

· Aid CWBI to avoid overspending and achieve better cost predictability.

· Allocate cloud costs to specific projects, teams, or modules.

· Identify underutilized resources and right-size instances.

· Implement consistent tagging and labeling practices for cost tracking.

· Predict future spending based on historical data.

· Use automation tools to manage and enforce cost-saving policies.

· Provide clear reports on financial information to CWBI PMO.

· Regularly review and refine FinOps practices.

Migration and Enhancement Services:

· Support migration of existing and new applications, data, and workloads from on- prem environments to the cloud.

· Enhance and modernize existing cloud-based solutions based on defined requirements.

· Plan, execute, and validate the migration process, while minimizing downtime and ensuring data integrity.

· Follow CWBI cloud migration steps and business processes.

Networking:

· Ensure IL4 data and systems traffic flows through the DISA BCAP.

· Implement and manage network load balancing.

· Provide load balancer health checks, such as allowing non-responsive machines to be dropped from the load balancing group.

· Allow for dynamic IP addressing.

· Provide the option to create an isolated virtual private network.

Outreach and Communication:

· Host weekly Office Hours sessions where partners have an opportunity to ask questions about specific Jira tickets.

· Participate in weekly Partner Priority meetings to review Jira tickets and infrastructure priorities.

· Meet with CWBI PMO weekly to review Jira tickets.

· Attend weekly CWBI Technical meeting to collaborate with CWBI PMO, CWBI System Engineering Team, CWBI Cybersecurity Team, and partners.

· Meet monthly with AWS Enterprise Support team.

· Participate in specific meeting with module stakeholders to review requirements, troubleshoot issues, and resolve concerns.

· Submit accomplishments to weekly CWBI situation report.

· Contribute information, best practices, lessons learned, announcements, etc. to CWBI Hub web site.

· Submit monthly invoices and reference each Jira ticket worked.

· Participate in monthly CWBI program synchronization and cloud optimization meeting.

· Collaborate with CWBI PMO members of topics related to development, data, GIS, etc.

· Participate in CWBI Advisory Board and Board of Director meetings, when requested.

· Participate in quarterly CWBI Sharing Sessions, when requested.

· Message to partners when patching occurs.

· Message to partners about system maintenance and outages.

· Manage and share infrastructure schedule.

· Report on available funding, funding balances, and forecasted fund exhaustion.

Security and Compliance:

· Secure cloud resources, data, and applications in partnership with CWBI Cybersecurity Team and module partners. This includes identity and access management (IAM), encryption, network security, and compliance.

· Ensure all new resources are STIG compliant prior to release to partner (Operating System, Apache, IIS, containers, etc.)

· Implement best practices and adhere to DoD regulations, including the latest version of the DoD Cloud Computing Security Requirements Guide and DoD Security Technical Implementation Guide as mandated by DoDI 8500.01.

· Maintain CWBI Authority to Operate and ensure CCRI score remains at or below the “minor concern” category.

· Aid in the timely remediation of identified vulnerabilities.

· Implement zero-trust architecture.

· Support implementation and management of Security Information and Event Management (SIEM) solution.

· Deliver automated notifications to CWBI for critical incident alerts, unplanned traffic spikes, outages, and patching.

· Comply with DoD continuous monitoring and risk management framework (RMF) requirements, including implementation of DoD RMF as governed by DoD Instruction 8510.01 for DoD Information Technology.

· In partnership with CWBI Cybersecurity Team, prepare Plan of Action & Milestones (POAM) documentation.

· Ensure that the cloud environment fully complies or exceeds the security requirements for impact level 4 in the latest version of the DoD Cloud Computing Security Requirements Guide (SRG). Make the environment accessible for the CWBI ISSO team or independent DoD auditors to evaluate the environment prior to the placement of any DoD data in the environment and allow for periodic security reviews of the environment during the performance of this contract.

System Administration:

· Install and configure various components of the cloud system, including servers, networks, storage, and software. Ensure infrastructure is setup correctly and optimized for performance.

· Troubleshoot operational issues and provide technical support for all systems to address any problems that arise.

· Proactively monitor the capabilities and performance of the cloud systems.

· Analyze logs, evaluate system performance, and identify areas for improvement.

· Implement new technologies to enhance efficiency or ensure cybersecurity compliance.

· Configure security settings, manage user accounts, handle software upgrades.

· Document infrastructure, configurations, and processes for future reference.

· Upgrade operating systems and other cloud components.

· Perform regular patching of DEV, TEST, and PROD environments on an agreed upon schedule. Notify parties of patch schedule, completion, and any issues that occur. Ensure issues include root cause explanation.

Testing:

· Assess system performance under different conditions (e.g., load, stress, scalability).

· Validate application functionality.

· Check application compatibility across different resources (e.g., browsers, devices, and operating systems).

· Evaluate user experience and interface design.

· Ensure new changes do not break existing functionality.

· Verify accessibility features.

5. Other Requirements In addition to the cloud professional service requirements listed in Section 4, CWBI also requires additional support with other cloud-related activities and resources.

5.1. Software License

The contractor will be responsible for procuring software licenses on behalf of the USACE CWBI program. The licenses will be owned by USACE CWBI.

· GitHub Enterprise: 150 licenses

· Tableau: 3 Creator (Server) licenses, 100 Viewer (Server) licenses

· Chainguard: 4 Container images

5.2. Scalable Resources

The contractor will provide the ability to increase/decrease resources, as needed, to support any periods of unpredictable high/low usage. Scalable resources include but are not limited to:

· Bandwidth

· Servers (including modifications to instance count, instance type/size, and changes to vCPU/memory of ECS resources)

· Storage

· Database instances (changes to instance type/size, storage)

· Other

5.3. Travel

The contractor will be required to send 1-4 representatives each year to CWBI’s annual in-person meeting. The meeting normally occurs Tuesday – Thursday, with Monday and Friday being a travel day. The location of the annual meeting varies and will be provided to the contracor in advance. The contractor will be responsible for ensuring it does not exceed federal government lodging and per diem rates for the location. Travel receipts will be required for submittal with monthly invoices.

5.4. System Availability

The Contractor will maintain the CWBI environment configuration to support the system availability of 99% or greater per month.

5.5. Help Desk Support

CWBI utilizes Jira as its primary change management collaboration tool. All changes to the CWBI environment require a Jira ticket. The contractor will be responsible for completing tickets per CWBI’s standard ticket workflow and change management business process (see Figure 2).

Figure 2 - CWBI Ticketing Workflow

Tickets will be worked Monday – Friday (except federal holidays) from 0800 – 1700 ET. The contractor will ensure cloud engineering availability to complete tickets within the maximum times identified below:

· BLOCKER: 15 minutes to 2 hours.

· CRITICAL: 2 hours to 2 days.

· HIGH: 2 days – 5 days.

· MEDIUM: 5 days – 10 days.

· LOW: 10 days – 20 days.

5.6. Uptime Monitoring

The contractor will maintain CWBI’s Uptime Kuma monitoring solution that connects to the CWBI Hub site. The uptime monitor will report automated uptime and outages for all CWBI modules.

6. Period of Performance

24 MAR 2025 – 23 MAR 2029

APPENDIX: REFERENCES

A – CWBI Fact Sheet B – CWBI Architecture Diagram (CUI) C – CWBI AWS Account Names and Numbers (CUI) D – CWBI Pinwheel Diagram image1.gif image2.png