Set up multi-account multi-Region data ingestion
You can use this solution to monitor DevOps metrics from multiple AWS accounts and Regions in a monitoring account. To do so, follow these steps to set up resources and permissions required for streaming data multi-account multi-Region into a central S3 bucket in the monitoring account.
-
Deploy the solution’s main AWS CloudFormation template into a monitoring account, where the data from different accounts are gathered and analyzed. You must enter the AWS account numbers or organization IDs of other accounts in the main template.
-
Deploy the sharing-account-stack.template
into other accounts where the data is generated.
| Parameter | Default | Description |
|---|---|---|
| Monitoring Account Configuration | ||
| ARN of the custom event bus in the monitoring account | <requires input> |
ARN of the custom Amazon EventBridge event bus in the
monitoring account where the events are sent. To find the
ARN, sign in to the AWS CloudFormation console in the
monitoring account, select the solution's main
CloudFormation stack you deployed, open the Outputs tab,
then copy the value for
CustomEventBusArn, for
example,
arn:aws:events:Region:Account:event-bus/EventBusName
|
| ARN of the DevOps metrics S3 bucket in the monitoring account | <requires input> |
Enter the ARN of the S3 bucket in the monitoring account
where DevOps metrics are stored. To find the ARN, sign in to
the AWS CloudFormation console in the monitoring account,
select the solution's main CloudFormation stack you
deployed, open the Outputs tab, then copy the value for
DevOpsMetricsS3Bucket,
for example, arn:aws:s3:::aws-devops-metrics-xxxxxx.
|
| AWS account number of the monitoring account | <requires input> | Enter the AWS account number of the monitoring account where the solution's main template is deployed to receive data from other accounts. |
| AWS region of the monitoring account where the solution's main template is deployed | <requires input> |
Enter the AWS region of the monitoring account where the
solution's main template is deployed to receive data from
other account, for example, us-east-1.
|
| Tag Configuration | ||
| Tag Configuration for filtering on CodeCommit Repositories | <requires input> |
Enter a semicolon-separated list of tags, using comma as a
separator between the tag key and value, for example,
env,prod;anotherKey,anotherValue. This tag is used in an
Athena query to find repositories with the matching tag and
is used as data filter in the QuickSight dashboard. Omitting
a tag value will result in a filter that captures all values
for that tag key. Only repositories matching the combination
of all tags will be captured. Leave it blank if you do not
use the tag feature.
|
| Tag Configuration for filtering on CodeBuild Projects | <requires input> |
Enter a semicolon-separated list of tags, using a comma as a
separator between the tag key and value, for example,
env,prod;anotherKey,anotherValue. This tag is used in an
Athena query to find build projects with the matching tag
and is used as a data filter in QuickSight dashboard.
Omitting a tag value will result in a filter that captures
all values for that tag key. Only build projects matching
the combination of all tags will be captured. Leave it blank
if you do not use the tag feature.
|
| Tag Configuration for filtering on CodePipeline Projects | <requires input> |
Enter a semicolon-separated list of tags, using a comma as a
separator between the tag key and value, for example,
env,prod;anotherKey,anotherValue. This tag is used in an
Athena query to find pipelines with the matching tag and is
used as a data filter in QuickSight dashboard. Omitting a
tag value will result in a filter that captures all values
for that tag key. Only pipelines matching the combination of
all tags will be captured. Leave it blank if you do not use
the tag feature.
|
