├── PULL_REQUEST_TEMPLATE ├── CODE_OF_CONDUCT.md ├── profile └── README.md ├── SECURITY.md └── CONTRIBUTING.md /PULL_REQUEST_TEMPLATE: -------------------------------------------------------------------------------- 1 | *Issue #, if available:* 2 | 3 | *Description of changes:* 4 | 5 | 6 | By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice. 7 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | ## Code of Conduct 2 | This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 3 | For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 4 | opensource-codeofconduct@amazon.com with any additional questions or comments. 5 | -------------------------------------------------------------------------------- /profile/README.md: -------------------------------------------------------------------------------- 1 | ## AWS Solutions 2 | AWS Solutions bring together AWS services into pre-configured deployable code, architecture diagrams, and implementation guides. Developed, maintained and supported by AWS, AWS Solutions simplify the deployment of optimized infrastructure tailored to meet customer use cases. 3 | 4 | Find out more at: https://aws.amazon.com/solutions/what-are-solutions/ 5 | 6 | AWS Solutions Library: https://aws.amazon.com/solutions/ 7 | 8 | 9 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | ## Reporting Security Issues 2 | 3 | Amazon Web Services (AWS) is dedicated to the responsible disclosure of security vulnerabilities. 4 | 5 | We kindly ask that you **do not** open a public GitHub issue to report security concerns. 6 | 7 | Instead, please submit the issue to the AWS Vulnerability Disclosure Program via [HackerOne](https://hackerone.com/aws_vdp) or send your report via [email](mailto:aws-security@amazon.com). 8 | 9 | For more details, visit the [AWS Vulnerability Reporting Page](http://aws.amazon.com/security/vulnerability-reporting/). 10 | 11 | Thank you in advance for collaborating with us to help protect our customers. 12 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing Guidelines 2 | 3 | Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional 4 | documentation, we greatly value feedback and contributions from our community. 5 | 6 | Please read through this document before submitting any issues or pull requests to ensure we have all the necessary 7 | information to effectively respond to your bug report or contribution. 8 | 9 | 10 | ## Security issue notifications 11 | If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public GitHub issue. 12 | 13 | 14 | ## Reporting Bugs/Feature Requests 15 | 16 | We welcome you to use the GitHub issue tracker to report bugs or suggest features. 17 | 18 | When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already 19 | reported the issue. Please try to include as much information as you can. Details like these are incredibly useful: 20 | 21 | * A reproducible test case or series of steps 22 | * The version of our code being used 23 | * Any modifications you've made relevant to the bug 24 | * Anything unusual about your environment or deployment 25 | 26 | 27 | ## Contributing via Pull Requests 28 | Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that: 29 | 30 | 1. You are working against the latest source on the *main* branch. 31 | 2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already. 32 | 3. You open an issue to discuss any significant work - we would hate for your time to be wasted. 33 | 34 | To send us a pull request, please: 35 | 36 | 1. Fork the repository. 37 | 2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change. 38 | 3. Ensure local tests pass. 39 | 4. Commit to your fork using clear commit messages. 40 | 5. Send us a pull request, answering any default questions in the pull request interface. 41 | 6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation. 42 | 43 | GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and 44 | [creating a pull request](https://help.github.com/articles/creating-a-pull-request/). 45 | 46 | 47 | ## Finding contributions to work on 48 | Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start. 49 | 50 | 51 | ## Code of Conduct 52 | This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 53 | For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 54 | opensource-codeofconduct@amazon.com with any additional questions or comments. 55 | 56 | 57 | ## Licensing 58 | 59 | See the LICENSE file for our project's licensing. We will ask you to confirm the licensing of your contribution. 60 | --------------------------------------------------------------------------------