refactor module with all the required files

Author: vara-bonthu

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,65 @@
+name: 🐞 Bug Report
+title: "[Bug]: <title>"
+description: Create a report to help us improve
+labels: ["bug", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ### How to write a good bug report?
+
+        - Respect the issue template as much as possible.
+        - The title should be short and descriptive.
+        - Explain the conditions which led you to report this issue and the context.
+        - The context should lead to something, an idea or a problem that you’re facing.
+        - Remain clear and concise.
+        - Format your messages to help the reader focus on what matters and understand the structure of your message, use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown)
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Welcome to Amazon EKS Blueprints!
+      options:
+        - label: Yes, I've searched similar issues on [GitHub](https://github.com/aws-ia/terraform-aws-observability-accelerator/issues) and didn't find any.
+          required: true
+
+  - type: input
+    attributes:
+      label: Amazon EKS Blueprints Release version
+      description: |
+        `latest` is not considered as a valid version.
+        Enter release number!
+      placeholder: Your version here.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: What is your environment, configuration and the example used?
+      description: |
+        Terraform version, link to example used or your main.tf content etc.
+
+        Use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown) if needed.
+      placeholder: Add information here.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: What did you do and What did you see instead?
+      description: |
+        Provide error details and the expected details.
+
+        Use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown) if needed.
+      placeholder: Add information here.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Additional Information
+      description: Use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown) if needed.
+      placeholder: Add information here.
+      render: shell
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: '[FEATURE] <title>'
+labels: 'feature-request'
+assignees: ''
+
+---
+
+#### Is your feature request related to a problem? Please describe
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+
+#### Describe the solution you'd like
+A clear and concise description of what you want to happen.
+
+
+#### Describe alternatives you've considered
+A clear and concise description of any alternative solutions or features you've considered.
+
+
+#### Additional context
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,24 @@
+---
+name: Question
+about: I have a Question
+title: '[QUESTION] <title>'
+labels: 'question'
+assignees: ''
+
+---
+
+#### Please describe your question here
+<!-- Provide as much information as possible to explain your question -->
+
+
+#### Provide link to the example related to the question
+<!-- Please provide the link to the example related to this question from this repo -->
+
+
+#### Additional context
+<!-- Add any other context or screenshots about the question here -->
+
+
+#### More
+
+- [ ] Yes, I have checked the repo for existing issues before raising this question

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+
+### What does this PR do?
+
+<!-- A brief description of the change being made with this pull request. -->
+
+
+### Motivation
+
+<!-- What inspired you to submit this pull request? -->
+
+
+### More
+
+- [ ] Yes, I have tested the PR using my local account setup  (Provide any test evidence report under Additional Notes)
+- [ ] Yes, I have added a new example under [examples](https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/main/examples) to support my PR
+- [ ] Yes, I have created another PR for add-ons under [add-ons](https://github.com/aws-samples/eks-blueprints-add-ons) repo (if applicable)
+- [ ] Yes, I have updated the [docs](https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/main/docs) for this feature
+- [ ] Yes, I ran `pre-commit run -a` with this PR
+
+
+**Note**: Not all the PRs required examples and docs except a new pattern or add-on added.
+
+### For Moderators
+- [ ] E2E Test successfully complete before merge?
+
+### Additional Notes
+
+<!-- Anything else we should know when reviewing? -->

.header.md

@@ -0,0 +1,15 @@
+# Who is using AWS Observability Accelerator for Terraform?
+
+AWS Observability Accelerator for Terraform has a variety of users and use cases to configure and manage Observability on EKS/ECS clusters.
+Many customers want to learn from others who have already implemented AWS Observability Accelerator in their environments.
+
+The following is a self-reported list of users to help identify adoption and points of contact.
+
+## Add yourself
+
+If you are using AWS Observability Accelerator please consider adding yourself as a user by opening a pull request to this file.
+
+## Adopters (Alphabetical)
+
+| Organization | Description | Contacts | Link |
+| --- | --- | --- | --- |

.terraform-docs.yaml

@@ -1 +1,4 @@
-* @aws-ia/aws-ia
+# Require approvals from someone in the owner team before merging
+# More information here: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+
+* @aws-ia/aws-observability-accelerator