You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This terraform module sends a daily cost report and the cost delta in a 7 day rolling period, scheduled on a CRON to a slack or teams channel of your choice.
The module also reports on the top 5 services attributing to the daily cost. Its a very rudimentary means of managing the cost of your AWS bill, but it does provide a 1000 ft view of the current expenses for the previous day. More on this module can be found on our blog on Medium.
Lambda deployment package
The Lambda function is deployed using a .zip deployment package. The package is contained within this module and also attached to the GitHub release.
You may choose one of the following options for the deployment:
default: If no s3_* variables are specified, then the package is used by the lambda directly.
recommended: s3_bucket can be specified to upload the package to the S3 bucket, for the lambda to use.
s3_prefix can be specified to override the default location.
upload_deployment_to_s3=false can be specified to disable the upload, in which case the package must be placed on s3 manually.
Examples
See examples dropdown on Terraform Cloud, or browse here.
Specifies the number of days you want to retain log events in the specified log group. Possible values are: 1, 3, 5, 7, 14, 30, 60, 90, 120, 150, 180, 365, 400, 545, 731, 1827, and 3653.
IAM role ARN attached to the Lambda Function. This governs both who / what can invoke your Lambda Function, as well as what resources our Lambda Function has access to. See Lambda Permission Model for more details.
If true, the deployment package within this module repo will be copied to S3. If false then the S3 object must be uploaded separately. Ignored if s3_bucket is null.