iSharkFly-Docs
/
opensearch-docs-cn
mirror of https://github.com/iSharkFly-Docs/opensearch-docs-cn
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Style changes, corrects directory for security plugin

This commit is contained in:
aetter 2021-05-05 19:03:07 -07:00
parent ac6ade448b
commit 691f323be7
15 changed files with 130 additions and 92 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

95
_sass/color_schemes/opensearch.scss
View File

@ -2,60 +2,55 @@
// Brand colors
//
$blue-300: #0055A6;
$blue-200: #005EB8; // Pacific Blue
$blue-100: #337EC6;
$blue-000: #80AFDC;
$blue-dk-300: #003b5c; // Deep Blue Sea
$blue-dk-200: #47738D;
$blue-dk-100: #A3BDCC;
$blue-dk-000: #E6EEF2;
$blue-vibrant-300: #00a3e0; // Open Sky
$blue-vibrant-200: #46BDE9;
$blue-vibrant-100: #92D9F3;
$blue-vibrant-000: #CCF1FF;
$blue-lt-300: #b9d9eb; // Pacific Sky
$blue-lt-200: #C0DDED;
$blue-lt-100: #D5E8F3;
$blue-lt-000: #EAF4F9;
$white: #FFFFFF;
$grey-dk-300: #002A3A; //
$grey-dk-250: mix(white, $grey-dk-300, 12.5%);
$grey-dk-200: mix(white, $grey-dk-300, 25%);
$grey-dk-100: mix(white, $grey-dk-300, 50%);
$grey-dk-000: mix(white, $grey-dk-300, 75%);
$grey-dk-300: #002A3A; // Midnight Sky
$grey-dk-200: #1B4859;
$grey-dk-100: #346173;
$grey-dk-000: #4D8399;
$grey-lt-300: #D9E1E2; //
$grey-lt-200: mix(white, $grey-lt-300, 25%);
$grey-lt-100: mix(white, $grey-lt-300, 50%);
$grey-lt-000: mix(white, $grey-lt-300, 75%);
$grey-lt-300: #D9E1E2; // San Francisco Fog
$grey-lt-000: #F5F7F7;
$blue-300: #005eb8; //
$blue-200: mix(white, $blue-300, 25%);
$blue-100: mix(white, $blue-300, 50%);
$blue-000: mix(white, $blue-300, 75%);
$purple-000: #963CBD; // Purple Sage
$purple-100: #8736AA;
$purple-200: #692A84;
$purple-300: #4B1E5F;
$purple-300: #963CBD; //
$purple-200: mix(white, $purple-300, 25%);
$purple-100: mix(white, $purple-300, 50%);
$purple-000: mix(white, $purple-300, 75%);
$green-000: #2CD5C4; // Seafoam Mint
$green-100: #28C0B0;
$green-200: #1F9589;
$green-300: #166B62;
$green-300: #2cd5c4; //
$green-200: mix(white, $green-300, 25%);
$green-100: mix(white, $green-300, 50%);
$green-000: mix(white, $green-300, 75%);
$yellow-000: #FFB81C; // Golden Poppy
$yellow-100: #CC9316;
$yellow-200: #996E11;
$yellow-300: #664A0B;
$yellow-300: #FFDF00; //
$yellow-200: mix(white, $yellow-300, 25%);
$yellow-100: mix(white, $yellow-300, 50%);
$yellow-000: mix(white, $yellow-300, 75%);
$red-300: #F65275; //
$red-200: mix(white, $red-300, 25%);
$red-100: mix(white, $red-300, 50%);
$red-000: mix(white, $red-300, 75%);
$blue-lt-300: #00A3E0; //
$blue-lt-200: mix(white, $blue-lt-300, 25%);
$blue-lt-100: mix(white, $blue-lt-300, 50%);
$blue-lt-000: mix(white, $blue-lt-300, 75%);
/*
Other, unused brand colors
Float #2797F4
Firewall #0FF006B
Hyper Pink #F261A1
Cluster #ED20EB
Back End #808080
Python #25EE5C
Warm Node #FEA501
*/
$red-000: #F65275; // Malibu Sunrise
$red-100: #DD4A69;
$red-200: #AC3952;
$red-300: #7B293B;
$body-background-color: $white;
$sidebar-color: $grey-lt-000;
@ -63,10 +58,10 @@ $code-background-color: $grey-lt-000;
$body-text-color: $grey-dk-200;
$body-heading-color: $grey-dk-300;
$nav-child-link-color: $grey-dk-200;
$link-color: mix(black, $blue-lt-300, 37.5%);
$nav-child-link-color: $blue-200;
$link-color: $blue-300;
$btn-primary-color: $purple-300;
$base-button-color: $grey-lt-000;
$base-button-color: $grey-lt-300;
// $border-color: $grey-dk-200;
// $search-result-preview-color: $grey-dk-000;

