Launching a Stack

Learn how to launch a stack using the Console and API interfaces.

  • Tip

    When you create a stack, potentially many other resources are involved (for example, an instance, a cloud network, or a subnet), aside from the stacks and jobs resources. You must have the required access to all involved resources to create a stack. Those other resources can be in the same compartment  with the instance or in other compartments. You must have the required level of access to each of the compartments involved in order to launch the instance. This is also true when you attach a volume to an instance; they don't have to be in the same compartment, but if they're not, you need the required level of access to each of the compartments.
    1. Open the navigation menu and click Marketplace. Under Marketplace, click All Applications.
    2. Click the listing that you're interested in.
    3. Review the Usage Instructions tab and ensure you understand what you will need to deploy and to access the instance after the stack finishes deployment.
    4. Under Version, click the package version of the stack that you want to install. By default, the menu displays the latest version.
    5. Under Compartment, click the name of the compartment where you want to launch the instance. (If you don't have permissions to launch the instance in the selected compartment, it will be launched in the root compartment instead.)
    6. Select the check box to accept the terms of use, and then click Launch Stack.
    7. On the Stack Information page, configure the following:
      1. Name. Optionally, provide a name by which you can refer to the stack after it's deployed.
        Avoid entering confidential information.
      2. Description. Optionally, provide a description of the stack. For example, you can specify the name of the application that will run on the instance after the stack is deployed.
      3. Create in Compartment. This is the compartment where the stack will be created in the tenancy. (Stacks are attached to a specific region. However, where necessary, the resources on a given stack can be deployed across multiple regions.)
      4. Tags. If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator.
      5. When you are ready, click Next.
    8. On the Configure Variables page, verify that the values for variables extracted from the Terraform configuration file are as you want them. Some variables might be required, but don't have a default value and must be configured before you can proceed. These vary from listing to listing, but often include the following: availability domain and compartment. Optionally, you can change default values, such as any display names automatically given to resources, to help differentiate them. For some stacks, you can customize additional variables by selecting the Additional Customization or WLS Instance Advanced Configuration check box. The variables in these sections otherwise use default values. When you are ready, click Next.
    9. On the Review page, confirm that variables have been configured properly. (Marketplace does not display variables that have default values or variables that you didn't change.) Then, click Create.

    Resource Manager runs the plan job and the apply job to create stack resources accordingly. The information you need to connect to the instance created as part of the stack can appear in the Application Information tab or in the Usage Information or Related Documents sections of the listing.

  • This task is not available in the CLI.

  • Use the following operations to work with listings: