In this guide
Before you start
Have your application runtime, required ports and initial resource needs ready. Use a separate test dataset for the first deployment.
Step-by-step workflow
- Identify the deployable artifact
Choose a VM for a Linux environment, a container for an OCI image or a function for an HTTP handler. Write down its ports, dependencies and storage needs.
- Review a published configuration
Open the marketplace, select an offer and read the resources and billing components. The offer defines what you can configure; product guides explain how to use it.
- Configure and confirm
Complete the Resource Composer, review its estimate and confirm the order once. Follow the resulting operation from the console.
- Check the application
Use the assigned access details and test a representative request. Record the configuration and recovery steps before relying on the service.
Create an account
Use Create account to open registration. Follow the email verification steps presented by the sign-up flow, then sign in to the console.
Choose a published offer
Open the marketplace and review the product description, available plans, billing components and configuration options. Choose a VM when you need to administer the operating system, a container for an OCI-packaged service, or a function for a supported request-driven task.
Configure and review
The Resource Composer collects the options supported by the selected product. Review the configuration estimate and order before confirming. Available images, resources, regions and billing intervals depend on the offer.
Follow the resource
Open the console to inspect deployment progress. When the resource is ready, use its available connection details and service actions. Maintain your application, credentials and data according to your operating plan.
Check your result
You can find the new service in the console, understand its current state and reach the application through the configured access path.
If something does not work
If the service is not ready, inspect its operation state before submitting another order. If it is running but unreachable, check the application listener, connection details and network rules.
- The order exists but the service is not ready
- Follow the existing operation and check its status. Creating another order can create another billable resource.
- The service is running but the application does not answer
- Check the application listener, configured port, network rules and access credentials. Resource state alone does not establish application health.