How to Add Storage in the NetActuate Customer Portal

Overview

NetActuate Storage lets you provision storage resources alongside your infrastructure so you can match the right storage model to each workload and location. From Infrastructure → Storage, you can deploy object storage for S3-style workflows or block storage for disk/volume-based workloads.

Storage options and common use cases

• S3 Bucket (Object Storage)
  
  • Use for S3-compatible storage such as backups, artifacts, logs, media, datasets, static assets, and application object storage.
  • Supports Public or Private access behavior for the HTTPS endpoint (see Public vs Private below).
• S3 Object Store
  
  • Use when you need to deploy or manage the underlying object storage service construct (the “object store” that buckets live within), rather than only creating an individual bucket.
  • Typically used for more advanced object storage setups or when an environment is organized around object-store resources.
• Block Device
  
  • Use when you need a single block volume for a VM or workload—commonly for boot/data disks, databases, or any application that expects a filesystem-backed disk.
• Block Device Pool
  
  • Use when you need pooled block capacity that can be used dynamically across workloads (commonly for Kubernetes or multi-volume use cases).

Add a Storage Resource

1) Navigate to Storage

1. In the top navigation bar, click Infrastructure.
2. In the left sidebar, click Storage.
   
   • You’ll see a list/grid of your existing storage resources (each card shows the label, type, usage/capacity, and location).

2) Start the deploy flow

3. Click + Add (top-right).

This opens the Deploy Storage → Storage Details panel.

3) Fill out Storage Details

Label

4. Enter a Label.
   
   • This is the friendly name that appears in your Storage list.

Location

5. Choose a Region.
6. Choose a POP / City.
   
   • Storage is provisioned in the location you select, so choose where your workloads/users need it.

Storage Type

7. Open the Storage Type dropdown and select what you want to deploy:

• S3 Bucket
• S3 Object Store
• Block Device
• Block Device Pool

Tip: If your goal is “I need S3-style object storage,” choose S3 Bucket unless you specifically know you need S3 Object Store for your environment.

4) Capacity and billing (Autoscaling vs Reserved Capacity)

After selecting a storage type (for example, S3 Bucket), the form reveals sizing/billing controls.

Autoscaling

• Autoscaling ON
  
  • Your storage capacity can grow with your usage.
  • The resource has no fixed quota/limit set via the capacity slider.
  • Billing is based on usage rather than a reserved capacity.
• Autoscaling OFF
  
  • You reserve a specific capacity using the slider.
  • This sets a defined quota/limit for the resource.

5) Public vs Private (S3 buckets)

If you’re creating an S3 Bucket, you’ll also see a toggle for bucket access:

• Public bucket
  
  • The bucket is accessible via the HTTPS endpoint without requiring credentials.
• Private bucket
  
  • The bucket’s HTTPS endpoint requires authentication credentials/keys.

Note: This setting is about access behavior for the HTTPS endpoint (public vs requires auth), not about whether the bucket exists or how you use S3 tooling.

6) Deploy

8. Review your selections (Label, Location, Storage Type, Autoscaling, Public/Private).
9. Click Deploy.

After deployment, you’ll return to the Storage list and see the new resource as a card with its type and location.

Connect to the Customer Portal

Learn more about NetActuate Storage

Get Storage Documentation

Schedule a Call