Initial Contribution of the AWS Connector (eclipse-kanto#1)

[eclipse-kanto#2] Initial Contribution of the AWS Connector

.gitattributes

@@ -0,0 +1 @@
+*.go text eol=lf

.github/workflows/validation.yaml

@@ -0,0 +1,45 @@
+name: Validation
+
+on:
+  pull_request:
+    branches:
+      - main
+    paths-ignore:
+      - "**/*.md"
+  push:
+    branches:
+      - main
+    paths-ignore:
+      - "**/*.md"
+
+jobs:
+  validation:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-go@v2
+        with:
+          go-version: '1.21.0'
+      - name: Setup
+        run: |
+          go mod download
+          go install golang.org/x/lint/golint@latest
+          go get -t ./...
+      - name: Format
+        run: |
+          unformatted_code=$(gofmt -l .)
+          if [ -n "$unformatted_code" ]; then
+            echo "Improperly formatted code:"
+            echo "$unformatted_code"
+            exit 1
+          fi
+      - name: Lint
+        run: |
+          golint -set_exit_status ./...
+      - name: Vet
+        run: |
+          go vet ./...
+      - name: Test
+        run: |
+          go test ./... -coverprofile coverage.out -covermode count
+          go tool cover -func coverage.out

.gitignore

@@ -0,0 +1,2 @@
+.idea/
+.vscode/

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Community Code of Conduct
+
+**Version 1.2
+August 19, 2020**
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as community members, contributors, committers, and project leaders pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, 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
+
+With the support of the Eclipse Foundation staff (the “Staff”), project committers and leaders 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 committers and leaders 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 within all project spaces, and it also applies when an individual is representing the Eclipse Foundation project or its community in public spaces. Examples of representing a project or community include posting via an official social media account, or acting as a project representative at an online or offline event. Representation of a project may be further defined and clarified by project committers, leaders, or the EMO.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Staff at codeofconduct@eclipse.org. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The Staff is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project committers or leaders who do not follow the Code of Conduct in good faith may face temporary or permanent repercussions as determined by the Staff.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org) , version 1.4, available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html](https://www.contributor-covenant.org/version/1/4/code-of-conduct/)

CONTRIBUTING.md

@@ -0,0 +1,70 @@
+# How to Contribute to Eclipse Kanto - AWS Connector
+
+First of all, thanks for considering to contribute to Eclipse Kanto - AWS Connector. We really
+appreciate the time and effort you want to spend helping to improve things around here.
+
+In order to get you started as fast as possible we need to go through some organizational issues first, though.
+
+## Eclipse Contributor Agreement
+
+Before your contribution can be accepted by the project team contributors must
+electronically sign the Eclipse Contributor Agreement (ECA).
+
+* http://www.eclipse.org/legal/ECA.php
+
+Commits that are provided by non-committers must have a Signed-off-by field in
+the footer indicating that the author is aware of the terms by which the
+contribution has been provided to the project. The non-committer must
+additionally have an Eclipse Foundation account and must have a signed Eclipse
+Contributor Agreement (ECA) on file.
+
+For more information, please see the Eclipse Committer Handbook:
+https://www.eclipse.org/projects/handbook/#resources-commit
+
+## Code Style Guide
+
+* Keep the code well-formatted through: `gofmt`
+* Keep the code error-free through: `go vet` and `golint`
+* Avoid common mistakes and pitfalls following: [Go Code Review Comments](https://github.com/golang/go/wiki/CodeReviewComments)
+
+## Making Your Changes
+
+* Fork the repository on GitHub.
+* Create a new branch for your changes.
+* Make your changes following the code style guide (see Code Style Guide section above).
+* When you create new files make sure you include a proper license header at the top of the file (see License Header section below).
+* Make sure you include test cases for non-trivial features.
+* Make sure test cases provide sufficient code coverage (see GitHub actions for minimal accepted coverage).
+* Make sure the test suite passes after your changes.
+* Commit your changes into that branch.
+* Use descriptive and meaningful commit messages. Start the first line of the commit message with the issue number and titile e.g. `[#9865] Add token based authentication`.
+* Squash multiple commits that are related to each other semantically into a single one.
+* Make sure you use the `-s` flag when committing as explained above.
+* Push your changes to your branch in your forked repository.
+
+## License Header
+
+Please make sure any file you newly create contains a proper license header like this:
+
+Adjusted for Go files:
+```go
+// Copyright (c) {year} Contributors to the Eclipse Foundation
+//
+// See the NOTICE file(s) distributed with this work for additional
+// information regarding copyright ownership.
+//
+// This program and the accompanying materials are made available under the
+// terms of the Eclipse Public License 2.0 which is available at
+// https://www.eclipse.org/legal/epl-2.0, or the Apache License, Version 2.0
+// which is available at https://www.apache.org/licenses/LICENSE-2.0.
+//
+// SPDX-License-Identifier: EPL-2.0 OR Apache-2.0
+```
+
+## Submitting the Changes
+
+Submit a pull request via the normal GitHub UI.
+
+## After Submitting
+
+* Do not use your branch for any other development, otherwise further changes that you make will be visible in the PR.