Last updated on November 02, 2015

Public and Private Cloud

This article lists frequently asked questions related to IT, security, and operations of Appspace Public and Private Cloud.


FAQ: Public Cloud

  1. Does Public Cloud come SSL enabled?

    By default, Public Cloud comes SSL enabled.

  2. Who has access to my data in Public Cloud?

    A restricted group of Appspace Cloud Operations engineers, with justified and documented reason for accessing the Public Cloud instances. In addition, all access is audited.

  3. What security measures are in place for Public Cloud?

    Appspace employs a number of measures to safeguard the security of your Public Cloud, these include;

    • Physical Security

      For datacenter security refer to: http://www.softlayer.com/security.


    • People and Access

      • A restricted group of Appspace Cloud Operations engineers, with audited access to Public Cloud instances.
      • Firewall permissions prevent management of Public Cloud instances from outside of our datacenter or support facilities.

    • Backups

      • Frequent backups are taken of the Public Cloud instance; these are stored within the local datacenter and offsite.
      • All backup data is encrypted during transmission and at rest.

    • Privacy


  4. What ports are enabled in Public Cloud?

    Both HTTP and HTTPS (Ports 80 & 443) are required for base Appspace functionality.


  5. What SLA is in place for Public Cloud?

    See Appspace Service Level Agreement.


  6. Can I use Active Directory to access Public Cloud?

    This is currently unsupported but is projected as a future enhancement.


FAQ: Private Cloud

  1. How quickly can my Private Cloud be operational?

    Typically within two business days from Appspace receiving the order.


  2. What level of access to I get to my Private Cloud?

    Users have unrestricted access to the application; i.e. Appspace.


  3. Who has access to my Private Cloud data?

    A restricted group of Appspace Cloud Operations engineers, with justified and documented reason for accessing the Private Cloud instances. In addition, all access is audited.


  4. Does my Private Cloud come SSL enabled?

    By default, Private Cloud comes SSL enabled; this certificate is bound to our domain e.g. https://companyx.cloud.appspace.com.


  5. What security measures are in place for my Private Cloud?

    Appspace employs a number of measures to safeguard the security of your Private Cloud, these include;

    • Physical Security

      For datacenter security refer to: http://www.softlayer.com/security.


    • People and Access

      • A restricted group of Appspace Cloud Operations engineers, with audited access to Private Cloud instances.
      • Firewall permissions prevent management of Private Cloud instances from outside of our datacenter or support facilities.

    • Backups

      • Frequent backups are taken of the Private Cloud instance; these are stored within the local datacenter and offsite.
      • All backup data is encrypted during transmission and at rest.

    • Privacy


  6. Can I use a custom domain with my Private Cloud?

    Yes. Private Cloud instances can be mapped to a custom domain, e.g. https://appspace.companyx.com. Customers who wish to use a custom domain are required to provide the appropriate SSL key and certificate.


  7. What HA (High Availability) options do I have with my Private Cloud?

    HA options for Private Cloud are not yet available. Current HA options are for on-premise deployments of Appspace.


  8. When do software updates / patches get deployed to my Private Cloud?

    Private Cloud instances are patched within 30 days of Public Cloud instances being updated.


  9. What ports are enabled in my Private Cloud?

    Both HTTP and HTTPS (Ports 80 & 443) are required for base Appspace functionality.


  10. What SLA is in place for Private Cloud?

    See Appspace Service Level Agreement.


  11. Can I use Active Directory to access Private Cloud?

    Appspace 5.2 and above supports SAML-based Single Sign On (SSO), which allows for users to authenticate using their Active Directory based ldP.


For detailed information on security improvements, please refer to Security changelog.