AWS Data Collection Using a CloudFormation Template (CFT)

AWS Data Collection Using a CloudFormation Template

​

Overview

Densify’s CloudFormation template creates a stack comprised of the AWS resources required by Densify to collect the Resource Utilization Metrics (via CloudWatch) that are then used for cloud optimization analysis. If your accounts are setup using an AWS organization/management account structure, in which many accounts are linked to one management account, you can use the CloudFormation template to create, update and delete StackSets across multiple accounts and also create the cloud connection within Densify for each of the linked accounts. If you are not using an organizational account structure you can provide a list of accounts to be updated when you are configuring the stack.

Figure: Onboarding AWS Accounts Using CloudFormation

This template creates the IAM role and access policy and assigns the policy to the role using native CloudFormation capabilities. The template then uses a Lambda function to make an API call to Densify to create the cloud connections required to collect resource utilization data. If you need to update the IAM role or policy after they have been created, see Editing the Stackset . This may be necessary if the IAM access policy needs additional permissions.

​

Supported Regions

You can run Densify’s CloudFormation template in any of the following regions;

ap-northeast-1 ap-northeast-2 ap-south-1 ap-southeast-1 ap-southeast-2

eu-central-1 eu-north-1 eu-west-1 eu-west-2 eu-west-3

ca-central-1 us-east-1 us-east-2 us-west-1 us-west-2 sa-east-1

Densify CloudFormation template can must be run in a single region even if the target accounts span multiple regions. The template creates an IAM role and permission policy which are both global and are not region-specific. Please contact [email protected] if you need to run the template in regions, not listed above.

​

Additional Considerations Regarding Regions

When you create the StackSet, you need to specify a region from where the stack is deployed to each account and from where the Lambda function runs. Ensure you specify a single region as the IAM role and permission policy are globally accessible and as such will work from any region. If you try to re-run the template in a different region it will fail as the IAM role and the permission policy already exist. The Lambda function is region-specific but it only runs once to create the cloud connections within Densify. The StackSet and the CloudWatch logs that result from running the template are also region-specific and are defined within a specific region. You need to log into the specified region to manage your Stack and view its related log files. These log files will be required by the Densify support team, if troubleshooting any data collection issues.

​

Using the CloudFormation Template

If your AWS accounts are setup using an organizational structure, in which many accounts are linked to one master account, you can use the CloudFormation template to create, update and delete stacks across multiple accounts and also create the cloud connection within Densify for each of the linked accounts. If you are using the organizational account structure, you need an IAM user that has sufficient execute permissions to create the required roles and IAM policies in each linked account. If you are not using an organizational account, you can provide a list of accounts in which the CloudFormation template will run and create the required prerequisites for data collection. In addition to creating connections from your linked accounts, you also need to create a connection for your payer accounts. The payer account connection provides the name of each linked accounts.

​

Prerequisites

Obtain the following required inputs for the template before starting:

• External ID for IAM Role—This value is similar to a password and should be unique and difficult to guess. Densify recommends using a password generator to create a random, alphanumeric string (e.g. ae73mcf4ldjpet96) for the external ID.
• Both the URL and user credentials for your Densify instance—Contact your Densify Account Manager for details if you do not have this information.
• IAM User with Execute Permissions—If you are using an AWS Organization/management account structure with many linked accounts, you need an IAM user that has sufficient execute permissions to create the required roles and IAM policies in each linked account.

​

Considerations when Working with Large Environments

In large environments, Densify highly recommends batching your accounts into smaller groups for improved performance when using the CloudFormation templates. i.e. no more than 10 accounts at a time. You can use a resource tag, such as application or business unit to separate the CloudFormation stack so that data is collected in manageable batches.

​

Configuring and Running the Template

​

Step 1: Choose a Template

1. Log into the AWS Management Console and navigate to CloudFormation and select StackSets. You may need to expand the options in the upper left corner of the page:

Figure: Accessing Stack Options

2. At the top of the StackSets page, select a supported region. See the list of Supported Regions.
3. Click Create StackSet to begin.

Figure: Create StackSet Options

4. In the Permissions section at the top of the page select the applicable option.

Your selection, here depends on the nature of your organizational structure and your specific requirements for managing permissions across accounts.

• Service-managed permissions—Use this option when you want the AWS Organization to automatically manage permissions. This is useful if you have a large number of accounts under an organization and you want to simplify the management of permissions across these accounts.
• Self-service permissions—Use this option when you need more granular control over permissions or when you are working in an environment where accounts are not part of the same AWS organizational structure.

5. If you selected “Self-service permissions”, then specify an IAM role that has execute privileges in your target linked accounts.

Figure: Specify CloudFormation Permissions

6. In the next section, Prerequisite - Prepare template, select Template is ready
7. In the next section, Specify template copy and then paste the following URL into the Amazon S3 URL field: https://densify-cf-template.s3.us-east-2.amazonaws.com/Densify_CloudFormation.yml
8. Click Next to proceed with creating the stack.

Figure: Specify CloudFormation Template

​

Step 2: Specify StackSet Details

