Optional post-deployment activities and FAQ - Cloud Intelligence Dashboards on AWS
Post-deployment configurationFAQ

Optional post-deployment activities and FAQ

Post-deployment configuration

Lambda Partitioner function

Amazon CloudWatch Log Group Retention

The logs of the Partitioner function are kept for 14 days. If needed, change the retention period directly on the Amazon CloudWatch console.

FAQ

I installed the dashboard, how can I test the data pipeline works correctly?

See I installed the dashboard successfully, but there’s no data below.

I installed the dashboard successfully, but there’s no data

If you followed our recommendations in the prerequisites, AWS Config delivers a configuration snapshot file every 24 hours, so you will probably start seeing data in a couple of days, depending on when the configuration snapshot files are generated and when the QuickSight datasets are refreshed.

AWS Config generates history records approximately 6 hours after a resource is changed. These records will be loaded on the dasboard faster, and be visible on the Configuration Item Events tab.

Follow these steps to have AWS Config generate a configuration snapshot and visulize its data on the dashboard:

  1. Log into the AWS Management Console of an account of you organization.

  2. Open AWS CloudShell in the region whose data you want to export.

  3. Run the following command:

    aws configservice describe-delivery-channels

  1. This command will provide information about your current delivery channel configuration, including the S3 bucket where configuration updates are sent and the configuration snapshot delivery properties. The output of the CLI command should look like this:

    {
     "DeliveryChannels": [
         {
             "name": "[YOUR-DELIVERY-CHANNEL-NAME]",
             "s3BucketName": "[YOUR-LOG-ARCHIVE-BUCKET-NAME]",
             "s3KeyPrefix": "[OPTIONAL-S3-PREFIX-FOR-AWS-CONFIG-FILES]",
             "configSnapshotDeliveryProperties": {
                 "deliveryFrequency": "TwentyFour_Hours"
             }
         }
     ]
 }

  2. Note down the name of your delivery channel.

  3. Run this command to generate an AWS Config snapshot (replace "YOUR-DELIVERY-CHANNEL-NAME" with the name reported above):

    aws configservice deliver-config-snapshot --delivery-channel-name "`YOUR-DELIVERY-CHANNEL-NAME`"

    The snapshot file will be delivered to the Log Archive bucket, optionally replicated to the Dashboard bucket, and indexed by the Lambda Partitioner function.

  4. Optionally repeat these steps on other AWS accounts/regions. We recommend doing this only for test purposes, or for rapidly checking the AWS Config data of a few accounts of your interest. AWS Config will deliver a snapshot file for all your resources within 24 hours.

  5. Open Athena and query the table (or any view) to see if the data has been indexed.

SELECT * FROM "`cid_crcd_database`".”cid_crcd_config” limit 10;

  1. Log onto QuickSight and refresh your datasets before opening the dashboard.