We also have the ability to delete users, change passwords, add user tags, or authenticate users (I'm not sure how yet). Not sure any of this is necessary, but it's good to know it exists.
"^aliveness-test$" is the conf. A regular expression matching resource names for which the user is granted configure permissions.
Will configure permissions on resources that include ^aliveness-test$
The conf operations create or destroy resources, or alter their behaviour.
Aliveness-Test - Declares a test queue, then publishes and consumes a message. Intended for use by monitoring tools. If everything is working correctly, will return HTTP status 200 with body: {"status":"ok"}
"^amq\.default$" The regular expression ^$, i.e. matching nothing but the empty string, covers all resources and effectively stops the user from performing any operation. Standard AMQP resource names are prefixed with amq.
amq\.default$' gives a user access to the default exchange.
In the write portion of the command.
.* - gives write and read permissions on all resources
ran the same commands for atlas vhost that we did in the previous step for the default vhost...and I think it's working??? 🤷🏻♀️
Issues/Questions:
Timebox to ~1 hour, start time ~8:30amPDT
List/find users in RabbitMQ
Create a user in RabbitMQ
What version are we running?
Does my command work for the version of rabbit we're running?
How do I make positive aspects of my apprentice engineering experience reproducible?
define all aspects of
rabbitmqctl set_permissions -p / datadog "^aliveness-test$" "^amq\.default$" ".*"
set same permissions for atlas vhost that we did for the default vhost
Solutions:
looked up rabbitmqctl here, used the
help
command on-l
and foundlist_users
ssh'd into the rabbitmq node, followed the commands above and received the input for 1.
add_user
command, which is formatted likesudo rabbitmqctl add_user <username> <password>
Version 3.6.10 relevant stack overflow ticket
We also have the ability to delete users, change passwords, add user tags, or authenticate users (I'm not sure how yet). Not sure any of this is necessary, but it's good to know it exists.
Started writing up the Apprentice Engineer Outline
Definitions:
set_permissions
- sets user permissions-p /
- chosen default vhostdatadog
- name of the user"^aliveness-test$"
is the conf.A regular expression matching resource names for which the user is granted configure permissions.
^aliveness-test$
conf
operations create or destroy resources, or alter their behaviour.{"status":"ok"}
"^amq\.default$"
The regular expression^$
, i.e. matching nothing but the empty string, covers all resources and effectively stops the user from performing any operation. Standard AMQP resource names are prefixed withamq
.amq\.default$'
gives a user access to the default exchange.write
portion of the command..*
- gives write and read permissions on all resourcesran the same commands for atlas vhost that we did in the previous step for the default vhost...and I think it's working??? 🤷🏻♀️