Editing Cloud Profiles

Edit a cloud profile to modify how you access the provider of a public or private cloud service.
Important: If virtual environments based on this profile are already deployed (see the Deployed Instances column of the grid), changing the settings might cause that Silk Central will not delete these unused environments automatically anymore.
  1. In the menu, click Administration > Execution Environment.
  2. Click the Cloud Providers tab.
  3. Click in the Actions column to synchronize the list of execution servers that use templates from this cloud provider. This will remove all virtual execution servers of this profile that have a template assigned which no longer exists. After a Hotfix has been applied, this will also update the templates of automatically created virtual execution servers.
  4. Click (Edit) in the Actions column of the profile that you want to edit. The Edit Cloud Provider Profile dialog box appears.
  5. In the Name field, enter a name for the profile. This name will be displayed in the list of profiles when creating a cloud-hosted execution server.
  6. Enter valid credentials to remotely access the cloud system in the Username and Password fields. For Amazon Web Services, this is the Access Key and the Secret Key.
  7. To configure a VMware vCloud profile (skip this step to configure a different profile):
    1. Enter the URL with the hostname only and do not append /cloud/org/<organization name> as you would when accessing the system with a Web browser. Example: https://vdirectorweb.
    2. Optional: Version: Leave the field empty if you are using VMware vCloud Director 5.5 (default). Enter V5.1 if you are using vCloud Director 5.1.
    3. Organization: Enter the name of the vCloud organization that you want to access, for example dev_org.
  8. To configure an Amazon Web Services profile (skip this step to configure a different profile):
    1. Region: Select the region in which you want to deploy your instance.
    2. Instance Type: The instance types that Amazon offers. This defines for example how much RAM and CPU power your instance will have. Note that this also has an impact on lease costs. For more information, visit the Amazon EC2 Instances page.
    3. Keep instance alive on connection error: Select true if you want the instance to stay alive when the connection between the application server and the Amazon instance breaks.
  9. Click Test Connection to perform a test connection to the cloud provider with the information that you have entered.
  10. Click OK to save your settings.
Parent topic: Cloud Integration