This guide covers the essential management operations for Runpod Serverless endpoints, helping you deploy, configure, and maintain your Serverless applications effectively.
Create a new Serverless endpoint through the Runpod web interface:
You can optimize cost and availability by specifying GPU preferences in order of priority. Runpod attempts to allocate your first choice GPU. If unavailable, it automatically uses the next GPU in your priority list, ensuring your workloads run on the best available resources.
You can enable or disable particular GPU types using the Advanced > Enabled GPU Types section.
After deployment, your endpoint takes time to initialize before it is ready to process requests. You can monitor the deployment status on the endpoint details page, which shows worker status and initialization progress. Once active, your endpoint displays a unique API URL (https://api.runpod.ai/v2/{endpoint_id}/
) that you can use to send requests. For information on how to interact with your endpoint, see Endpoint operations.
You can modify your endpoint’s configuration at any time:
Navigate to the Serverless section in the Runpod console.
Click the three dots in the bottom right corner of the endpoint you want to modify.
Click Edit Endpoint.
Update any configuration parameters as needed:
Click Save Endpoint to apply your changes.
Changes take effect over time as each worker is updated to the new configuration.
To force an immediate configuration update, temporarily set Max Workers to 0, trigger the Release, then restore your desired worker count and update again.
Attach persistent storage to share data across workers:
Network volumes are mounted to the same path on each worker, making them ideal for sharing large models, datasets, or any data that needs to persist across worker instances.
When you no longer need an endpoint, you can remove it from your account:
After confirmation, the endpoint will be removed from your account, and you’ll no longer be charged for its resources.