Skip to content

Latest commit

 

History

History
 
 

trends

README.md

Pre-Requisites

Note: If the customer has multiple payer accounts, this will need to be done for each payer account individually.

  1. Set up Hourly CUR with Athena compatibility and resource_ids and wait at least 24 hours.

  2. Deploy crawler-cfn.yml CloudFormation template generated in the CUR S3 bucket

  3. Setup Amazon Athena "Query result location" in the Athena "primary" Workgroup

  4. Subscribe to Amazon QuickSight Enterprise Edition

  5. Give Amazon QuickSight role access to CUR bucket

  6. Purchase required amount of SPICE capacity for Amazon QuickSight

  7. Launch AWS CloudShell and upgrade the AWS CLI on your AWS CloudShell

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install --update
  1. Run the ./shell-script/trends.sh script from the trends directory (NOT from trends/shell-script)

Note: Your user would require minimal permissions on the IAM Role described in minimal_permissions.json

Note: map parameter requires AWS Organisations API ListAccounts

./shell-script/trends.sh config
./shell-script/trends.sh prepare
./shell-script/trends.sh deploy-datasets
./shell-script/trends.sh deploy-dashboard
./shell-script/trends.sh map
./shell-script/trends.sh refresh-data-sets

  1. Set up scheduled SPICE refresh for the SPICE datasets:

    • daily_anomaly_detection
    • monthly_anomaly_detection
    • monthly_bill_by_account

  2. To pull updates run

    ./shell-script/trends.sh update-dashboard

  3. To delete Trends dashboard, datasets from Amazon QuickSight and views from Athena run

    ./shell-script/trends.sh delete
./shell-script/trends.sh cleanup