Skip to main content
undefined
undefined

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

undefined

Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Infrastructure under cloud.gov

Table of Contents

The infrastructure underlying cloud.gov

cloud.gov runs on top of Infrastructure as a Service provided by Amazon Web Services (AWS) in the AWS GovCloud partition (specifically within the us-gov-west-1 region), which has a FedRAMP JAB P-ATO at the High impact level. GovCloud also offers support for other formal compliance needs such as ITAR compliance.

Services in our marketplace

cloud.gov brokers instances of:

  • FedRAMP JAB-authorized services available in AWS GovCloud and
  • Services run directly inside cloud.gov (which benefit from our own FedRAMP JAB authorization)

In principle, cloud.gov can broker any service provider for which there is an implementation of the Open Service Broker API. For more information, see our docs on extending the marketplace.

Other IaaS vendors we can support

cloud.gov is a Platform as a Service (PaaS), which offers an additional level of services and functions beyond the basics offered by an Infrastructure as a Service (IaaS) provider. We built cloud.gov based on the Cloud Foundry open source project, which was designed to be compatible with multiple IaaS providers. For that reason, it would be possible to provide cloud.gov services using Google Cloud Platform, Microsoft Azure, or any public, commercial, or private OpenStack instance in the future.

If you’re an IaaS vendor interested in offering your solution to cloud.gov users

We recommend examining the BOSH Cloud Provider Interface (CPI) documentation. Provide a CPI which makes it possible for BOSH to manipulate your cloud. This will enable cloud.gov (or any other PaaS based on Cloud Foundry) to offer alternative API endpoints corresponding to different IaaS providers with little effort. cloud.gov will deploy on new IaaS providers and expose those as new API endpoints as warranted by agency demand.