27
_sass/custom/custom.scss
View File

@ -1,9 +1,9 @@
@import url('https://fonts.googleapis.com/css?family=Open+Sans:400,400i,600,700');
@import url('https://fonts.googleapis.com/css2?family=Open+Sans+Condensed:wght@700&display=swap');
// Additional variables
$table-border-color: $grey-lt-300;
$toc-width: 232px !default;
$red-dk-200: mix(black, $red-300, 25%);
// Replaces xl size
$media-queries: (
@ -23,7 +23,7 @@ body {
}
code {
font-family: "SFMono-Regular", Menlo, "DejaVu Sans Mono", "Droid Sans Mono", Consolas, Monospace;
font-family: "SFMono-Regular", Menlo, "DejaVu Sans Mono", "Droid Sans Mono", Consolas, monospace;
font-size: 0.75rem;
}
@ -47,9 +47,14 @@ code {
}
}
h1, h2, h3, h4, h5, h6 {
font-family: "Open Sans Condensed", "Open Sans", sans-serif;
font-weight: 400;
margin-top: 2.4rem;
margin-bottom: 0.8rem;
}
h4 {
font-size: 14px !important;
}
.highlight {
line-height: 1.4;
}
@ -74,12 +79,12 @@ img {
}
.img-border {
border: 1px solid $grey-lt-200;
border: 1px solid $grey-lt-300;
}
// Note, tip, and warning blocks
%callout {
border: 1px solid $grey-lt-200;
border: 1px solid $grey-lt-300;
border-radius: 5px;
margin: 1rem 0;
padding: 1rem;
@ -93,12 +98,12 @@ img {
.tip {
@extend %callout;
border-left: 5px solid $green-300;
border-left: 5px solid $green-100;
}
.warning {
@extend %callout;
border-left: 5px solid $red-dk-200;
border-left: 5px solid $red-100;
}
// Labels
@ -112,16 +117,16 @@ img {
}
.label-purple {
background-color: $purple-300;
background-color: $purple-200;
}
.label-red {
background-color: $red-300;
background-color: $red-100;
}
.label-yellow {
color: $grey-dk-200;
background-color: $yellow-300;
color: $grey-dk-300;
background-color: $yellow-000;
}
// Buttons
@ -130,7 +135,7 @@ img {
}
.btn-purple {
@include btn-color($white, $purple-300);
@include btn-color($white, $purple-200);
}
.btn-blue {

22
docs/install/docker-security.md
View File

@ -42,11 +42,11 @@ services:
- ./admin.pem:/usr/share/opensearch/config/admin.pem
- ./admin-key.pem:/usr/share/opensearch/config/admin-key.pem
- ./custom-opensearch.yml:/usr/share/opensearch/config/opensearch.yml
- ./internal_users.yml:/usr/share/opensearch/plugins/opensearch_security/securityconfig/internal_users.yml
- ./roles_mapping.yml:/usr/share/opensearch/plugins/opensearch_security/securityconfig/roles_mapping.yml
- ./tenants.yml:/usr/share/opensearch/plugins/opensearch_security/securityconfig/tenants.yml
- ./roles.yml:/usr/share/opensearch/plugins/opensearch_security/securityconfig/roles.yml
- ./action_groups.yml:/usr/share/opensearch/plugins/opensearch_security/securityconfig/action_groups.yml
- ./internal_users.yml:/usr/share/opensearch/plugins/opensearch-security/securityconfig/internal_users.yml
- ./roles_mapping.yml:/usr/share/opensearch/plugins/opensearch-security/securityconfig/roles_mapping.yml
- ./tenants.yml:/usr/share/opensearch/plugins/opensearch-security/securityconfig/tenants.yml
- ./roles.yml:/usr/share/opensearch/plugins/opensearch-security/securityconfig/roles.yml
- ./action_groups.yml:/usr/share/opensearch/plugins/opensearch-security/securityconfig/action_groups.yml
ports:
- 9200:9200
- 9600:9600 # required for Performance Analyzer
@ -78,11 +78,11 @@ services:
- ./admin.pem:/usr/share/opensearch/config/admin.pem
- ./admin-key.pem:/usr/share/opensearch/config/admin-key.pem
- ./custom-opensearch.yml:/usr/share/opensearch/config/opensearch.yml
- ./internal_users.yml:/usr/share/opensearch/plugins/opensearch_security/securityconfig/internal_users.yml
- ./roles_mapping.yml:/usr/share/opensearch/plugins/opensearch_security/securityconfig/roles_mapping.yml
- ./tenants.yml:/usr/share/opensearch/plugins/opensearch_security/securityconfig/tenants.yml
- ./roles.yml:/usr/share/opensearch/plugins/opensearch_security/securityconfig/roles.yml
- ./action_groups.yml:/usr/share/opensearch/plugins/opensearch_security/securityconfig/action_groups.yml
- ./internal_users.yml:/usr/share/opensearch/plugins/opensearch-security/securityconfig/internal_users.yml
- ./roles_mapping.yml:/usr/share/opensearch/plugins/opensearch-security/securityconfig/roles_mapping.yml
- ./tenants.yml:/usr/share/opensearch/plugins/opensearch-security/securityconfig/tenants.yml
- ./roles.yml:/usr/share/opensearch/plugins/opensearch-security/securityconfig/roles.yml
- ./action_groups.yml:/usr/share/opensearch/plugins/opensearch-security/securityconfig/action_groups.yml
networks:
- opensearch-net
opensearch-dashboards
@ -133,7 +133,7 @@ opensearch_security.audit.config.disabled_rest_categories: NONE
opensearch_security.audit.config.disabled_transport_categories: NONE
```
Use this same override process to specify new [authentication settings](../../security/configuration/configuration/) in `/usr/share/opensearch/plugins/opensearch_security/securityconfig/config.yml`, as well as new default [internal users, roles, mappings, action groups, and tenants](../../security/configuration/yaml/).
Use this same override process to specify new [authentication settings](../../security/configuration/configuration/) in `/usr/share/opensearch/plugins/opensearch-security/securityconfig/config.yml`, as well as new default [internal users, roles, mappings, action groups, and tenants](../../security/configuration/yaml/).
To start the cluster, run `docker-compose up`.

2
docs/install/plugins.md
View File

@ -72,7 +72,7 @@ Navigate to the OpenSearch home directory (most likely, it is `/usr/share/opense
sudo bin/opensearch-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloads/opensearch-plugins/opensearch-security/opensearch-security-{{site.opensearch_major_minor_version}}.1.0.zip
```
After installing the security plugin, you can run `sudo sh /usr/share/opensearch/plugins/opensearch_security/tools/install_demo_configuration.sh` to quickly get started with demo certificates. Otherwise, you must configure it manually and run [securityadmin.sh](../../security/configuration/security-admin/).
After installing the security plugin, you can run `sudo sh /usr/share/opensearch/plugins/opensearch-security/tools/install_demo_configuration.sh` to quickly get started with demo certificates. Otherwise, you must configure it manually and run [securityadmin.sh](../../security/configuration/security-admin/).
The security plugin has a corresponding [OpenSearch Dashboards plugin](../../opensearch-dashboards/plugins) that you probably want to install as well.

2
docs/opensearch/cluster.md
View File

@ -330,7 +330,7 @@ You can then use the [Index State Management (ISM)](../../ism/index/) plugin to
## Next steps
If you are using the security plugin, the previous request to `_cat/nodes?v` might have failed with an initialization error. To initialize the plugin, run `opensearch/plugins/opensearch_security/tools/securityadmin.sh`. A sample command that uses the demo certificates might look like this:
If you are using the security plugin, the previous request to `_cat/nodes?v` might have failed with an initialization error. To initialize the plugin, run `opensearch/plugins/opensearch-security/tools/securityadmin.sh`. A sample command that uses the demo certificates might look like this:
```bash
sudo ./securityadmin.sh -cd ../securityconfig/ -icl -nhnv -cacert /etc/opensearch/root-ca.pem -cert /etc/opensearch/kirk.pem -key /etc/opensearch/kirk-key.pem -h <private-ip>

2
docs/security/access-control/api.md
View File

@ -87,7 +87,7 @@ opensearch_dashboards_user:
Hidden resources are automatically reserved.
To add or remove these flags, you need to modify `plugins/opensearch_security/securityconfig/internal_users.yml` and run `plugins/opensearch_security/tools/securityadmin.sh`.
To add or remove these flags, you need to modify `plugins/opensearch-security/securityconfig/internal_users.yml` and run `plugins/opensearch-security/tools/securityadmin.sh`.
---

2
docs/security/access-control/multi-tenancy.md
View File

@ -23,7 +23,7 @@ http://<opensearch_dashboards_host>:5601/app/opensearch-dashboards?security_tena
## Configuration
Multi-tenancy is enabled by default, but you can disable it or change its settings using `plugins/opensearch_security/securityconfig/config.yml`:
Multi-tenancy is enabled by default, but you can disable it or change its settings using `plugins/opensearch-security/securityconfig/config.yml`:
```yml
config:

4
docs/security/configuration/configuration.md
View File

@ -10,7 +10,7 @@ nav_order: 2
One of the first steps to using the security plugin is to decide on an authentication backend, which handles [steps 2-3 of the authentication flow](../concepts/#authentication-flow). The plugin has an internal user database, but many people prefer to use an existing authentication backend, such as an LDAP server, or some combination of the two.
The main configuration file for authentication and authorization backends is `plugins/opensearch_security/securityconfig/config.yml`. It defines how the security plugin retrieves the user credentials, how it verifies these credentials, and how to fetch additional roles from backend systems (optional).
The main configuration file for authentication and authorization backends is `plugins/opensearch-security/securityconfig/config.yml`. It defines how the security plugin retrieves the user credentials, how it verifies these credentials, and how to fetch additional roles from backend systems (optional).
`config.yml` has three main parts:
@ -124,7 +124,7 @@ These are the possible values for `type`:
## Examples
The default `plugins/opensearch_security/securityconfig/config.yml` that ships with OpenSearch contains many configuration examples. Use these examples as a starting point, and customize them to your needs.
The default `plugins/opensearch-security/securityconfig/config.yml` that ships with OpenSearch contains many configuration examples. Use these examples as a starting point, and customize them to your needs.
## HTTP basic

2
docs/security/configuration/disable.md
View File

@ -14,7 +14,7 @@ You might want to temporarily disable the security plugin to make testing or int
opensearch_security.disabled: true
```
A more permanent option is to remove the security plugin entirely. Delete the `plugins/opensearch_security` folder on all nodes, and delete the `opensearch_security` configuration entries from `opensearch.yml`.
A more permanent option is to remove the security plugin entirely. Delete the `plugins/opensearch-security` folder on all nodes, and delete the `opensearch_security` configuration entries from `opensearch.yml`.
To perform these steps on the Docker image, see [Customize the Docker image](../../../install/docker/#customize-the-docker-image).

4
docs/security/configuration/ldap.md
View File

@ -58,7 +58,7 @@ We provide a fully functional example that can help you understand how to use an
## Connection settings
To enable LDAP authentication and authorization, add the following lines to `plugins/opensearch_security/securityconfig/config.yml`:
To enable LDAP authentication and authorization, add the following lines to `plugins/opensearch-security/securityconfig/config.yml`:
```yml
authc:
@ -250,7 +250,7 @@ Name | Description
## Use Active Directory and LDAP for authentication
To use Active Directory/LDAP for authentication, first configure a respective authentication domain in the `authc` section of `plugins/opensearch_security/securityconfig/config.yml`:
To use Active Directory/LDAP for authentication, first configure a respective authentication domain in the `authc` section of `plugins/opensearch-security/securityconfig/config.yml`:
```yml
authc:

2
docs/security/configuration/saml.md
View File

@ -40,7 +40,7 @@ We provide a fully functional example that can help you understand how to use SA
## Activating SAML
To use SAML for authentication, you need to configure a respective authentication domain in the `authc` section of `plugins/opensearch_security/securityconfig/config.yml`. Because SAML works solely on the HTTP layer, you do not need any `authentication_backend` and can set it to `noop`. Place all SAML-specific configuration options in this chapter in the `config` section of the SAML HTTP authenticator:
To use SAML for authentication, you need to configure a respective authentication domain in the `authc` section of `plugins/opensearch-security/securityconfig/config.yml`. Because SAML works solely on the HTTP layer, you do not need any `authentication_backend` and can set it to `noop`. Place all SAML-specific configuration options in this chapter in the `config` section of the SAML HTTP authenticator:
```yml
authc:

12
docs/security/configuration/security-admin.md
View File

@ -10,7 +10,7 @@ nav_order: 20
The security plugin stores its configuration---including users, roles, and permissions---in an index on the OpenSearch cluster (`.opensearch_security`). Storing these settings in an index lets you change settings without restarting the cluster and eliminates the need to edit configuration files on every single node.
After changing any of the configuration files in `plugins/opensearch_security/securityconfig`, however, you must run `plugins/opensearch_security/tools/securityadmin.sh` to load these new settings into the index. You must also run this script at least once to initialize the `.opensearch_security` index and configure your authentication and authorization methods.
After changing any of the configuration files in `plugins/opensearch-security/securityconfig`, however, you must run `plugins/opensearch-security/tools/securityadmin.sh` to load these new settings into the index. You must also run this script at least once to initialize the `.opensearch_security` index and configure your authentication and authorization methods.
After the `.opensearch_security` index is initialized, you can use OpenSearch Dashboards to manage your users, roles, and permissions.
@ -32,16 +32,16 @@ You can't use node certificates as admin certificates. The two must be separate.
The `securityadmin.sh` tool can be run from any machine that has access to the transport port of your OpenSearch cluster (the default is 9300). You can change the security plugin configuration without having to access your nodes through SSH.
Each node also includes the tool at `plugins/opensearch_security/tools/securityadmin.sh`. You might need to make the script executable before running it:
Each node also includes the tool at `plugins/opensearch-security/tools/securityadmin.sh`. You might need to make the script executable before running it:
```bash
chmod +x plugins/opensearch_security/tools/securityadmin.sh
chmod +x plugins/opensearch-security/tools/securityadmin.sh
```
To print all available command line options, run the script with no arguments:
```bash
./plugins/opensearch_security/tools/securityadmin.sh
./plugins/opensearch-security/tools/securityadmin.sh
```
To load configuration changes to the security plugin, you must provide your admin certificate to the tool:
@ -73,7 +73,7 @@ Name | Description
Apply configuration in `securityconfig` using PEM certificates:
```bash
/usr/share/opensearch/plugins/opensearch_security/tools/securityadmin.sh -cacert /etc/opensearch/root-ca.pem -cert /etc/opensearch/kirk.pem -key /etc/opensearch/kirk-key.pem -cd /usr/share/opensearch/plugins/opensearch_security/securityconfig/
/usr/share/opensearch/plugins/opensearch-security/tools/securityadmin.sh -cacert /etc/opensearch/root-ca.pem -cert /etc/opensearch/kirk.pem -key /etc/opensearch/kirk-key.pem -cd /usr/share/opensearch/plugins/opensearch-security/securityconfig/
```
Apply configuration from a single file (`config.yml`) using PEM certificates:
@ -86,7 +86,7 @@ Apply configuration in `securityconfig` with keystore and truststore files:
```bash
./securityadmin.sh \
-cd /usr/share/opensearch/plugins/opensearch_security/securityconfig/ \
-cd /usr/share/opensearch/plugins/opensearch-security/securityconfig/ \
-ks /path/to/keystore.jks \
-kspass changeit \
-ts /path/to/truststore.jks \

4
docs/security/configuration/tls.md
View File

@ -90,7 +90,7 @@ If your node certificates have an OID identifier in the SAN section, you can omi
## Configure admin certificates
Admin certificates are regular client certificates that have elevated rights to perform administrative tasks. You need an admin certificate to change the the security plugin configuration using `plugins/opensearch_security/tools/securityadmin.sh` or the REST API. Admin certificates are configured in `opensearch.yml` by stating their DN(s):
Admin certificates are regular client certificates that have elevated rights to perform administrative tasks. You need an admin certificate to change the the security plugin configuration using `plugins/opensearch-security/tools/securityadmin.sh` or the REST API. Admin certificates are configured in `opensearch.yml` by stating their DN(s):
```yml
opensearch_security.authcz.admin_dn:
@ -123,7 +123,7 @@ Name | Description
```
{% endcomment %}
1. Download the statically-linked JAR that includes OpenSSL, Apache Portable Runtime, and `netty-tcnative` for [RPM-based distributions](https://bintray.com/floragunncom/netty-tcnative/download_file?file_path=netty-tcnative-openssl-1.1.0j-static-2.0.20.Final-fedora-linux-x86_64.jar) or [other distributions](https://bintray.com/floragunncom/netty-tcnative/download_file?file_path=netty-tcnative-openssl-1.1.0j-static-2.0.20.Final-non-fedora-linux-x86_64.jar) and place it in `plugins/opensearch_security/` on every node.
1. Download the statically-linked JAR that includes OpenSSL, Apache Portable Runtime, and `netty-tcnative` for [RPM-based distributions](https://bintray.com/floragunncom/netty-tcnative/download_file?file_path=netty-tcnative-openssl-1.1.0j-static-2.0.20.Final-fedora-linux-x86_64.jar) or [other distributions](https://bintray.com/floragunncom/netty-tcnative/download_file?file_path=netty-tcnative-openssl-1.1.0j-static-2.0.20.Final-non-fedora-linux-x86_64.jar) and place it in `plugins/opensearch-security/` on every node.
## (Advanced) Hostname verification and DNS lookup

4
docs/security/configuration/yaml.md
View File

@ -8,7 +8,7 @@ nav_order: 3
# YAML files
Before running `securityadmin.sh` to load the settings into the `.opensearch_security` index, configure the YAML files in `plugins/opensearch_security/securityconfig`. You might want to back up these files so that you can reuse them on other clusters.
Before running `securityadmin.sh` to load the settings into the `.opensearch_security` index, configure the YAML files in `plugins/opensearch-security/securityconfig`. You might want to back up these files so that you can reuse them on other clusters.
The best use of these YAML files is to configure [reserved and hidden resources](../../access-control/api/#reserved-and-hidden-resources), such as the `admin` and `opensearch-dashboardsserver` users. You might find it easier to create other users, roles, mappings, action groups, and tenants using OpenSearch Dashboards or the REST API.
@ -17,7 +17,7 @@ The best use of these YAML files is to configure [reserved and hidden resources]
This file contains any initial users that you want to add to the security plugin's internal user database.
The file format requires a hashed password. To generate one, run `plugins/opensearch_security/tools/hash.sh -p <new-password>`. If you decide to keep any of the demo users, *change their passwords* and re-run [securityadmin.sh](../security-admin/) to apply the new passwords.
The file format requires a hashed password. To generate one, run `plugins/opensearch-security/tools/hash.sh -p <new-password>`. If you decide to keep any of the demo users, *change their passwords* and re-run [securityadmin.sh](../security-admin/) to apply the new passwords.
```yml
---

38
index.md
View File

@ -7,15 +7,33 @@ permalink: /
---
# OpenSearch documentation
Some Label
{: .label .label-yellow }
This site contains the technical documentation for [OpenSearch](https://opensearch.org/), the search, analytics, and visualization suite with advanced security, alerting, SQL support, automated index management, deep performance analysis, and more.
## Header 2
Stuff about Docker
{: .label .label-green }
This site contains the technical documentation for [OpenSearch](https://opensearch.org/), the search, analytics, and visualization suite with advanced security, alerting, SQL support, automated index management, deep performance analysis, and more.
[Get started](#docker-quickstart){: .btn .btn-blue }
[Get started](#docker-quickstart){: .btn .btn-purple }
Older versions of OpenSearch used arbitrary document *types*, but indices created in current versions of OpenSearch should use a single type named `_doc`. Store different document types in different indices.
{: .note }
Older versions of OpenSearch used arbitrary document *types*, but indices created in current versions of OpenSearch should use a single type named `_doc`.
{: .tip }
---
## Why use OpenSearch?
Some Label
{: .label .label-yellow }
OpenSearch is well-suited to the following use cases:
@ -62,6 +80,26 @@ Docker
To learn more, see [Install](docs/install/).
### Lots of deeper headers
[OpenSearch](https://opensearch.org) is supported by Amazon Web Services. All components are available under the [Apache License, Version 2.0](https://www.apache.org/licenses/LICENSE-2.0.html) on [GitHub](https://github.com/opensearch-project/).
The project welcomes GitHub issues, bug fixes, features, plugins, documentation---anything at all. To get involved, see [Contribute](https://opensearch.org/contribute.html) on the OpenSearch website.
#### Some file
```
[Contribute](https://opensearch.org/contribute.html) on the OpenSearch website.
```
##### An h5 for some odd reason
The project welcomes GitHub issues, bug fixes, features, plugins, documentation---anything at all. To get involved, see [Contribute](https://opensearch.org/contribute.html) on the OpenSearch website.
###### Hm this seems excessive
The project welcomes GitHub issues, bug fixes, features, plugins, documentation---anything at all. To get involved, see [Contribute](https://opensearch.org/contribute.html) on the OpenSearch website.
---