Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Matthew Gladman
    @mattisdada
    Quick question about Finala, does it support AWS Organisations? Or would I have to setup each AWS account?
    Costya Regev
    @cregev
    Hi @mattisdada
    Benedikt Wieloch
    @bene-dt0
    Hello just tried finala on my private aws account and it works super fine. I have just one question and I know this might be newbish, but I got a message which says my ACCESS_Key and SECRET are not set. Is this a problem? And how can I fix this?
    WARNING: The AWS_ACCESS_KEY_ID variable is not set. Defaulting to a blank string.
    WARNING: The AWS_SECRET_ACCESS_KEY variable is not set. Defaulting to a blank string.
    Benedikt Wieloch
    @bene-dt0
    It seems as this is not a problem because the provided environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY are optional?
    Costya Regev
    @cregev
    @bene-dt0 thanks for writing here, We will take a look at that.
    Benedikt Wieloch
    @bene-dt0
    I have added additional EC2 checks to the existing ones within the collector.yaml. Now some instances are listed twice and thus distort the result of the savings. Is it possible to merge duplicate listed resources/findings and thus display the correct "Monthly unused resources"? Is this already possible or would this be a new feature request?
    Costya Regev
    @cregev
    Hi @bene-dt0 Did you add more checks for a single resource ?
    Costya Regev
    @cregev
    Can you please share you configuration for the collector ?
    Benedikt Wieloch
    @bene-dt0

    Hey @cregev. Yes, I've added more checks for a single ressource. I've seen and tested your example configuration (https://files.gitter.im/5f0b4e52d73408ce4fe963a0/vbww/image.png). When I list the EC2 resource two times like in your example I only get the latest/2nd (in this case ConsumedReadCapacityUnits) metric evaluated. The first doesn't show up in the UI, even though it should.

    When I put both metrics in the same ressource, the found instance is listed twice.

    Here is my configuration:

        metrics:
          ec2:
            - description: TA - Network Input
              enable: true
              metrics:
                - name: NetworkIn
                  statistic: Sum
              period: 24h 
              start_time: 168h # 24h * 7d
              constraint:
                operator: "<"
                value: 10485760 # (10 * 1024 * 1024) = 10 MB
    
            - description: CPU utilization 
              enable: true
              metrics:
                - name: CPUUtilization
                  statistic: Average
              period: 24h 
              start_time: 168h # 24h * 7d
              constraint:
                operator: "<"
                value: 10

    The result looks like this:

    alt
    The instance i-01361 is listed twice.

    Costya Regev
    @cregev
    Thank you @bene-dt0 I will take a look at it in the beginning of the next week.
    Chris Altman
    @Altonymous
    I'd like to exclude all AWS resources with a specific tag. Is there a way to configure this?