Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove AWS lambda mentions from README and docs #6997

Merged
merged 1 commit into from
Jun 6, 2023
Merged

Remove AWS lambda mentions from README and docs #6997

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 0 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,9 +166,6 @@ Once this is done you can run your image with `docker run -p 19120:19120 quay.io
environment variables, if any. Environment variables names must follow MicroProfile Config's [mapping
rules](https://github.com/eclipse/microprofile-config/blob/master/spec/src/main/asciidoc/configsources.asciidoc#environment-variables-mapping-rules).

### AWS Lambda
You can also deploy to AWS lambda function by following the steps in `servers/lambda/README.md`

## Nessie related repositories

* [Nessie Demos](https://github.com/projectnessie/nessie-demos): Demos for Nessie
Expand Down
5 changes: 2 additions & 3 deletions site/docs/features/security.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,16 +7,15 @@ Nessie currently supports 3 security modes:

* No Security
* Open Id Connect
* AWS IAM Roles (limited to API calls, UI not supported)
* AWS IAM Roles (supported only on the Nessie client side)


## Authorization

Nessie authorization can only be done externally at the moment. However, because of
the way that the REST APIs are defined, many operations can be controlled via a layer
7 firewall so that users and systems can be controlled depending on what read/write
and types of operations should be allowed. This works especially well with Nessie run
as an AWS Lambda using [API gateway policies](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-iam-policy-examples.html).
and types of operations should be allowed.

## Metadata authorization
Nessie supports authorization on metadata. Details are described in the [Metadata Authorization](metadata_authorization.md) section.
2 changes: 1 addition & 1 deletion site/docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ template: "home.html"
* Cross-table transactions and visibility
* Open data lake approach, supporting Hive, Spark, Dremio, AWS Athena, etc.
* Works with Apache Iceberg and Delta Lake tables
* Run as a docker image, AWS Lambda or fork it on GitHub
* Run as a docker image or fork it on GitHub

Get in touch via our [Google Group](https://groups.google.com/g/projectnessie) and our
[Zulip Chat](https://project-nessie.zulipchat.com/) and follow us on
Expand Down