Creating and Managing AWS SQS Queues

The create-and-manage-sqs-queue Jenkins job creates, updates, and deletes one single queue and an associated dead-letter-queue in the AWS Simple Queue Service (SQS).

note

We recommend creating SQS queues in the cluster that will be using them. For example, create pre-production queues from the pre-production cluster. This is so the resources are all grouped by source cluster.

Parameters for the create-and-manage-sqs-queue Jenkins Job

deleteQueue

When checked, this destroys the SQS queue instead of creating it.

plan_mode

When selected, this runs Terraform in plan mode and prompts you to approve changes before you continue. This works in both the setup and destroy modes.

queueName

The name of the SQS queue to be created. We recommend that the name indicates which Elastic Path environment the queue is for as well as the purpose of the queue. For example, the name staging-inventory would be a queue that handles inventory messages for the Self Managed Commerce staging environment. Ensure that the name adheres to the SQS naming conventions.

snsTopicSubscription

Optional. The Amazon Resource Name (ARN) of the Amazon Simple Notification Service (SNS) topic that you want the SQS queue to subscribe to. The SNS topic must be created and exist in advance.

sqsPolicy

Optional. You may specify an SQS policy for the SQS queue by providing a proper SQS policy in JSON format. The policy specified must be syntactically correct and valid, and in the format required by AWS SQS. For more information, see the AWS SQS documentation.

cloudOpsForKubernetesRepoURL

The Git repository URL of the cloudops-for-kubernetes code.

cloudOpsForKubernetesBranch

The branch of cloudops-for-kubernetes to use.