Welcome to the DivvyCloud Docs!

DivvyCloud is a Cloud Security Posture Management (CSPM) platform that provides real-time analysis and automated remediation across leading cloud and container technologies.

For questions about documentation reach out to us [email protected]

Take Me to the Docs!    Release Notes

SMTP (Email Notifications)


Simple Mail Transfer Protocol (SMTP) enables DivvyCloud to send email notifications and is compatible with all DivvyCloud resources. This functionality, once configured, enables users to create notifications for emails in a variety of different scenarios.

For example, a user can generate an email that includes a list of all Instance Owners who have provisioned an instance without corporate-required tags. Alternatively an email notification could also be generated to list all Instance Owners who have modified an instance removing corporate-required tags.

This example is just one of hundreds of possibilities that you can explore based on your specific needs and driven by your deployed cloud resources, security and compliance goals, and operational strategy.


Before you get started you will want to ensure you have the following:

  • A functioning DivvyCloud installation with the appropriate admin permissions
  • Details about your SMTP server (hostname, IP, port, etc.)

Note: Email notifications are isolated to an organization. This allows you to tailor email settings to business units, geographies, or however your enterprise is structured.


Integrations and Templating

Divvycloud includes support for Jinja2 Templating and numerous third-party Integrations. Check out the links for details on configuring these capabilities.

Steps to Configure SMTP

Follow the steps below to configure an SMTP server in DivvyCloud.

1. Login to DivvyCloud and navigate to System Administration (under Administration on the left-hand side menu).

2. From the Organizations tab, locate the "Actions" menu for the organization to wish you wish to send emails, and select "Configure Email (SMTP)".

3. To configure SMTP, enter the information relevant to your organization (you may need to scroll through the dialog to access all inputs):

  • Hostname/IP Enter the name or IP address of the host used for SMTP transactions, e.g., smtp.your-company-name.com.
  • Port Enter the port used for SMTP transactions, e.g., 465.
  • When enabled, SSL will be used to encrypt communications. Select if you want DivvyCloud to use Secure Sockets Layer (SSL) to encrypt the connection; this selection is recommended if you are sending sensitive information.
  • Username (Optional) Enter the username for the account that you will use to connect to the SMTP server, e.g., [email protected]
  • Password (Optional) Enter the password of the account that you will use to connect to the SMTP server.
  • Sender Enter the email address you wish to use as the default for emails sent from DivvyCloud, e.g., [email protected]


Amazon SES

To leverage Amazon SES refer to our example here.

4. To confirm/test your settings click "test". You should see a confirmation message indicating success (that the SMTP messages was generated). You should also verify you've received the email.


Verify Receipt of Email

Once configured, the emails will be "sent" even if they have an incorrectly configured destination. We strongly recommend that you verify receipt of email on your end to ensure your configuration is correct; DivvyCloud does not include a mechanism to verify the receipt of email.

5. Click on Submit to save your settings. You should see "Email Configured" has a checkmark next to the organization you modified.

Configuring an Example Bot

Part of the SMTP functionality allows users to take advantage of the DivvyCloud Email action within a Bot configuration. To test, you can create a Bot that, based upon its scope and filtering, will return a positive result. In this example, we will walk you through setting up a Bot to verify that a cloud account has a cloud user.

Check out our BotFactory documentation to learn more about this feature.


Make a Note!

You will receive one email per match, so choose a test without too many matches!

1. To begin, navigate to the BotFactory (under Automation on the left-side navigation menu). Select Create Bot. Give your bot a name, description, and category. Then select Next.

2. Select the Scope of your bot and the Conditions for your bot. Select Next after each.

3. For the bot’s action, you can now send yourself an email for all matches.

  • You can use Jinja2 templating to add resource-specific data in your email.
  • You can also dynamically assign a recipient via one or more tags. (You may need to scroll through the dialog to access all setup fields.)

4. Select when to run your bot.

5. Review and run your bot.


To Run Your Bot Immediately

Bots are created in a paused state. This is done to allow you to review your bot first--a DivvyCloud best practice--before running your bot.

You can review your bot using the Bot Overview window (see Overview of Your Bot). When you are ready to run your bot, go to the Bot Listing tab, and select 'Resume' from the action hamburger next to the name of your bot. Then return to the action hamburger and select 'Ondemand Scan'.

6. Finally, check your email to see the results.

Pack-Level Notifications


Pack-level notifications enable customers to send emails based on packs of Insights. This includes both the out-of-the-box Compliance Packs that are included with DivvyCloud, and any Custom Packs a customer may create for their specific environment.

In our previous Bot example we configured a single email for a single Insight. While this single email per Insight may be appropriate for your use, you may also seek a different level of granularity. Pack-level notifications can configure a single email that can be generated for an entire group of Insights.

The pack-level notification capability includes cadence settings to send an email weekly, daily, or hourly. It allows for the delivery of information around an entire category of Insights, enabling organizations to cut down on the "noise" of notifications generated from several bots, since each Bot can only send an email for a single Insight.


Before setting up a pack-level notification email, you will need:

  • A running instance of DivvyCloud with Organization or Domain Admin permissions
  • A working SMTP configuration


Delivery Cadence

It's important to note that selecting a specific hour or minute will not guarantee delivery of an email notification at the specified time.

When selecting a delivery time you must account for the time required to process the request and create the data for the email notification.

For example, if the cadence is shorter than the time to takes the system to process the request and generate the reports, a user may receive two copies of the email notification.

To avoid issues with your delivery we recommend a cadence that is atleast 10 minutes or longer.

Pack-level Email Notification Setup

To configure an email notification, you can set up the notification (subscription) based on an Insight Compliance Pack or a Custom Pack. Complete the following steps.

1. Navigate to the Insight section of your DivvyCloud installation and locate the Insight Pack you want to use as the basis of your notification.

2. Click the envelope icon on the bottom of target Insight pack. This will open the "Manage Insight Pack Subscriptions" page and allow you to create a new subscription.

3. Complete the details for your email subscription including the following details:

  • a name
  • the target email address
  • a subtitle (optional)
  • your desired frequency

Create a New Subscription

4. Click "Subscribe" when you have completed the fields as desired.

5. To test your newly created subscription, select the ellipsis menu to the right of the subscription name and select "Send Now".

  • If you've supplied an invalid email address, or you do not have an SMTP server configured, the system will respond with an error.

Note - This is where you will also access any existing subscriptions or notifications if you need to edit or update them.

Subscription Options

6. Success! Your intended recipients should receive an email that looks something like the image below!

  • Download the excel attachment to view your report findings for the notification (e.g. HIPPA Subscription).

Sample Subscription Report

Updated 7 months ago

Other Helpful Pages

Amazon SES

SMTP (Email Notifications)

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.