Managed Services configuration in AWS

Storage Security comes bundled with 3rd party services that can be replaced with AWS managed equivalents. Below are the steps on how to configure each of the AWS services in MDSS.

MongoDB -> Amazon DocumentDB

TLS can be disabled in the cluster parameter group, otherwise the DocumentDB tls certificate will need to be loaded in MDSS using the /etc/mdss/ca_certificates directory

After creating a DocumentDB instance in AWS, its connection string can be added in the MDSS configuration file /etc/mdss/customer.env as it appears in the “Connect“ section:

MONGO_URL=mongodb://<username>:<insertYourPassword>@<address>:27017/?replicaSet=rs0&readPreference=secondaryPreferred&retryWrites=false

Redis -> Amazon ElastiCache

After creating a new Redis cache in Amazon ElastiCache, its Configuration endpoint can be added in the MDSS configuration file /etc/mdss/customer.env as it appears in the “Cluster details“ section:

CACHE_SERVICE_URI=<redis_hostname>.cache.amazonaws.com:6379 CACHE_SERVICE_URL=<redis_hostname>.cache.amazonaws.com CACHE_SERVICE_PORT=6379

CACHE_SERVICE_URL and CACHE_SERVICE_PORT also need to be configured for MDSS to check connectivity to the service before starting up.

RabbitMQ -> Amazon MQ

After creating a new Amazon MQ instance, its Endpoint can be added in the MDSS configuration file /etc/mdss/customer.env as it appears in the “Connections“ section:

RABBITMQ_URI=amqps://<username>:<password>@<amazon_mq_hostname>.amazonaws.com:5671 RABBITMQ_HOST=<amazon_mq_hostname>.amazonaws.com:5671 RABBITMQ_PORT=5671

RABBITMQ_HOST and RABBITMQ_PORT also need to be configured for MDSS to check connectivity to the service before starting up.

Last updated on

Was this page helpful?