aws-reference-architectures/datalake
  • Overview of a Data Lake on AWS
  • Amazon S3: A Storage Foundation for Datalakes on AWS
    • Data lake Storage Architecture FAQs
  • Data Catalog Architecture
    • Schema Management Within a Data Catalog
  • Data Security and Access Control Architecture
    • Data Security and Access Control Using IAM
    • Fine-grained Access Control With AWS LakeFormation
  • Ingestion Architectures for Data lakes on AWS
    • Data Ingestion using Kinesis Firehose and Kinesis Producer Library (KPL)
    • Data Ingestion using Database Migration Service(DMS) and Lambda
    • Data Ingestion using Amazon Glue
    • Data Ingestion From On-Premise NFS using Amazon DataSync
  • Data Curation Architectures
    • Overwrite Table Partitions Using PySpark
  • Data Consumption Architectures
    • Query S3 Data lake using Athena and Glue Catalog
    • Query Data lake using Redshift Spectrum and Glue Catalog
    • Query Data lake using EMR and External Hive Metastore in VPC
    • Query Data lake using EMR and Glue Catalog
  • Code of Conduct
  • Contributing Guidelines
Powered by GitBook
On this page
  • Join our Slack channel to share feedback.
  • Reporting Bugs/Feature Requests
  • Contributing via Pull Requests
  • Finding contributions to work on
  • Code of Conduct
  • Security issue notifications
  • Licensing

Was this helpful?

Contributing Guidelines

PreviousCode of Conduct

Last updated 5 years ago

Was this helpful?

Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional documentation, we greatly value feedback and contributions from our community.

Please read through this document before submitting any issues or pull requests to ensure we have all the necessary information to effectively respond to your bug report or contribution.

Join our to share feedback.

Reporting Bugs/Feature Requests

We welcome you to use the GitHub issue tracker to report bugs or suggest features.

When filing an issue, please check , or , issues to make sure somebody else hasn't already reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:

  • A reproducible test case or series of steps

  • The version of our code being used

  • Any modifications you've made relevant to the bug

  • Anything unusual about your environment or deployment

Contributing via Pull Requests

Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:

  1. You are working against the latest source on the master branch.

  2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.

  3. You open an issue to discuss any significant work - we would hate for your time to be wasted.

To send us a pull request, please:

  1. Fork the repository.

  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.

  3. Ensure local tests pass.

  4. Commit to your fork using clear commit messages.

  5. Send us a pull request, answering any default questions in the pull request interface.

  6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.

Finding contributions to work on

Code of Conduct

Security issue notifications

Licensing

GitHub provides additional document on and .

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 issues is a great place to start.

This project has adopted the . For more information see the or contact opensource-codeofconduct@amazon.com with any additional questions or comments.

If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our . Please do not create a public github issue.

See the file for our project's licensing. We will ask you to confirm the licensing of your contribution.

We may ask you to sign a for larger changes.

Slack channel
existing open
recently closed
forking a repository
creating a pull request
'help wanted'
Amazon Open Source Code of Conduct
Code of Conduct FAQ
vulnerability reporting page
LICENSE
Contributor License Agreement (CLA)