Formatting

.gitattributes

@@ -0,0 +1,2 @@
+* text=auto
+readme.md merge=union

.yo-rc.json

@@ -0,0 +1,8 @@
+{
+  "generator-awesome-list": {
+    "promptValues": {
+      "username": "Jacob Silva",
+      "email": "jacob.silva0123@gmail.com"
+    }
+  }
+}

README.md

@@ -1,6 +1,10 @@
-# Awesome Cloud Security
+# Awesome Cloud Security [![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)](https://github.com/sindresorhus/awesome)
+
+> cloud security information
+
+
+## Contents
 
-## Table of Contents
 * [Blogs](#blogs)
 * [Podcasts](#podcasts)
 * [Projects](#projects)
@@ -9,8 +13,11 @@
   * [Automated Security Assessment](#automated-security-assessment)
   * [Data Loss Prevention](#data-loss-prevention)
   * [Logging](#logging)
+* [Contribute](#contribute)
+* [License](#license)
 
 ## Blogs
+
 * [AWS Security](https://aws.amazon.com/blogs/security/)
 
 ## Podcasts
@@ -20,10 +27,14 @@
 ## Examples
 
 ### IAM
+
+Identity and Access Management
+
 * [Amazon Cognito Streams connector for Amazon Redshift](https://github.com/awslabs/amazon-cognito-streams-sample)
 
 
 ### Automated Security Assessment
+
 * [AWS Config Rules Repository](https://github.com/awslabs/aws-config-rules)
 * [AWS Inspector Agent Autodeploy](https://github.com/awslabs/amazon-inspector-agent-autodeploy)
 * [AWS Inspector Auto Remediation](https://github.com/awslabs/amazon-inspector-auto-remediate)
@@ -31,14 +42,30 @@
 * [AWS Security Benchmark](https://github.com/awslabs/aws-security-benchmark)
 
 ### Data Loss Prevention
+
 * [GIT Secrets](https://github.com/awslabs/git-secrets)
 
 ### Logging
+
 * [AWS Centralized Logging](https://github.com/awslabs/aws-centralized-logging)
 * [AWS Config Snapshots to ElasticSearch](https://github.com/awslabs/aws-config-to-elasticsearch)
 * [AWS CloudWatch Events Monitor Security Groups](https://github.com/awslabs/cwe-monitor-secgrp)
 
 
 ### Web Application Firewall
+
 * [AWS WAF Sample](https://github.com/awslabs/aws-waf-sample)
-* [AWS WAF Security Automations](https://github.com/awslabs/aws-waf-security-automations)
+* [AWS WAF Security Automations](https://github.com/awslabs/aws-waf-security-automations)
+
+
+## Contribute
+
+Contributions welcome! Read the [contribution guidelines](contributing.md) first.
+
+
+## License
+
+[![CC0](http://mirrors.creativecommons.org/presskit/buttons/88x31/svg/cc-zero.svg)](http://creativecommons.org/publicdomain/zero/1.0)
+
+To the extent possible under law, Jacob Silva has waived all copyright and
+related or neighboring rights to this work.

code-of-conduct.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at jacob.silva0123@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

contributing.md

@@ -0,0 +1,25 @@
+# Contribution Guidelines
+
+Please note that this project is released with a
+[Contributor Code of Conduct](code-of-conduct.md). By participating in this
+project you agree to abide by its terms.
+
+---
+
+Ensure your pull request adheres to the following guidelines:
+
+- Make sure you take care of this
+- And this as well
+- And don't forget to check this
+
+Thank you for your suggestions!
+
+
+## Updating your PR
+
+A lot of times, making a PR adhere to the standards above can be difficult.
+If the maintainers notice anything that we'd like changed, we'll ask you to
+edit your PR before we merge it. There's no need to open a new PR, just edit
+the existing one. If you're not sure how to do that,
+[here is a guide](https://github.com/RichardLitt/docs/blob/master/amending-a-commit-guide.md)
+on the different ways you can update your PR so that we can merge it.