1. Enter the following Stackset details:

• Stack name—Densify-Data-Collection, as an example.
• Stack description—Optionally enter a description for this StackSet

Figure: Specify CloudFormation Template

2. Enter the following Densify instance details:

• Densify Instance URL—This is your Densify SaaS instance.
• Densify User ID—This is your Densify user name.
• Densify Password—This is the password for the listed user name.

Figure: Specify Densify Instance Details

3. The values for IAM Role Name and the Permission Policy Name fields are provided. You do not need to enter any values here.
4. Click Next to proceed with creating the stack.

​

Step 3: Configure StackSet Options

1. In the Configure StackSet options page, accept the default values and then click Next.

• Tags—No tags need to be specified for the StackSet.
• Inactive—Leave this value to simplify StackSet execution.

​

Step 4: Set Deployment Options

Set the following deployment options

1. In the first section, Add stacks to stack set select Deploy new stacks.

Figure: Specify Account Details

2. Under Accounts > Deployment locations , define the accounts to which you want to deploy the StackSet:

• Deploy Stacks in accounts—Enter the 12-digit account numbers in the field.

Alternatively, you can specify a .CSV file with the account information. The .CSV files must contain the 12-digit account numbers separated by commas.

• Deploy stacks in organizational units—Specify the organization units to use. The StackSet will be deployed to all account in the specified organizational units.

3. In the next section, select one region from which the StackSet will be managed. This is typically the same region from which the StackSet is deployed. See the list of Supported Regions.
4. Set the following Deployment Options:

• Maximum Concurrent Accounts—Choose Number from the dropdown list and enter a value of 10.

Do not set this value greater than 10. Densify highly recommends batching your accounts into smaller groups for improved performance. Setting a higher number is faster for AWS operations, but creating the cloud environments and initiating data collection within Densify is negatively impacted if more than 10 accounts are run concurrently.

• Failure Tolerance (Optional)—Set this to an absolute number or a percentage of the total number of accounts being updated. If this value is exceeded, all resource changes will be rolled back.

• Region Concurrency—Select the desired option. As long as Maximum Concurrent Accounts is specified, parallel is preferred.
• Concurrency Mode—Leave the default value, of “Strict failure tolerance”.

Figure: Deployment Options

6. Click Next to proceed with creating the stack.

​

Step 5: Review

1. Scroll through each section and verify the data you have entered.
2. At the bottom of the page, in the Capabilities section, click the checkbox to acknowledge that the StackSet will create IAM resources with custom names, as required.

Figure: Permission to Create Resources

​

Step 6: Run the Template

1. Click Submit to begin the process. The CloudFormation dashboard displays the stack creation progress.
2. Click on the Events tab to see both the progress and status of the stack creation process. Click the Refresh button to show the latest events.
3. Once the StackSet has been created successfully, you can review the results.

• Click the Resources tab to see the list of created resources (e.g. IAM role, policies).
• Click the Outputs tab to see the version of both the CloudFormation template and Lambda function that were run. You will need this version information if you need to upgrade the stackset or the template.

4. You can also log into your Densify instance and verify that the cloud connections are listed in the Cloud Connection wizard.

Figure: Outputs Tab

The initial audit will pick up historical data, if configured and available and each daily audit will collect the last 24-hours of data. If this is a new or trial deployment, you will be contacted, once your data has been analyzed and is ready to review. Otherwise, analysis will be run overnight and you can review the optimization results the morning after creating the cloud connections. See Viewing the Optimization Overview Report for analysis results.

​

Other StackSet Operations

If your accounts are setup using an organizational structure you can use the CloudFormation template to update stacks across the multiple linked accounts and also create the cloud connection within Densify for each of the linked accounts. After the initial StackSet deployment you can do the following:

• Push changes to the existing stack in your accounts.
• Add the stack to additional accounts.
• Delete the stack from the accounts.

​

Editing the Stackset

In most cases you will only need to edit the set of minimum required permissions. The list of minimum required permissions changes as Densify adds new features and functionality,

1. Log into the AWS Management Console and navigate to CloudFormation and select StackSets.
2. Select the StackSet you want to edit and then choose Actions > Edit StackSet details from the dropdown menu at the top of the page.

Figure: Edit StackSet Details

Refer to the AWS documentation for additional details on modifying a StackSet after it has been deployed.

​

Adding the Stackset to New Accounts

1. Log into the AWS Management Console and navigate to CloudFormation and select StackSets.
2. Select the StackSet you want to add and then choose Actions > Add new stacks to StackSet then specify the new accounts as outlined in Step 4.

​

Deleting a Stackset from Accounts

1. Log into the AWS Management Console and navigate to CloudFormation and select StackSets.
2. Select the StackSet you want to delete and then choose Actions > Delete stacks from StackSet then specify the accounts as outlined in Step 4.
3. Navigate to Set Deployment Options and edit the list of accounts.

Figure: Specify Account Details

4. You need to remove any deleted accounts from Densify. See Deleting a Connection for details.

Refer to the AWS documentation for additional details on deleting a StackSet after it has been deployed.