Code Monkey home page Code Monkey logo

antiope's People

Contributors

davidhammturner avatar falequin avatar jchrisfarris avatar kaangoksal avatar kozmic avatar zmarouf avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

antiope's Issues

Trouble getting this to deploy

I'm trying to follow the directions in INSTALL.md - I have all the pre-reqs set up.

I cloned the repo and created a config.env as specified. Then tried running the deploy_stack. Looks like that actually needs to run from inside the aws_inventory directory given the pathing in the command.

I tried to edit the Manifest file. Setting the StackName is unclear where and how to do that. I removed the pBucketName definition but pDeployBucket doesn't exist. Then I tried running the make command. It was looking for config.prod so a copied config.env to that. But the make fails. I get a couple of these errors:

*** No rule to make target yaml', needed by zipfile'. Stop.

Any ideas?

Comparisons

I came across this while exploring the turner labs terraform tools, and was curious for a comparison to Netflix security monkey, or cloud custodian

Present or purge duplicate billing data

AWS Only updates the billing data every six hours, but the inventory pulls the data every 30 minutes. The DDB table will get pretty large if we don't do something about purge or dedup.

Keeping all resource objects in Resources/

Keeping all resource objects in Resources/ is going to cause that to grow tremendously. Reindexing will become impossible too.

I think there will need to be some task that moves resource objects older than 7 days to a Aged-Resources subfolder (possibly even by YYYY-MM) to remain manageable.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.