Skip to main content
Sumo Logic

Deploy to Multiple Accounts and Regions

Learn how to deploy the AWS Observability Solution for a single AWS region and account.

This topic has instructions for deploying AWS Observability Solution to multiple AWS accounts and regions
using Stack Sets.

Before you start

You need to install apps and determine account aliases before deploying.

Step 1: Install Apps

  1. Complete the prerequisites for StackSets as described in the AWS documentation.
  2. Install the apps by running the AWS CloudFormation Stack once in any given account and region. Use the configuration below to set up only app dashboards.
    1. Install AWS Observability Apps as Yes.
      Multiaccount 1.png
    2. Select the Sumo Logic Metrics Sources to create as None.
      Multiaccount 2.png
    3. Enable ALB Access logging as None and Create Sumo Logic ALB Logs Source as No.
      Multiaccount 3.png
    4. Create Sumo Logic CloudTrail Logs Source as ‘No’.
      Multiaccount 4.png
    5. Create Sumo Logic CloudWatch Logs Source as No.
      Multiaccount 5.png

Step 2: Determine Account Aliases

If you are going to deploy the solution in multiple AWS accounts, we highly recommend that you prepare a CSV file that maps your AWS Account-ids to account aliases. These aliases should be something that makes it easy for you to identify what this AWS account is being used for (for example dev, prod, billing, and marketplace). These names will appear in the Sumo Logic Explorer View, metrics, and logs and can be queried using the “account field”.

The following is an example of the CSV file format to use:




Please upload this file to an Amazon S3 bucket and make it accessible to the account from where you are going to run the CloudFormation template. 

Use the AWS CloudFormation template with StackSets

  1. Go to Stack Sets in your AWS account.
  2. Click Create StackSet.
    ClodFormation_Stackset 1.png
  3. Paste the URL - in the Amazon S3 URL option and click Next.
    ClodFormation_Stackset 2.png
  4. Provide a StackSet Name and supply the values for each of the prompts listed as per instructions in the Deploy the AWS Observability Solution section with the following exception:
    • Leave the field “Alias for AWS Account Identification” blank.

    • Provide the S3 Object URL of a CSV file that maps AWS Account IDs to an Account Alias in Section 2 of the template “AWS Account Alias”.
    • Answer No in Section 3 of the template "Install AWS Observability Apps". 
      ClodFormation_Stackset 3.png
    • Click Next.
  5. Add Tags, select the Administrator role defined in the prerequisites above, and click Next.ClodFormation_Stackset 4.png
  6. Provide a single AWS account number only and select a list of regions in the account where you would like to deploy the AWS CloudFormation template as shown in the screenshot below:
    • You will need to select all the regions in the current account where you would like to deploy the template.
      ClodFormation_Stackset 5.png
  7. Increasing the Maximum concurrent actions to be more than 1 is not recommended and can cause your stack set deployment to fail. Stack sets should be deployed one at a time, sequentially. Click Next.
    ClodFormation_Stackset 6.png
  8. Review the details, select the capabilities and click Submit.
    ClodFormation_Stackset 7.png
  9. Once you hit submit, the AWS CloudFormation template will execute in the provided account and regions sequentially.

To add more accounts to the same Stack Set

  1. Select ‘Add new stacks to StackSet’.ClodFormation_Stackset 8.png
  2. In ‘Set deployment options’, Enter the account number and regions you want to deploy the stack.
    ClodFormation_Stackset 9.png
  3. Verify the S3 mapping file contains the mapping for the new Account ID.
  4. Review the details, select the capabilities, and click Submit.