Skip to main content
NetApp Knowledge Base

What is path style vs virtual style

Views:
52
Visibility:
Public
Votes:
0
Category:
storagegrid
Specialty:
sgrid
Last Updated:
5/15/2025, 6:04:28 PM

Applies to

  • StorageGRID
  • AWS 

Answer

  • Virtual hosted style requests have the bucket as part of the subdomain instead of the URL path (see below for examples)
    • Virtual hosted style example: https://bucket_name.s3.testdomain.com/object_key
    • Path style example: https://s3.testdomain.com/bucket_name/object_key"

Virtual-hosted-style:

  • Uses a virtual-hosted-style URL to access the bucket. 
  • Virtual hosted-style is now the default method for AWS S3.
  • StorageGRID and many applications still support path style, it is best practice to implement virtual hosted-style support.
  • Virtual-hosted-style URLs include the bucket name as part of the domain name.
  • If you choose to use a domain name instead, it is recommended to use the "Virtual Hosted-Style URL" for StorageGRID.
    • Examplehttps://bucket_name.s3.company.com/key-name
    • Example: bucket.domain.domain.domain
  • It can support wildcard DNS lookups as well
    • Example:  *.s3.company.com
  • Information over configuring virtual hosted style: Configure S3 endpoint domain names
  • Only populate the S3 endpoint domain page if virtual style is needed for the environment. 

Path-style:

  • Use a path-style URL to access the bucket.
  • The "Path-Style URL" is the default URL style used by clients when configuring StorageGRID.
  • Path-style URLs include the bucket name at the end.
  • This style is used when you provide an IP address instead of a domain name for the Server name (FQDN) field.
  • Note: The path-style URL option is not recommended and will be deprecated in a future release of StorageGRID.

Additional Information

N/A

 

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.