- Glasswall CDR
- Embedded Engine
- About Embedded Engine
- Overview
- Getting Started
- API
- Engine Release Notes
- Release 16.6.0
- Release 16.5.1
- Release 16.5.0
- Release 16.4.0
- Release 16.3.0
- Release 16.2.0
- Release 16.1.0
- Release 16.0.1
- Release 16
- Release 15
- Release 14
- Release 13.1 (beta)
- Release 13
- Release 12
- Release 11
- Release 10
- Release 9
- Release 8
- Release 7
- Release 6
- Release 5.4
- Release 5.3
- Release 5.2
- Release 5.1
- Release 5
- Release 4
- Legacy
- Supporting Tools
- Appendix
- Terms of Service
- Halo
- About Halo
- Glasswall Halo FAQs
- Overview
- Getting Started
- Evaluation via AWS Marketplace
- Evaluation via minikube
- Deployment
- Deployment Overview
- Shared Responsibility Model
- Glasswall Artifact Registry
- Configuration Changes
- Authentication
- AKS
- AKS Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to AKS
- Step 2 - Create Glasswall Halo namespace
- Step 3 - Add secrets in Key Vault
- Step 4 - Enable your AKS cluster to access Key Vault
- Step 5 - Enable access to Glasswall's Artifact Registry
- Step 6 - Pull Helm charts
- Step 7 - Install and configure prerequisite components
- Step 8 - Install CDR components
- Amazon EC2
- EKS
- EKS Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to EKS
- Step 2 - Create Glasswall Halo namespace
- Step 3 - Create secrets in Secrets Manager
- Step 4 - Enable access to Glasswall's Artifact Registry
- Step 5 - Pull Helm charts
- Step 6 - Install and configure prerequisite components
- Step 7 - Install CDR components
- GKE
- GKE Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to GKE
- Step 2 - Create Glasswall Halo namespace
- Step 3 - Enable your GKE cluster to access Secrets
- Step 4 - Manage Secrets
- Step 5 - Enable access to Glasswall's Artifact Registry
- Step 6 - Pull Helm charts
- Step 7 - Install and configure prerequisite components
- Step 8 - Install CDR components
- OKE
- Single Node VM
- License Management
- Functionality
- Using Halo
- Halo Release Notes
- v2.7.2
- v2.7.1
- v2.7.0
- v2.6.2
- v2.6.1
- v2.6.0
- v2.5.4
- v2.5.3
- v2.5.2
- v2.5.1
- v2.5.0
- v2.4.15
- v2.4.13
- v2.4.12
- v2.4.11
- v2.4.10
- v2.4.9
- v2.4.8
- v2.4.7
- v2.4.6
- v2.4.5
- v2.4.4
- v2.4.3
- v2.4.2
- v2.4.1
- v2.4.0
- v2.3.0
- v2.2.1
- v2.2.0
- V2.1.4
- v2.1.3
- v2.1.2
- v2.1.1
- v2.1.0
- v2.0.7
- V2.0.6
- V2.0.5
- v2.0.4
- v2.0.3
- v2.0.2
- Single Node VM
- v2.7.2 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.7.0 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.6.2 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.6.1 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.6.0 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.4 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.3 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.2 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.1 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.4.13 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.12 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.11 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.10 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.9 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.8 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.7 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.5 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.5 RHEL8.8 RKE1.25.9+rke2r1
- v2.4.4 RHEL8.8 RKE1.25.9+rke2r1
- v2.4.4 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.3.0 RHEL8.8 RKE1.25.9+rke2r1
- v2.2.1 RHEL8.8 RKE1.25.9+rke2r1
- Appendix
- Terms of Service
- Constellations
- About Constellations
- Constellations FAQs
- Overview
- Getting Started
- Architecture
- Deployment
- Glasswall Artifact Registry
- AKS
- AKS Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to AKS
- Step 2 - Create namespaces
- Step 3 - Add secrets in Key Vault
- Step 4 - Enable your AKS cluster to access Key Vault
- Step 5 - Enable access to Glasswall's Artifact Registry
- Step 6 - Pull Helm charts
- Step 7 - Install and configure prerequisite components
- Step 8 - Install Glasswall Halo services
- Step 9 - Install Constellations components
- Constellations Release Notes
- Terms of Service
- Performance
- Meteor
- About Meteor
- Meteor Versions
- Getting Started
- Using Meteor
- Meteor Connect
- About Meteor Connect
- Minimum Requirements
- Install Glasswall Meteor Connect
- User Interface
- Preferences
- File Versions
- Support
- Storage Protocols
- Connect Mode
- Meteor Connect Release Notes
- Cloud Folders
- Meteor Release Notes
- Appendix
- Terms of Service
- Glasswall REST APIs
- Glasswall Research
- PDF
Azure
- PDF
Windows Azure Blob Storage
Azure Blob Storage is a massively scalable object storage for unstructured data.
Connecting to Windows Azure Blob Storage
Hostname
Edit the hostname to connect to your account in the format <account>.blob.core.windows.net
.
Warning - Azure Files Storage is not supported.
Credentials
Account and Key
You must obtain the login credentials (Account Name and Primary Access Key) from portal.azure.com. You can find the keys in the section Access keys. In the login prompt of Cyberduck upon connecting to Windows Azure you enter the Storage Account Name for the username and Primary Access Key for the password.
Shared Access Signatures (SAS)
You can use a SAS when you want to provide access to resources in your storage account to any client not possessing your storage account's access keys.
- Download the Azure (Shared Access Signature Token) profile or install it from Preferences… → Profiles.
Containers
To create a new container in your account, browse to the root and choose File → New Folder... (Windows Ctrl+Shift+N
).
Blob Type
Uploads are stored as append blob type by default. You can use the hidden configuration option azure.upload.blobtype
which allows the values BLOCK_BLOB
, PAGE_BLOB
and APPEND_BLOB
.
Metadata
You can edit standard custom metadata. Choose File → Info → Metadata to edit custom headers.
Default Metadata
Currently only possible using a hidden configuration option you can define default headers to be added for uploads. Multiple headers must be separated using a whitespace delimiter. Key and value of a header are separated with =
. For example, if you want to add an HTTP header for Cache-Control
and one named Creator
you would set
defaults write ch.sudo.cyberduck azure.metadata.default "Cache-Control=public,max-age=86400 Creator=Cyberduck"
Shared Access Signature URLs
A private object stored in Azure Storage can be made publicly available for a limited time using a signed URL. The signed URL can be used by anyone to download the object, yet it includes a date and time after which the URL will no longer work. Copy the signed URL from Edit → Copy URL→ Signed URL.
Note - Currently only signed URLs with a validity of 24 hours are available.
Limitations
- Container and blob naming conventions.
- CDN configuration is currently only possible using the web interface.
Problems
One of the Request Inputs is out of Range
Please follow the Naming and Referencing Containers, Blobs, and Metadata guidelines.