---
id: deploy-multiple-accounts-regions
title: Deploy to Multiple Accounts and Regions
sidebar_label: Deploy to Multiple Accounts and Regions
description: Learn how to deploy the AWS Observability Solution for a single AWS region and account.
slug: /help/docs/observability/aws/deploy-use-aws-observability/deploy-with-aws-cloudformation/deploy-multiple-accounts-regions/
canonical: https://www.sumologic.com/help/docs/observability/aws/deploy-use-aws-observability/deploy-with-aws-cloudformation/deploy-multiple-accounts-regions/
---
import useBaseUrl from '@docusaurus/useBaseUrl';
This topic has instructions for deploying AWS Observability Solution to multiple AWS accounts and regions using [StackSets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-concepts.html).
Given that we use an account alias, we recommend you use StackSets to automatically deploy the AWS CloudFormation template across all regions in one AWS account at a time. New AWS accounts can be added to an existing StackSet.
## Before you start
* If this is the first time you've deployed our AWS Observability solution, read the [Before You Deploy](/docs/observability/aws/deploy-use-aws-observability/before-you-deploy/) topic for more information.
* Complete the prerequisites for StackSets as described in the [AWS documentation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs.html).
## Step 1: Open the CloudFormation template
1. Sign in to the AWS Management console.
1. Choose an option to invoke AWS CloudFormation Template:
* Click [this URL](https://console.aws.amazon.com/cloudformation/home#/stacks/quickcreate?templateURL=https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.15.0/sumologic_observability.master.template.yaml) to invoke the latest Sumo Logic AWS CloudFormation template.
* Download the AWS Observability Solution template (S3 link for CloudFormation template): https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.15.0/sumologic_observability.master.template.yaml to invoke the latest Sumo Logic AWS CloudFormation template.
:::note
If you would like to download or inspect this or other versions of this template, see the [Changelog](/docs/observability/aws/deploy-use-aws-observability/changelog/).
:::
1. Select the AWS Region where you want to deploy the AWS CloudFormation template.
:::danger
This step is critical. If you do not select the correct region, you will deploy the solution in the wrong region.
:::
1. Proceed to [Step 2](#step-2-sumo-logic-access-configuration) below.
## Step 2: Sumo Logic access configuration
The below table displays the response to each prompt during Step 2.
| Prompt | Guideline |
|:--|:--|
| Sumo Logic Deployment Name | Enter au, ca, ch, de, esc, eu, jp, us2, fed, kr, or us1. See [Sumo Logic endpoints by deployment and firewall security](/docs/api/about-apis/getting-started/#sumo-logic-endpoints-by-deployment-and-firewall-security) for more information on Sumo Logic deployments. |
| Sumo Logic Access ID | Sumo Logic Access ID. See [Create an access key](/docs/manage/security/access-keys/#create-an-access-key) for more information. |
| Sumo Logic Access Key | Sumo Logic Access Key. This key is used for Sumo Logic API calls. |
| Sumo Logic Organization ID | You can find your org on the [Preferences](/docs/get-started/account-settings-preferences/#accessing-preferences) page in the Sumo Logic UI. Your org ID will be used to configure the IAM Role for Sumo Logic AWS Sources. |
| Delete Sumo Logic Resources when stack is deleted | To delete collectors, sources and apps in Sumo Logic when the stack is deleted, set this parameter to "True". If this is set to "False", Sumo Logic resources are not deleted when the AWS CloudFormation stack is deleted. Deletion of updated resources will be skipped. |
## Step 3: AWS account alias
The below table displays the response to each prompt during Step 3.
| Prompt | Guideline |
|:--|:--|
| Alias for your AWS account | Enter an account alias for the AWS environment from which you are collecting data. This alias 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). This name will appear in the metrics and logs and can be queried via the “account field”.
**Important:** Account Aliases should be alphanumeric and cannot include special characters such as “-, $, _” etc.
Leave this blank If you're using CloudFormation StackSets to deploy the solution in multiple AWS accounts. |
| S3 URL of a CSV file that maps AWS Account IDs to an Account Alias | This parameter is applicable only If you're using CloudFormation StackSets to deploy the solution in multiple AWS accounts.
The S3 URL of the CSV file should have public read access when deploying or updating the solution.
Enter the S3 URL of a CSV file which contains the mapping of AWS Account IDs to an Account Alias in the following format:
**accountid,alias**
For example:
**1234567,dev**
**9876543,prod** |
## Step 4: Install Apps
Perform the following steps to install apps.
1. Complete the prerequisites for StackSets as described in the [AWS documentation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs.html).
1. 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**.
})
1. Select the Sumo Logic Metrics Sources to create as **None**.
})
1. Enable ALB Access logging as **None** and Create Sumo Logic ALB Logs Source as **No**.
})
1. Create Sumo Logic CloudTrail Logs Source as **No**.
})
1. Select Sumo Logic CloudWatch Logs Source as **None**.
})
1. Enable ELB Classic Access logging as **None** and Create Sumo Logic ELB Classic Logs Source as **No**.
})
1. Location where you want the App to be Installed as **Personal Folder**. And for **Do you want to share App with whole organization**, set as **True**.
})
## Step 5: 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 are examples of the CSV file format to use (`accountid,alias`):
* `234234234324,dev`
* `214324324324,prod`
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.
In case you do not provide a CSV file or if we detect that it does not have the right format, the AWS `account-id` will be used as the alias and this value will be used for the “account” field in Sumo Logic.
### Use the AWS CloudFormation template with StackSets
1. Go to [StackSets](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacksets) in your AWS account.
1. Click **Create StackSet**.
})
1. Paste the URL `https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.15.0/sumologic_observability.master.template.yaml` in the Amazon S3 URL option and click **Next**. If you'd like to download or inspect this or other versions of this template, see the [Changelog](/docs/observability/aws/deploy-use-aws-observability/changelog/).
})
1. Provide a StackSet Name and supply the values for each of the prompts listed as per instructions in the [Deploy and Use AWS Observability](/docs/observability/aws/deploy-use-aws-observability) section with the following exception:
1. Leave the field “Alias for AWS Account Identification” blank.
})
1. 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”.
})
1. Answer **No** in Section 3 of the template "Install AWS Observability Apps".
})
1. Click **Next**.
1. Add Tags, select the Administrator role defined in the prerequisites above, and click **Next**.
})
1. 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.
})
1. Increasing the **Maximum concurrent actions** to be more than 1 is not recommended and can cause your StackSet deployment to fail. Stack sets should be deployed one at a time, sequentially. Click **Next**.
})
1. Review the details, select the capabilities and click **Submit**.
})
1. Once you hit submit, the AWS CloudFormation template will execute in the provided account and regions sequentially.
## Add more accounts to the same StackSet
1. Select **Add new stacks to StackSet**.
})
1. In ‘**Set deployment options**’, Enter the account number and regions you want to deploy the stack.
})
1. Verify the S3 mapping file contains the mapping for the new Account ID.
1. Review the details, select the capabilities, and click **Submit**.