CloudWiki
Resource

Queue Storage

Microsoft Azure
Storage
Azure Queue Storage is a cloud-based message queuing service that allows users to store and retrieve messages between components or services. It is designed for building scalable and distributed applications that require asynchronous and decoupled communication between components. With Azure Queue Storage, messages can be sent and received in a reliable, asynchronous, and fault-tolerant manner. Messages are stored in a queue and can be accessed by multiple consumers or workers, which can process them in parallel. It supports various messaging patterns, such as point-to-point and publish-subscribe, and provides features such as message expiration, visibility timeout, and message ordering.
Terraform Name
terraform
azurerm_storage_queue
Queue Storage
attributes:

The following arguments are supported:

  • name - (Required) The name of the Queue which should be created within the Storage Account. Must be unique within the storage account the queue is located. Changing this forces a new resource to be created.
  • storage_account_name - (Required) Specifies the Storage Account in which the Storage Queue should exist. Changing this forces a new resource to be created.
  • metadata - (Optional) A mapping of MetaData which should be assigned to this Storage Queue.

Associating resources with a
Queue Storage
Resources do not "belong" to a
Queue Storage
Rather, one or more Security Groups are associated to a resource.
Create
Queue Storage
via Terraform:
The following HCL manages a Queue within an Azure Storage Account
Syntax:

resource "azurerm_resource_group" "example" {
 name     = "example-resources"
 location = "West Europe"
}

resource "azurerm_storage_account" "example" {
 name                     = "examplestorageacc"
 resource_group_name      = azurerm_resource_group.example.name
 location                 = azurerm_resource_group.example.location
 account_tier             = "Standard"
 account_replication_type = "LRS"
}

resource "azurerm_storage_queue" "example" {
 name                 = "mysamplequeue"
 storage_account_name = azurerm_storage_account.example.name
}

Create
Queue Storage
via CLI:
Parameters:

az storage queue create --name
                       [--account-key]
                       [--account-name]
                       [--auth-mode {key, login}]
                       [--connection-string]
                       [--fail-on-exist]
                       [--metadata]
                       [--queue-endpoint]
                       [--sas-token]
                       [--timeout]

Example:

az storage queue create -n myqueue --metadata key1=value1 key2=value2 --account-name mystorageaccount

aws cost
Costs
Direct Cost
Indirect Cost
No items found.
Best Practices for
Queue Storage

Categorized by Availability, Security & Compliance and Cost

Low
Access allowed from VPN
No items found.
Low
Auto Scaling Group not in use
No items found.
Medium
Connections towards DynamoDB should be via VPC endpoints
No items found.
Medium
Container in CrashLoopBackOff state
No items found.
Low
EC2 with GPU capabilities
No items found.
Medium
EC2 with high privileged policies
No items found.
Medium
ECS cluster delete alarm
No items found.
Critical
ECS task with Admin access (*:*)
Medium
ECS task with high privileged policies
No items found.
Critical
EKS cluster delete alarm
No items found.
Medium
ElastiCache cluster delete alarm
No items found.
Medium
Ensure Container liveness probe is configured
No items found.
Medium
Ensure ECS task definition has memory limit
No items found.
Critical
Ensure EMR cluster master nodes are not publicly accessible
No items found.
More from
Microsoft Azure