Cloud Services
A cloud service is any service that is made available on demand via the internet from a cloud computing provider. Cloud services are designed to provide scalable access to applications, resources and services. Examples of cloud services include the delivery of computing services including servers, online data storage and backup solutions, networking, software, delivery of analytics, and data processing.
Public cloud services will be known as “COV Cloud” in the future.
Additional information:
COV Ramp (formally ECOS) provide oversight and support services for agencies undertaking the decision to move to cloud-based services. For Approved Application List and Metrics visit COV Ramp page.
Cloud Services Offerings
A
mazon Web Services (AWS) is a cloud computing service, which provides on-demand cloud computing platforms and application programming interface's (API) for reliable, scalable and inexpensive cloud computing services. This allows for building, testing, deploying and managing applications and services. AWS is a set of cloud services to build and run a wide range of applications and services in a highly available host environment.
Network connections back to on-premise data centers are required services and will be charged based on agency consumption, as well as applicable one-time nonrecurring labor fees.
Enterprise architecture will validate the requested cloud service items by comparing them to the cloud workload optimization service (CWOS) artificial intelligence (AI) solution. This is to ensure the workloads are being optimized and right-sized for best use in the AWS environment.
All new services and upgrades are based on current market prices at the time of procurement as part of the initiation process.
Key Features:
- Compute Cloud allows you to increase or decrease storage according to the need of your organization
- Stronger support for business intelligence (Bl) and analytics
- AWS enables you to select an operating system, programming language and database of your choice.
- Broad & deep service offerings
- Robust partner ecosystem
- High transfer stability
- Minimal information is lost during server and storage transfer
- Offers multiple data centers for availability and low latency
- Better DevOps support
Minimum service commitment period: Public cloud services have a minimum service commitment period of one billing cycle. Customers will be invoiced the chargeback resource unit rate for one billing cycle even if the service ordered is installed and decommissioned within the same billing cycle. The chargeback resource unit rate is not prorated for a portion of the billing cycle.
Please visit the Cloud Third Party Use Policy for additional information on the adoption of cloud-based services.
Note: All existing workloads are required to run in the private cloud before being migrated to a public cloud.
The Microsoft Azure MCS enables the transition from on-premises to cloud-hosted applications, new applications hosted in the cloud or moving from one cloud to another. This custom solution consists of hosted infrastructure as a service (IaaS) and platform as a service (PaaS), with shared responsibilities from both the managed public cloud services provider and Microsoft. The managed public cloud services provider delivers the platform as a managed service tailored to VITA policies, including management, delivery and operations of the environment.
The Microsoft Azure MCS provides access to Azure computing services, such as servers, networking, storage, database, deployment, developer tools and software. Cloud computing through Microsoft Azure provides high availability and redundancy.
The Azure MCS introduces enhanced platform capabilities, key differentiators and the value proposition for organizations adopting cloud solutions.
Key features:
-
Enhanced security: The Azure MCS provides 24x7 monitoring, automated compliance checks, and advanced threat protection tools including Microsoft Defender for Cloud and Sentinel. This means agency Azure environments are always watched and protected — reducing risks and meeting strict security standards.
-
Streamlined operations: Routine tasks such as deployments, patching and backups are automated. This minimizes manual work, speeds up processes and helps prevent mistakes.
-
Integrated services: Azure Logic Apps automate the synchronization of Azure virtual machine (VM) configuration data into the VITA configuration management database (CMDB), ensuring accurate, real-time asset management and supporting audit/compliance needs. Integration with the VITA customer care center ServiceNow instance enables automated incident creation and ticketing for detected issues.
-
Azure enterprise dashboard: The Azure enterprise dashboard is used for a high-level status check of your cloud environment and includes the following information:
- Azure subscriptions
- Assessed resources
- Security alerts
- Active recommendations
- Virtual machine performance
Note: All existing workloads are required to run in the private cloud before being migrated to a public cloud.
The cloud service is provided as a means to access computing services such as servers, networking, storage, database, deployment, developer tools and software. The hardware, operating system (OS), software and selected networking features provide high availability, redundancy, security and service options. OCI must be implemented with Oracle FastConnect.
This request is for NEW or to MODIFY existing cloud services located at the OCI. OCI is a cloud computing service, which provides on-demand cloud computing platforms and the application programming interface’s (API) for reliable, scalable and inexpensive cloud computing services. This allows for building, testing, deploying and managing applications and services. OCI is a set of cloud services to build and run a wide range of applications and services in a highly available host environment.
Network connections back to on-premise data centers are required services and will be charged based on agency consumption, as well as applicable one-time labor fees.
Enterprise architecture will validate the requested cloud service items by comparing them to the cloud workload optimization service (CWOS) artificial intelligence (AI) solution. This is to ensure the workloads are being optimized and right-sized for best use in the OCI environment.
All new services and upgrades are based on current market prices at the time of procurement as part of the initiation process.
Key features:
- High performance and predictability
- Fully managed with zero administration
- On-demand throughput and storage provisioning
- Faster development life cycle
- Data modeling
- Simple APIs
- Secondary indexes
- Data security
Minimum service commitment period: Public cloud services have a minimum service commitment period of one billing cycle. Customers will be invoiced for the chargeback resource unit rate for one billing cycle even if the service ordered is installed and decommissioned within the same billing cycle. The chargeback resource unit rate is not prorated for a portion of the billing cycle.
Note: All existing workloads are required to run in the private cloud before being migrated to a public cloud.
View Cloud cost estimates for sample pricing.
Frequently Asked Questions about Cloud Services
How will agencies be billed for this service?
Agencies will be billed using the normal invoicing process. Cloud services will appear on their invoice just like any other service.
What is the rate structure for cloud services?
There are two components to the rate structure. The first component is a fixed month rate that is similar in concept to the type of server rates agencies currently get charged. This rate is charged at the instance level. There is also a one-time set up fee. The second component is a consumption based rate. Charges from AWS, Azure, and OCI will receive a mark-up from VITA and passed on to the customer.
If a question or dispute regarding invoicing occurs, how does an agency address it?
The same process currently used for addressing invoice questions and disputes should be used for cloud services.
When will charges begin to show on agency bills?
There are defined billing triggers that outline when charges show up on a customer bill. Billing triggers are defined by Unisys and documented/implemented by our multisupplier integrator, Science Applications International Corporation (SAIC). SAIC and Unisys will collaborate to determine and document billing triggers so SACM can implement them. Without these triggers, we can't invoice or bill out charges.
If an agency is on a budget program, who assumes the risk if the costs are more than they had projected?
VITA finance will work with the Department of Planning Budget (DPB) to align and set expectations around appropriations.
With the consumption based option, if the server is not ready, does the agency get charged based on when the vendor says it's ready or when the agency said that it should be ready?
There will be billing triggers in place. All customer charges are based on acceptance from the supplier.
Will I be able to monitor my workload with usage alerts?
VITA is currently working to implement this functionality.
Is VITA offering real-time operation monitoring?
VITA is considering the need for this service.
How will spikes in data usage be managed?
Autoscaling of cloud storage will be part of the service offerings.
Is there any way to monitor my cloud usage with the consumable option?
Yes, by setting thresholds in data consumption.
Will agencies be able to provide info on the peak times and request recommendations for optimization?
VITA is considering the need for this service.
Will there be continuous monitoring once agencies have moved their data to the cloud?
Yes, there are continuous improvements being made to the services offered, which could lower costs. Recommendations for modifying your service option will be made to agencies periodically.
Will there be a development and operations (DevOps) information session?
Yes.
When are we publishing these cloud services?
We are currently working to identify a timeline for delivery of these services.
Are there any limitations on what workloads can be moved?
At the commonwealth level, no. However, additional requirements should be included in your considerations, i.e. federal requirements.
How will agencies be able to connect to the different cloud environments?
There will be an initial network charge to connect to a cloud environment.
Will connections to other cloud environments be allowed?
If a SaaS solution is being used, yes. Otherwise, VITA provided services (private cloud, AWS, Azure, and Oracle) must be used.
Will VITA manage enterprise-level activities?
Yes.
Can the details behind the optimization analysis be shared with the agencies?
Yes, this information will be available at a later date.
Did the optimization analysis impact the data center move project?
No.
Why not just "lift and shift?"
VITA wants to avoid any extra costs that could be incurred by the agencies.
Can agencies obtain their own agency cloud?
Yes, through the VITA service portal.
Are the capabilities the same across the cloud suppliers?
Yes, each cloud service provider offers a similar set of services.
Can our cloud environments have different sizes in development than the production environment?
Yes, development and production environments can be different sizes.
Has VITA looked at cyberliability insurance for data in the cloud?
VITA provides cyberliability insurance for data in the commonwealth data center; Cloud data will be handled in a similar way.
Will the agency have access to manage resources within the portal?
Agencies will have some restrictions on rights within their cloud environment as they do within the enterprise private cloud.
Is sensitive data allowed in the cloud?
Yes.
As stated in the Hosted Environment Information Security Standard (SEC525), externally provided services and safeguards used in the electronic transmission or storing of commonwealth and/or citizen data must be risk assessed and security and interoperability must be maintained across all relevant state/national services.
The Code of Virginia § 2-2.2009 states the requirement: "To provide for the security of state government electronic information from unauthorized uses, intrusions or other security threats, the CIO shall direct the development of policies, standards, and guidelines for assessing security risks, determining the appropriate security measures and performing security audits of government electronic information. …" Non-compliance would be in direct violation of the associated Code of Virginia.
Why would current privileges change when I migrate to the cloud?
Current privileges are aligned to future capabilities in the cloud environments.