# Creating an EMR Serverless application from the EMR Studio console
<a name="studio"></a>

From the EMR Studio console, create, access, and manage EMR Serverless applications. To navigate to the EMR Studio console, follow the instructions in [Getting started from the console](https://docs.aws.amazon.com/emr/latest/EMR-Serverless-UserGuide/getting-started.html#gs-console). 

## Create an application
<a name="studio-create-app"></a>

With the **Create application** page, create an EMR Serverless application by following these steps.

1. In the **Name** field, enter the name you want to call your application.

1. In the **Type** field, choose Spark or Hive as the type of the application.

1. In the **Release version** field, choose the EMR release number.

1. In the **Architecture** options, choose the instruction set architecture to use. For more information, refer to [Amazon EMR Serverless architecture options](architecture.md).
   + **arm64** — 64-bit ARM architecture; to use Graviton processors
   + **x86\$164** — 64-bit x86 architecture; to use x86-based processors

1. There are two application setup options for the remaining fields: default settings and custom settings. These fields are optional.

   **Default settings** — Default settings allow you to create an application quickly with pre-initialized capacity. This includes one driver and one executor for Spark, and one driver and one Tez Task for Hive. The default settings don't enable network connectivity to your VPCs. The application is configured to stop if idle for 15 minutes, and auto-starts on job submission.

   **Custom settings** — Custom settings allow you to modify the following properties.
   + **Pre-initialized capacity** — The number of drivers and executors or Hive Tez Task workers, and the size of each worker.
   + **Application limits** — The maximum capacity of an application.
   + **Application behavior** — The application's auto-start and auto-stop behavior.
   + **Network connections** — Network connectivity to VPC resources.
   + **Tags** — Custom tags that assign to the application.

   For more information about pre-initialized capacity, application limits, and application behavior, refer to [Configuring an application when working with EMR Serverless](application-capacity.md). For more information about network connectivity, refer to [Configuring VPC access for EMR Serverless applications to connect to data](vpc-access.md).

1. To create the application, choose **Create application** .

# List applications from the EMR Studio console
<a name="studio-list-app"></a>

You can access all existing EMR Serverless applications from the **List applications** page. You can choose an application’s name to navigate to the **Details** page for that application.

# Manage applications from the EMR Studio console
<a name="studio-manage-app"></a>

You can perform the following actions on an application from either the **List applications** page or from a specific application’s **Details** page.

****Start application****  
Choose this option to manually start an application.

****Stop application****  
Choose this option to manually stop an application. An application must have no running jobs to be stopped. To learn more about application state transitions, refer to [Application states](applications.md#application-states).

****Configure application****  
Edit the optional settings for an application from the **Configure application** page. You can change most application settings. For example, change the release label for an application to upgrade it to a different version of Amazon EMR, or switch the architecture from x86\$164 to arm64. The other optional settings are the same as those that are in the **Custom settings** section on the **Create application** page. For more information about the application settings, refer to [Create an application](studio.md#studio-create-app).

****Delete application****  
Choose this option to manually delete an application. You must stop an application to delete it. To learn more about application state transitions, refer to [Application states](applications.md#application-states).