Federal Hybrid Cloud Solution

Eight Reasons to Implement a Federal Hybrid Cloud Solution

Hybrid cloud implementations offer flexibility, customization, and the ability to manage the balance between cloud security and ease of use of cloud architecture.

Federal agencies can use existing on-premises solutions for mission-critical workloads, while moving non-critical items to a public cloud.

  1. Speed up IT development and move to market faster with enhanced synergy and sandboxes.
  2. Use existing IT resources, while updating operations in phases, lowering risks and building an agency-specific lessons-learned library.
  3. Adjust solutions, choosing from on-premises, public or private cloud, allowing for the best available technologies for each application and agency-specific use.
  4. Enjoy the flexibility and agility of public cloud solutions, while securing and owning data and applications.
  5. Reduce IT expenses by dropping many in-house operations, freeing IT departments to focus on innovation.
  6. Increase asset use by purchasing only what you need and boosting current capital expenditures.
  7. Follow federal-and agency-specific regulations and policies.
  8. Lower cost and improve disaster recovery processes.

Cloud Infrastructure Features by Deployment Model

Model Cloud Infrastructure Set-up Managed by Location
Private cloud Used by a single organization comprising multiple consumers (e.g., business units) Owned, managed, and operated by the organization On or off premises
Community cloud Used by a specific community of consumers from organizations that have shared concerns (e.g., mission, security requirements, policy, and compliance reviews) Owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination of them On or off premises
Public cloud Used by the general public Owned, managed, and operated by a business, academic, or government organization, or some combination of them On the cloud provider's premises
Hybrid Cloud The cloud infrastructure combines two or more distinct cloud infrastructures (private, community, or public) that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability

Eight Things to Know Before Starting a Federal Hybrid Cloud Implementation

When you can’t migrate all legacy IT infrastructure, applications, or data to the cloud, consider hybrid cloud—a mix of on-site computing resources and commercially provided computing resources.

Make sure the hybrid solution will support the agency's mission, as well as the current IT strategy.

Know the desired business objectives. Understand what security and access levels are required for users to accomplish agency objectives.

Document what systems, infrastructure and data the agency owns. Evaluate what resources require private and which resources are suited for public cloud. Take into account legacy systems, as well as on-premises infrastructure.

This is not an IT project; it will change the way the agency administers IT. It requires training and a solid communications plan that includes all stakeholders.

Do not use private cloud by default.

By using open technology, your agency will not be locked into one vendor or solution, allowing future flexibility. Use the Federal Risk and Authorization Management Program (FedRAMP) templates to ensure compliance, while navigating from vendor to vendor.

Hybrid solutions may involve several technologies and several suppliers. Supplier relationships may be more dynamic than traditional IT, requiring quick on-boarding and sometimes termination. Always plan to migrate data in case a relationship ends. Create a good evaluation system to make sure comparisons between suppliers and offerings are similar.

Develop agency-specific lessons learned from carrying out more manageable solutions first. This step helps to make sure that implementations of mission-critical systems are successful.

Contact Us

Learn more by contacting the GSA cloud experts at 202-969-7113 or at cloudinfo@gsa.gov.

print Share Icon Last Reviewed 2019-05-31