aws_mq_configurations Resource

Use the aws_mq_configurations InSpec audit resource to test the properties of multiple AWS MQ configuration.

Install

This resource is available in the Chef InSpec AWS resource pack.

For information on configuring your AWS environment for Chef InSpec and creating an InSpec profile that uses the InSpec AWS resource pack, see the Chef InSpec documentation on the AWS cloud platform.

Ensure that AWS MQ configuration exists.

describe aws_mq_configurations do
  it { should exist }
end

This resource does not require any parameters.

arns: The ARN of the configuration.; Field: arn
authentication_strategies: The authentication strategy associated with the configuration. The default is SIMPLE.; Field: authentication_strategy
Created: The date and time of the configuration revision.; Field: Created
description: The description of the configuration.; Field: description
engine_types: The type of broker engine. Currently, Amazon MQ supports ACTIVEMQ and RABBITMQ.; Field: engine_type
engine_versions: The broker engine’s version. For a list of supported engine versions.; Field: engine_version
ids: The unique ID that Amazon MQ generates for the configuration.; Field: id
names: The name of the configuration.; Field: name
tags: The list of all tags associated with this configuration.; Field: tags

Ensure a configuration ID is available.

describe aws_mq_configurations do
  its('ids') { should include 'configuration_id' }
end

Ensure a configuration name is available.

describe aws_mq_configurations do
    its('names') { should include 'configuration_name' }
end

For a full list of available matchers, see our Universal Matchers page.

The controls will pass if the list method returns at least one result.

Use should to test that the entity exists.

describe aws_mq_configurations do
  it { should exist }
end

Use should_not to test the entity does not exist.

describe aws_mq_configurations do
  it { should_not exist }
end

Use should to check if the mq configuration is available.

describe aws_mq_configurations do
  it { should be_available }
end

Your Principal will need the MQ:Client:ListConfigurationsResponsegit action with Effect set to Allow.