applatix / claudia Goto Github PK

We have a significant number of reserved instances. They are not being included in the pricing calculations. By limiting all of these reports to EC2 Instance costs only.. I can go to the AWS Cost Reports page and I do see the reserved costs (I can toggle them on/off with the check box.) When off, the total cost is nearly equal between cost explorer and claudia. When on, claudia is low by the amount of the reserved costs.

I then went into Claudia and under filter services then advanced, I clicked on dedicated instances. That number matches nearly exactly with cost explorer. When I uncheck dedicated and check reserved, the total cost is zero.

The terminology used throughout Claudia, to indicate the path of where billing reports will be located within the bucket, is currently "report prefix", or "report path prefix." The term "report path prefix" is what AWS uses when creating a report. However, "report path" is used when viewing the report settings, as shown in the following screenshot.

The term "report path" is more appropriate, and should eliminate confusion for new users. I will be switching both internal and external references from report prefix and report path prefix to just "report path."

In #4 (comment), we can see some AWS products showing up under the Marketplace service instead of their own. Specifically, CodeBuild and ElasticMapReduce. There may be others. The current logic keys off of the word Amazon or AWS in the service name to decide if it is an Amazon vs. marketplace product. It seems that for these products, Amazon does not include either of those words, so it fell into marketplace.

Publishing AMIs via Amazon Marketplace is an extremely slow and painful process, with the latest submission taking over 3 weeks for approval (and counting).

Claudia does not inherently depend on anything in the AMI other than docker, meaning when we rebuild a new AMI from a later claudia release, the only thing we are changing is the baked-in container image. Since claudia images are available on dockerhub, we could dynamically retrieve the latest stable release during the initial startup so that when new users launch claudia, they are getting the latest version, without having to wait for the marketplace listing to become approved.

So long as the docker version does not need to be updated, publishing a new Claudia version would only involve pushing and tagging the latest claudia release either on dockerhub (or github), which the initialization script use to decide which version of claudia to run during initial launch.

Note that this auto-selection of image version should happen once, during initial start.

ERROR: pull access denied for claudia, repository does not exist or may require 'docker login'

while i run docker-compose up , I got above error message

Is there an API or way to automate importing account aliases? Even if I could pass in a csv file with account number to alias that would make life so much easier. I haven't looked thru the code yet to determine the underlying API in order to automate it but was wondering if there is an officially supported way to automate importing it as importing one or two manually is fine, when you have over 100 accounts it gets a bit tedious.

Hi,
I am getting TLS handshake error:

http: TLS handshake error from 192.168.122.1:33936: remote error: tls: bad certificate

How can I fix this, or is there a way to not redirect from 80 -> 443 ?

Hi,

as I tried to launch your AMI I noted that the instance automatically redirects all traffic from HTTP to HTTPS. This makes the AMI very impractical to use since if I have a setup like HTTPS -> CloudFront -> HTTP -> ALB -> HTTP -> EC2 it won't work. Would it be possible to release the AMI without it? Even as I tried to run the app locally with docker-compose it wouldn't work as the app keeps redirecting http://localhost to https://localhost.

Otherwise the app looks good, nice work!

Teemu

Currently we do not support upgrades in claudia. One simple way to handle upgrade is by adding a simple shell/python script in the AMI to stop and restart the containers with the later tag. The user would run this script and pass in the target version, which would handle the docker-compose down/up with later images.

When viewing the spend report for AWS Marketplace service and grouping by product most products are some sort of hash or ID. It would be great if they could be resolved to an actual name, I've had to google these IDs to determine what they are using http://thecloudmarket.com/ to determine what they are and help determine if they are necessary. Below is an example screenshot of the table.