Appian Licensing for On-Premise to Cloud migration

Hello All,

We are evaluating for a move from On-Premise hosting to Cloud hosting. This is not Appian cloud, but rather having the current on-premise installation to be installed on Cloud. the present Appian version is 17.2 and we plan to keep the same for the Cloud installation. 

Can anyone guide me on

1. how the licensing will work when we move to cloud setup? do we have to change the existing licensing which is for On-Prem application?

2. We have few custom plugins, how can we identify if they are cloud compatible or not?

3. are there any other areas of concern to look for better evaluation.

 

Thanks!

  Discussion posts and replies are publicly visible

Parents
  • +2
    Certified Lead Developer
    Since you aren't using Appian Cloud, some of the answers above are potentially misleading. Bring Your Own Key is only relevant to Appian Cloud. The same is true with "Cloud Approved" plugins. That approval is specific to the Appian Cloud PaaS and is not directly related to your IaaS cloud plans.

    1. You will need new license files as you will be changing servers. All you need to do is request new licenses through support once you have the server information available.

    2. Plugin compatibility has nothing to do with your IaaS setup. As long as your infrastructure is setup to allow the plugins to function as they would on-premise then you are fine. Appian Cloud does not allow certain plugin functionality as it would be a potential conflict for the PaaS offering. For example, a plugin that is allowed to access and modify files on the Appian Cloud servers would be an issue for the PaaS security configuration and would not be "Cloud Approved". If you run that same plugin on your own IaaS cloud your security team may be okay with that level of sever interaction.

    3. You are basically just moving to a new server. The same preparation and validation should be taken into account for shifting to Iaas (i.e. infrastructure, network, security, data migration, etc).
Reply
  • +2
    Certified Lead Developer
    Since you aren't using Appian Cloud, some of the answers above are potentially misleading. Bring Your Own Key is only relevant to Appian Cloud. The same is true with "Cloud Approved" plugins. That approval is specific to the Appian Cloud PaaS and is not directly related to your IaaS cloud plans.

    1. You will need new license files as you will be changing servers. All you need to do is request new licenses through support once you have the server information available.

    2. Plugin compatibility has nothing to do with your IaaS setup. As long as your infrastructure is setup to allow the plugins to function as they would on-premise then you are fine. Appian Cloud does not allow certain plugin functionality as it would be a potential conflict for the PaaS offering. For example, a plugin that is allowed to access and modify files on the Appian Cloud servers would be an issue for the PaaS security configuration and would not be "Cloud Approved". If you run that same plugin on your own IaaS cloud your security team may be okay with that level of sever interaction.

    3. You are basically just moving to a new server. The same preparation and validation should be taken into account for shifting to Iaas (i.e. infrastructure, network, security, data migration, etc).
Children