Closed prasenforu closed 7 years ago
@prasenforu S3_REPORT_PATH
must have the value exactly as mentioned by Report path
field at billing reports page
Can you post a screenshot of your billing reports page. It must look something like this.
Now a day its not visible. This changes I noticed in January 17 onwards. That is why I took initial screen shot.
You can try, the screen shot you send its old.
So once you create request after that not visible that record but you will get report data.
oh I see. Thanks for the info. In that case the value for S3_REPORT_PATH
will be /awscoebilling
OK will try one more time and let you know.
For this setup its not working t2.micro due to memory issue.
So for that I have to choose t2.medium which is changeable and not in free tier.
Any way I dowloaded the bill csv file kept in test/sample folder then rename that file with "test_ub_cost_2016-06.csv" then run "docker-compose -f docker-compose-test.yml up -d"
Then followed below steps
But Dashboard not coming.
Anyway ....
Thanks your reply..
will update you :)
Yeah that's fine. BecauseS3_REPORT_PATH
starts with /
and report name file S3_REPORT_NAME=awscoebilling-1.cvs.gz
or only
S3_REPORT_NAME=awscoebilling
Let me know do I need to give "/" before file name
S3_REPORT_NAME=/awscoebilling
It will be S3_REPORT_NAME=awscoebilling
Sorry I updated my previous comment. Just change S3_REPORT_NAME=awscoebilling
Everything else looks good.
Ok Let me try NOW :)
Please pray good luck for me :)
yday onward I launched 10 times t2.medium ;)
Fantastic :)
Thanks you man it worked .......
@prasenforu Glad I could help. Would love to hear your feedback. Thanks
I am not sure how to send feedback, please guide me.
I am happy to send feedback.
By the way if my entire environment (all container) running, will this pull biiling report from S3 everyday ?
@prasenforu In order to pull new billing report you need to restart the container.
docker-compose restart
will be good enough.
Email Sent. :)
I could not find any billing report under under Path
getting all time same error, did multiple combination in prod.env file but same error.
Thnx :)
Prasen