From 2a1a27f39da98f8fcb0a87055f71b948142ca58f Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 14 Dec 2023 17:02:11 +0000 Subject: [PATCH] Commit changes made by code formatters --- runbooks/source/analyze-vpc-flow-logs.html.md.erb | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/runbooks/source/analyze-vpc-flow-logs.html.md.erb b/runbooks/source/analyze-vpc-flow-logs.html.md.erb index 536feb35..4842871e 100644 --- a/runbooks/source/analyze-vpc-flow-logs.html.md.erb +++ b/runbooks/source/analyze-vpc-flow-logs.html.md.erb @@ -5,9 +5,9 @@ last_reviewed_on: 2023-12-14 review_in: 6 months --- -# <%= current_page.data.title %> +# <%= current_page.data.title %> -Cloud Platform `live-1` VPC is connected to various other MoJ AWS accounts using Transit Gateway. In order to debug network connectivity issues +Cloud Platform `live-1` VPC is connected to various other MoJ AWS accounts using Transit Gateway. In order to debug network connectivity issues that are coming to/from Cloud Platform VPC, the VPC flow logs are enabled. These logs are stored in an S3 bucket and can be analyzed using Athena when needed. The steps involve a pointy-clicky exercise to generate Athena integration by creating a CloudFormation stack using a template and use that as a datasource in Athena @@ -18,5 +18,3 @@ Things to note: - Provide Partition start date and end date closer when the issue was observed. The duration is limited to 20 days - Create two s3 buckets one for CloudFormation template and and another one to store the Athena query results which you will provide when creating the CloudFormation stack. - When the flow logs are downloaded and the user has investigated the issue, delete the created s3 buckets for CloudFormation template and Athena query results and the CloudFormation stack. - -