Confluence Retirement

Due to the feedback from stakeholders and our commitment to not adversely impact USGS science activities that Confluence supports, we are extending the migration deadline to January 2023.

In an effort to consolidate USGS hosted Wikis, myUSGS’ Confluence service is targeted for retirement. The official USGS Wiki and collaboration space is now SharePoint. Please migrate existing spaces and content to the SharePoint platform and remove it from Confluence at your earliest convenience. If you need any additional information or have any concerns about this change, please contact Thank you for your prompt attention to this matter.
Skip to end of metadata
Go to start of metadata

This Forum post is the parent page for questions related to the July 13th CDI Monthly Meeting presentation, USGS Cloud Hosting Solutions (CHS) Progress and Activities Kimberly Scott, USGS and Vickie Backus, USGS.

CDI Members can view the slides at the July Monthly Meeting page

Here's a selected slide that points to more information on CHS.


  • No labels


  1. Megan Hines: Are there limitations on what types of applications or data we can put into the CHS environment?

    1. Kimberly: Right now, the biggest limitation is with regard to security, so we are only able to handle data that is classified as FISMA low or moderate. For any application that has an identified technical requirement that we have not yet deployed, our team works with the customer and USGS/DOI management to make these solutions available.

  2. Rob: Are there geospatial related tech stacks in place in the sandbox (Geoserver, ArcGIS Server)? We'd like to test performance of geosptial web service endpoints hosted on AWS.

    1. From Vickie Backus:

      There are no geospatial tech stacks in the place in sandbox. You would be responsible for setting up each of the tech stacks before testing.

      Have you worked in the AWS already? The Sandbox is meant as an exploratory/experimental environment, thus it does not come with extensive technical support. However, currently, we do have customers that are working on deploying either Geoserver or ArcGIS Server and I could put you in contact with them so you could use their experience and knowledge as a resource. In addition, we have a monthly user's forum you could attend and ask questions.

      You can find out more information about the Sandbox under Introducing the CHS Sandbox found here;

      I would be very interested in your results. If you would be willing to share your results, or you have other questions on the Sandbox, please email me at

      FYI: CHS will be standing up ESRI services at the enterprise-level at some point in the future. I do not have an exact date at the time.

  3. Can you point us to more information if we'd like to know more about the new GitHub Enterprise License?

    So this is different from, right?

    1. GitHub Enterprise is very different from


      GitHub Enterprise

      • Internal access only
      • Limited number of users
      • Can exist on ".gov" domain which is ideal.

      • Public and open-source hosting
      • Free
      • Unlimited access
      • Exists on a ".com" domain which is less than ideal


      CHS is investigating a public-facing (with internal-only option) bureau-wide solution for hosting source code. If you have specific requirements for such a solution these would be worth noting at this time.

    2. From Vickie Backus:

      Yes, our github product is different from  The github license CHS has is for a product hosted internally inside the CHS Virtual Data Center (VDC). It is a 50 named user license, and only for people using GitHub for work inside the CHS VDC.  We are looking at potentially using AWS Code Commit in a year or so, once that product matures, and offering it more broadly (right now it is not available in the Oregon West region where CHS VDC is located).