Adds Reporting CLI documentation (#2170)
* add files back from lost local files Signed-off-by: Alice Williams <alicejw@amazon.com> * nest reporting CLI under main Reporting page Signed-off-by: Alice Williams <alicejw@amazon.com> * rough draft examples for AWS Lambda and Cron Signed-off-by: Alice Williams <alicejw@amazon.com> * better title for cron job report example Signed-off-by: Alice Williams <alicejw@amazon.com> * for more details from tech reviewer Signed-off-by: Alice Williams <alicejw@amazon.com> * for better cron job usage description Signed-off-by: Alice Williams <alicejw@amazon.com> * for more details Signed-off-by: Alice Williams <alicejw@amazon.com> * remove needs info markers and add links to events doc Signed-off-by: Alice Williams <alicejw@amazon.com> * more info Signed-off-by: Alice Williams <alicejw@amazon.com> * more details from demonstration Signed-off-by: Alice Williams <alicejw@amazon.com> * remove reporting directory to keep both parallel in left nav Signed-off-by: Alice Williams <alicejw@amazon.com> * small addition Signed-off-by: Alice Williams <alicejw@amazon.com> * for two configuration settings in the function Signed-off-by: Alice Williams <alicejw@amazon.com> * more details from eng meeting adding to the steps Signed-off-by: Alice Williams <alicejw@amazon.com> * more details from eng meeting adding to the steps Signed-off-by: Alice Williams <alicejw@amazon.com> * for more details Signed-off-by: Alice Williams <alicejw@amazon.com> * for additional steps to create and test the lambda function Signed-off-by: Alice Williams <alicejw@amazon.com> * for scheduling reports with lambda Signed-off-by: Alice Williams <alicejw@amazon.com> * merge redundant set of steps together Signed-off-by: Alice Williams <alicejw@amazon.com> * for tech review comments Signed-off-by: Alice Williams <alicejw@amazon.com> * to add download correct title and link Signed-off-by: Alice Williams <alicejw@amazon.com> * for reporting directory to nest new cli page Signed-off-by: Alice Williams <alicejw@amazon.com> * un-nest reporting directory Signed-off-by: Alice Williams <alicejw@amazon.com> * to remove reporting directory - will nest with other page in separate PR Signed-off-by: Alice Williams <alicejw@amazon.com> * tech review comments and some reorg Signed-off-by: Alice Williams <alicejw@amazon.com> * for tech review comments Signed-off-by: Alice Williams <alicejw@amazon.com> * to minor changes Signed-off-by: Alice Williams <alicejw@amazon.com> * more info about crontab sequence Signed-off-by: Alice Williams <alicejw@amazon.com> * cron updates Signed-off-by: Alice Williams <alicejw@amazon.com> * for cron syntax Signed-off-by: Alice Williams <alicejw@amazon.com> * small updates to lambda proc Signed-off-by: Alice Williams <alicejw@amazon.com> * for final writer checklist Signed-off-by: Alice Williams <alicejw@amazon.com> * cron link update Signed-off-by: Alice Williams <alicejw@amazon.com> * format fix Signed-off-by: Alice Williams <alicejw@amazon.com> * for doc review cron & lambda sections Signed-off-by: Alice Williams <alicejw@amazon.com> * for cron reference to man page Signed-off-by: Alice Williams <alicejw@amazon.com> * add internal link to cron ref Signed-off-by: Alice Williams <alicejw@amazon.com> * reorg single topic into 7 pages Signed-off-by: Alice Williams <alicejw@amazon.com> * minor update Signed-off-by: Alice Williams <alicejw@amazon.com> * link to set ses permissions Signed-off-by: Alice Williams <alicejw@amazon.com> * for tech review meeting updates Signed-off-by: Alice Williams <alicejw@amazon.com> * small update Signed-off-by: Alice Williams <alicejw@amazon.com> * npm download command name changed to remove opensearch prepended name Signed-off-by: Alice Williams <alicejw@amazon.com> * for new download via artifacts hub Signed-off-by: Alice Williams <alicejw@amazon.com> * for new download instructions Signed-off-by: Alice Williams <alicejw@amazon.com> * small fix signature file Signed-off-by: Alice Williams <alicejw@amazon.com> * typo Signed-off-by: Alice Williams <alicejw@amazon.com> * for cleaner image Signed-off-by: Alice Williams <alicejw@amazon.com> * remove image for push commands we won't use Signed-off-by: Alice Williams <alicejw@amazon.com> --------- Signed-off-by: Alice Williams <alicejw@amazon.com>
This commit is contained in:
Alice Williams
GitHub
parent
850ce482b9
commit
1dd560977b
|
|
@ -1,3 +1,4 @@
|
|||
build_gh_pages.sh
|
||||
_site
|
||||
.sass-cache
|
||||
.jekyll-metadata
|
||||
|
|
|
|||
|
|
@ -0,0 +1,49 @@
|
|||
---
|
||||
layout: default
|
||||
title: Creating and requesting a visualization report
|
||||
nav_order: 15
|
||||
parent: Creating reports with the Reporting CLI
|
||||
|
||||
---
|
||||
|
||||
# Creating and requesting a visualization report
|
||||
|
||||
First, you need to get the URL for the visualization that you want to download as an image file or PDF.
|
||||
|
||||
To generate a visualization report, you need to specify the Dashboards URL.
|
||||
|
||||
Open the visualization for which you want to generate a report, and select **Share > Permalinks > Generate link as Shapshot > Short URL > Copy link**, as shown in the following image.
|
||||
|
||||
|
||||
|
||||
You will need to add the URL with the `-u` argument when you request the report in the CLI.
|
||||
|
||||
#### Example: Requesting a PNG file
|
||||
|
||||
The following command requests a report in PNG format with basic authentication and sends the report to an email address using Amazon SES:
|
||||
|
||||
```
|
||||
opensearch-reporting-cli -u https://localhost:5601/app/dashboards#/view/7adfa750-4c81-11e8-b3d7-01146121b73d -a basic -c admin:Test@1234 -e ses -s <email address> -r <email address> -f png
|
||||
```
|
||||
|
||||
#### Example: Requesting a PDF file
|
||||
|
||||
The following command requests a PDF file and specifies the recipient's email address:
|
||||
|
||||
```
|
||||
opensearch-reporting-cli -u https://localhost:5601/app/dashboards#/view/7adfa750-4c81-11e8-b3d7-01146121b73d -a basic -c admin:Test@1234 -e ses -s <email address> -r <email address> -f pdf
|
||||
```
|
||||
|
||||
Upon success, the file will be sent to the specified email address. The following image shows an example PDF report.
|
||||
|
||||
|
||||
|
||||
#### Example: Requesting a CSV file
|
||||
|
||||
The following command generates a report that contains all table content in CSV format and sends the report to an email address using Amazon SES transport:
|
||||
|
||||
```
|
||||
opensearch-reporting-cli -u https://localhost:5601/app/dashboards#/view/7adfa750-4c81-11e8-b3d7-01146121b73d -f csv -a basic -c admin:Test@1234 -e ses -s <email address> -r <email address>
|
||||
```
|
||||
|
||||
Upon success, the email will be sent to the specified email address with the CSV file attached.
|
||||
|
|
@ -0,0 +1,35 @@
|
|||
---
|
||||
layout: default
|
||||
title: Scheduling reports with the cron utility
|
||||
nav_order: 20
|
||||
parent: Creating reports with the Reporting CLI
|
||||
|
||||
---
|
||||
|
||||
# Scheduling reports with the cron utility
|
||||
|
||||
You can use the cron command-line utility to initiate a report request with the Reporting CLI that runs periodically at any date or time interval. Follow the cron expression syntax to specify the date and time that precedes the command that you want to initiate.
|
||||
|
||||
To learn about the cron expression syntax, see [Cron expression reference]({{site.url}}{{site.baseurl}}/observing-your-data/alerting/cron/). To get help with cron, open the man page by running the following command:
|
||||
|
||||
```
|
||||
man cron
|
||||
```
|
||||
|
||||
### Prerequisites
|
||||
|
||||
- You need a machine with cron installed.
|
||||
- You need to install the Reporting CLI. See [Downloading and installing the Reporting CLI tool]({{site.url}}{{site.baseurl}}/dashboards/reporting-cli/rep-cli-install/)
|
||||
|
||||
## Specifying the report details
|
||||
|
||||
Open the crontab editor by running the following command:
|
||||
|
||||
```
|
||||
crontab -e
|
||||
```
|
||||
In the crontab editor, enter the report request. The following example shows a cron report that runs every day at 8:00 AM:
|
||||
|
||||
```
|
||||
0 8 * * * opensearch-reporting-cli -u https://playground.opensearch.org/app/dashboards#/view/084aed50-6f48-11ed-a3d5-1ddbf0afc873 -e ses -s <sender_email> -r <recipient_email>
|
||||
```
|
||||
|
|
@ -0,0 +1,102 @@
|
|||
---
|
||||
layout: default
|
||||
title: Using environment variables with the Reporting CLI
|
||||
nav_order: 35
|
||||
parent: Creating reports with the Reporting CLI
|
||||
|
||||
---
|
||||
|
||||
# Using environment variables with the Reporting CLI
|
||||
|
||||
Instead of explicitly providing values in the command line, you can save them as environment variables. The Reporting CLI reads environment variables from the current directory inside the project.
|
||||
|
||||
To set the environment variables in Linux, use the following command:
|
||||
|
||||
```
|
||||
export NAME=VALUE
|
||||
```
|
||||
|
||||
Each line should use the format `NAME=VALUE`.
|
||||
Each line that starts with a hashtag (#) is considered to be a comment.
|
||||
Quotation marks (") don't get any special handling.
|
||||
|
||||
Values from the command line argument have higher priority than the environment file. For example, if you add the file name as *test* in the *.env* file and also add the `--filename report` command option, the generated report's name will be *report*.
|
||||
{: .note }
|
||||
|
||||
#### Example: Requesting a PNG report with environment variables set
|
||||
|
||||
The following command requests a report with basic authentication in PNG format:
|
||||
|
||||
```
|
||||
opensearch-reporting-cli --url https://localhost:5601/app/dashboards#/view/7adfa750-4c81-11e8-b3d7-01146121b73d --format png --auth basic --credentials admin:admin
|
||||
```
|
||||
|
||||
Upon success, the report will download to the current directory.
|
||||
|
||||
## Using Amazon SES to request an email with a report attachment
|
||||
|
||||
To use Amazon SES as the email transport mechanism, the following prerequisites apply:
|
||||
|
||||
- The sender's email address must be verified by [Amazon SES](https://aws.amazon.com/ses/). The [AWS Command Line Interface (AWS CLI)](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html) is required to interact with Amazon SES. To configure basic settings used by the AWS CLI, see [Quick configuration with `aws configure`](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-config) in the AWS Command Line Interface user guide.
|
||||
- Amazon SES transport requires the `ses:SendRawEmail` role:
|
||||
|
||||
```json
|
||||
{
|
||||
"Statement": [
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": "ses:SendRawEmail",
|
||||
"Resource": "*"
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The following command requests an email with the report attached:
|
||||
|
||||
```
|
||||
opensearch-reporting-cli --url https://localhost:5601/app/dashboards#/view/7adfa750-4c81-11e8-b3d7-01146121b73d --transport ses --from <sender_email_id> --to <recipient_email_id>
|
||||
```
|
||||
|
||||
The following command uses default values for all other options. You can also set `OPENSEARCH_FROM`, `OPENSEARCH_TO`, and `OPENSEARCH_TRANSPORT` in your .env file and use the following command:
|
||||
|
||||
```
|
||||
opensearch-reporting-cli --url https://localhost:5601/app/dashboards#/view/7adfa750-4c81-11e8-b3d7-01146121b73d
|
||||
```
|
||||
|
||||
To modify the body of your email, you can edit the *index.hbs* file.
|
||||
|
||||
#### Example: Sending a report to an email address with SMTP
|
||||
|
||||
To send a report to an email address with SMTP transport, you need to set the options `OPENSEARCH_SMTP_HOST`, `OPENSEARCH_SMTP_PORT`, `OPENSEARCH_SMTP_USER`, `OPENSEARCH_SMTP_PASSWORD`, and `OPENSEARCH_SMTP_SECURE` in your .env file.
|
||||
|
||||
Once the transport options are set in your .env file, you can send the email using the following command:
|
||||
|
||||
```
|
||||
opensearch-reporting-cli --url https://localhost:5601/app/dashboards#/view/7adfa750-4c81-11e8-b3d7-01146121b73d --transport smtp --from <sender_email_id> --to <recipient_email_id>
|
||||
```
|
||||
|
||||
You can choose to set options using either your *.env* file or the command line argument values in any combination. Make sure to specify all required values to avoid errors.
|
||||
|
||||
To modify the body of your email, you can edit the *index.hbs* file.
|
||||
|
||||
## Limitations
|
||||
|
||||
The following limitations apply to environment variable usage with the Reporting CLI:
|
||||
|
||||
- Supported platforms are Windows x86, Windows x64, Mac Intel, Mac ARM, Linux x86, and Linux x64.
|
||||
|
||||
For any other platform, users can take advantage of the *CHROMIUM_PATH* environment variable to use custom Chromium.
|
||||
|
||||
- If a URL contains an exclamation point (!), then the history expansion needs to be disabled temporarily. Depending on which shell you are using, you can disable history expansion using one of the following commands:
|
||||
|
||||
* For bash, use `set +H`.
|
||||
* For zsh, use `setopt nobanghist`.
|
||||
|
||||
Alternatively, you can add a URL value as an environment variable using this format: `URL="<url-with-!>"`.
|
||||
|
||||
- All command options only accept lowercase letters.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
To resolve **MessageRejected: Email address is not verified**, see [Why am I getting a 400 "message rejected" error with the message "Email address is not verified" from Amazon SES?](https://aws.amazon.com/premiumsupport/knowledge-center/ses-554-400-message-rejected-error/) in the AWS Knowledge Center.
|
||||
|
|
@ -0,0 +1,36 @@
|
|||
---
|
||||
layout: default
|
||||
title: Creating reports with the Reporting CLI
|
||||
nav_order: 75
|
||||
has_children: true
|
||||
---
|
||||
|
||||
# Creating reports with the Reporting CLI
|
||||
|
||||
You can programmatically create dashboard reports in PDF or PNG format with the Reporting CLI without using OpenSearch Dashboards or the Reporting plugin. This allows you to create reports automatically within your email workflows.
|
||||
|
||||
If you want to download a CSV file, you need to have the Reporting plugin installed.
|
||||
{: .note }
|
||||
|
||||
For any dashboard view, you can request a report in PNG or PDF format to be sent to an email address. This can be useful for sending reports to multiple email recipients with an email alias. The only dashboard application that supports creating a CSV report is **Discover**.
|
||||
|
||||
With the Reporting CLI, you can specify options for your report in the command line. The report is sent to an email address as a PDF attachment by default. You can also request a PNG image or a CSV file with the `--formats` argument.
|
||||
|
||||
You can download the report to the directory in which you are running the Reporting CLI, or you can email the report by specifying Amazon Simple Email Service (Amazon SES) or SMTP for the email transport option.
|
||||
|
||||
You can connect to OpenSearch with any of the following authentication types:
|
||||
|
||||
- **Basic** – Basic HTTP authentication. Use `-a basic`.
|
||||
- **Cognito** – Authentication through Amazon Cognito. Use `-a cognito`.
|
||||
- **SAML** – Authentication between an identity provider and a service provider. Use `-a saml`. Okta provides the SAML third-party authentication.
|
||||
- **No auth** – No authentication. Use `-a none`. Authentication defaults to No auth if the `-a` flag is not specified.
|
||||
|
||||
To learn more about Amazon Cognito, see [What is Amazon Cognito?](https://docs.aws.amazon.com/cognito/latest/developerguide/what-is-amazon-cognito.html).
|
||||
|
||||
<!--
|
||||
### Bypass authentication option
|
||||
|
||||
The Reporting CLI tool allows you to integrate it into your own workflow or environment so that you can bypass authentication or potential security issues. For example, if you use the Reporting CLI tool within an AWS Lambda instance, no security issues would occur as long as you run the Reporting plugin in OpenSearch Dashboards. In this case, you would use "No auth" to bypass the authentication process. To specify "No Auth" use `--auth none` in your request. Lambda users should test to make sure they can bypass access to Dashboards without credentials using No Auth.
|
||||
|
||||
To get a list of all options, see [Reporting CLI options](#reporting-cli-options).
|
||||
-->
|
||||
|
|
@ -0,0 +1,35 @@
|
|||
---
|
||||
layout: default
|
||||
title: Downloading and installing the Reporting CLI tool
|
||||
nav_order: 10
|
||||
parent: Creating reports with the Reporting CLI
|
||||
|
||||
---
|
||||
|
||||
# Downloading and installing the Reporting CLI tool
|
||||
|
||||
You can download and install the Reporting CLI tool from either the npm software registry or the OpenSearch.org [Artifacts](https://opensearch.org/artifacts) hub. Refer to the following sections for instructions.
|
||||
|
||||
To learn more about the npm software registry, see the [npm](https://docs.npmjs.com/about-npm) documentation.
|
||||
|
||||
## Downloading and installing the Reporting CLI from npm
|
||||
|
||||
To download and install the Reporting CLI from npm, run the following command to initiate installation:
|
||||
|
||||
```
|
||||
npm i @opensearch-project/reporting-cli
|
||||
```
|
||||
|
||||
## Downloading and installing the Reporting CLI from OpenSearch.org
|
||||
|
||||
You can download the `opensearch-reporting-cli` tool from the OpenSearch.org [Artifacts](https://artifacts.opensearch.org/reporting-cli/opensearch-reporting-cli-1.0.0.tgz) hub.
|
||||
|
||||
Next, run the following command to install the .tar archive:
|
||||
|
||||
```
|
||||
npm install -g opensearch-reporting-cli-1.0.0.tgz
|
||||
```
|
||||
|
||||
Optionally, you can verify signatures by downloading the [Reporting CLI signature file](https://artifacts.opensearch.org/reporting-cli/opensearch-reporting-cli-1.0.0.tgz.sig).
|
||||
|
||||
To learn more about verifying signatures, see [How to verify signatures for downloadable artifacts](https://opensearch.org/verify-signatures.html).
|
||||
|
|
@ -0,0 +1,175 @@
|
|||
---
|
||||
layout: default
|
||||
title: Scheduling reports with AWS Lambda
|
||||
nav_order: 30
|
||||
parent: Creating reports with the Reporting CLI
|
||||
|
||||
---
|
||||
|
||||
# Scheduling reports with AWS Lambda
|
||||
|
||||
You can use AWS Lambda with the Reporting CLI tool to specify an AWS Lambda function to trigger the report generation.
|
||||
|
||||
This requires that you use an AMD64 system and Docker.
|
||||
|
||||
### Prerequisites
|
||||
|
||||
To use the Reporting CLI with AWS Lambda, you need to do the following preliminary steps.
|
||||
|
||||
- Get an AWS account. For instructions, see [Creating an AWS account](https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-creating.html) in the AWS Account Management reference guide.
|
||||
- Set up an Amazon Elastic Container Registry (ECR). For instructions, see [Getting started with Amazon ECR using the AWS Management Console](https://docs.aws.amazon.com/AmazonECR/latest/userguide/getting-started-console.html).
|
||||
|
||||
## Step 1: Create a container image with a Dockerfile
|
||||
|
||||
You need to assemble the container image by running a Dockerfile. When you run the Dockerfile, it downloads the OpenSearch artifact required to use the Reporting CLI. To learn more about Dockerfiles, see [Dockerfile reference](https://docs.docker.com/engine/reference/builder/).
|
||||
|
||||
Copy the following sample configurations into a Dockerfile:
|
||||
|
||||
```dockerfile
|
||||
# Define function directory
|
||||
ARG FUNCTION_DIR="/function"
|
||||
|
||||
# Base image of the docker container
|
||||
FROM node:lts-slim as build-image
|
||||
|
||||
# Include global arg in this stage of the build
|
||||
ARG FUNCTION_DIR
|
||||
|
||||
# AWS Lambda runtime dependencies
|
||||
RUN apt-get update && \
|
||||
apt-get install -y \
|
||||
g++ \
|
||||
make \
|
||||
unzip \
|
||||
libcurl4-openssl-dev \
|
||||
autoconf \
|
||||
automake \
|
||||
libtool \
|
||||
cmake \
|
||||
python3 \
|
||||
libkrb5-dev \
|
||||
curl
|
||||
|
||||
# Copy function code
|
||||
WORKDIR ${FUNCTION_DIR}
|
||||
RUN curl -LJO https://artifacts.opensearch.org/reporting-cli/opensearch-reporting-cli-1.0.0.tgz
|
||||
RUN tar -xzf opensearch-reporting-cli-1.0.0.tgz
|
||||
RUN mv package/* .
|
||||
RUN npm install && npm install aws-lambda-ric
|
||||
|
||||
# Build Stage 2: Copy Build Stage 1 files in to Stage 2. Install chrome, then remove chrome to keep the dependencies.
|
||||
FROM node:lts-slim
|
||||
# Include global arg in this stage of the build
|
||||
ARG FUNCTION_DIR
|
||||
# Set working directory to function root directory
|
||||
WORKDIR ${FUNCTION_DIR}
|
||||
# Copy in the build image dependencies
|
||||
COPY --from=build-image ${FUNCTION_DIR} ${FUNCTION_DIR}
|
||||
|
||||
# Install latest chrome dev package and fonts to support major char sets (Chinese, Japanese, Arabic, Hebrew, Thai and a few others)
|
||||
# Note: this installs the necessary libs to make the bundled version of Chromium that Puppeteer installs, work.
|
||||
RUN apt-get update \
|
||||
&& apt-get install -y wget gnupg \
|
||||
&& wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - \
|
||||
&& sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' \
|
||||
&& apt-get update \
|
||||
&& apt-get install -y google-chrome-stable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst fonts-freefont-ttf libxss1 \
|
||||
--no-install-recommends \
|
||||
&& apt-get remove -y google-chrome-stable \
|
||||
&& rm -rf /var/lib/apt/lists/*
|
||||
|
||||
ENTRYPOINT ["/usr/local/bin/npx", "aws-lambda-ric"]
|
||||
|
||||
ENV HOME="/tmp"
|
||||
CMD [ "/function/src/index.handler" ]
|
||||
|
||||
```
|
||||
|
||||
Next, run the following build command within the same directory that contains the Dockerfile:
|
||||
|
||||
```
|
||||
docker build -t opensearch-reporting-cli .
|
||||
```
|
||||
|
||||
## Step 2: Create a private repository with Amazon ECR
|
||||
|
||||
You need to follow the instructions to create an image repository, see [Getting started with Amazon ECR using the AWS Management Console](https://docs.aws.amazon.com/AmazonECR/latest/userguide/getting-started-console.html).
|
||||
|
||||
Give your repository the name `opensearch-reporting-cli`.
|
||||
|
||||
In addition to the Amazon ECR instructions, you need to make several adjustments for the Reporting CLI to function properly as described in the following steps in this procedure.
|
||||
|
||||
## Step 3: Push the image to the private repository
|
||||
|
||||
You need to get several commands from the AWS ECR Console to run within the Dockerfile directory.
|
||||
|
||||
1. After you create your repository, select it from **Private repositories**.
|
||||
1. Choose **view push commands**.
|
||||
1. Copy and run each command shown in **Push commands for opensearch-reporting-cli** sequentially in the Dockerfile directory.
|
||||
|
||||
For more details about Docker push commands, see [Pushing a Docker image](https://docs.aws.amazon.com/AmazonECR/latest/userguide/docker-push-ecr-image.html) in the Amazon ECR user guide.
|
||||
|
||||
## Step 4: Create a Lambda function with the container image
|
||||
|
||||
Now that you have a container image created for the Reporting CLI, you need to create a function defined as the container image.
|
||||
|
||||
1. Open the AWS Lambda console and choose [Functions](https://us-west-2.console.aws.amazon.com/lambda/home?region=us-west-2#/functions).
|
||||
1. Choose **Create function**, then choose **Container image** and fill in a name for the function.
|
||||
1. In **Container image URI**, choose **Browse images** and select `opensearch-reporting-cli` for the image repository.
|
||||
1. In **Images** select the image, and choose **Select image**.
|
||||
1. In **Architecture**, choose **x86_64**.
|
||||
1. Choose **Create function**.
|
||||
1. Go to **Lambda** > **functions** and choose the function you created.
|
||||
1. Choose **Configuration > General configuration > Edit timeout** and set the timeout in lambda to 5 minutes to allow the Reporting CLI to generate the report.
|
||||
1. Change the **Ephemeral storage** setting to at least 1024MB. The default setting is not a sufficient storage amount to support report generation.
|
||||
|
||||
1. Next, test the function either by providing values JSON format or by providing AWS Lambda environment variables.
|
||||
|
||||
- If the function contains fixed values, such as email address you do not need a JSON file. You can specify an environment variable in AWS Lambda.
|
||||
- If the function takes a variable key-value pair, then you need to specify the values in the JSON with the same naming convention as command options, for example the `--credentials` option requires the username and password.
|
||||
{: .note }
|
||||
|
||||
The following example shows fixed values provided for the sender and recipient email addresses:
|
||||
|
||||
```json
|
||||
{
|
||||
"url": "https://playground.opensearch.org/app/dashboards#/view/084aed50-6f48-11ed-a3d5-1ddbf0afc873",
|
||||
"transport": "ses",
|
||||
"from": "sender@amazon.com",
|
||||
"to": "recipient@amazon.com",
|
||||
"subject": "Test lambda docker image"
|
||||
}
|
||||
```
|
||||
|
||||
To learn more about AWS Lambda functions, see [Deploying Lambda functions as container images](https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-images.html) in the AWS Lambda documentation.
|
||||
## Step 5: Add the trigger to start the AWS Lambda function
|
||||
|
||||
Set the trigger to start running the report. AWS Lambda can use any AWS service as a trigger, such as SNS, S3, or an AWS CloudWatch EventBridge.
|
||||
|
||||
1. In the **Triggers** section, choose **Add trigger**.
|
||||
1. Select a trigger from the list. For example, you can set an AWS CloudWatch Event. To learn more about Amazon ECR events you can schedule, see [Sample events from Amazon ECR](https://docs.aws.amazon.com/AmazonECR/latest/userguide/ecr-eventbridge.html#ecr-eventbridge-bus).
|
||||
1. Choose **Test** to initiate the function.
|
||||
|
||||
## (Optional) Step 6: Add the role permission for Amazon SES
|
||||
|
||||
If you want to use Amazon SES for the email transport, you need to set up permissions.
|
||||
|
||||
1. Select **Configuration** and choose **Execution role**.
|
||||
1. In **Summary**, choose **Permissions**.
|
||||
1. Select **{}JSON** to open the JSON policy editor.
|
||||
1. Add the permissions for the Amazon SES resource that you want to use.
|
||||
|
||||
The following example provides the resource ARN for the send email action:
|
||||
|
||||
```json
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": [
|
||||
"ses:SendEmail",
|
||||
"ses:SendRawEmail"
|
||||
],
|
||||
"Resource": "arn:aws:ses:us-west-2:555555511111:identity/username@amazon.com"
|
||||
}
|
||||
```
|
||||
|
||||
To learn more about setting role permissions, see [Permissions](https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-images.html#gettingstarted-images-permissions) in the AWS Lambda user guide.
|
||||
|
|
@ -0,0 +1,41 @@
|
|||
---
|
||||
layout: default
|
||||
title: Reporting CLI options
|
||||
nav_order: 30
|
||||
parent: Creating reports with the Reporting CLI
|
||||
|
||||
---
|
||||
|
||||
# Reporting CLI options
|
||||
|
||||
You can use any of the following arguments with the `opensearch-reporting-cli` tool.
|
||||
|
||||
| Argument | Description | Acceptable values and usage | Environment variable
|
||||
:--------------------- | :--- | :--- |
|
||||
`-u`, `--url` | The URL for the visualization. | Obtain from OpenSearch Dashboards > Visualize > Share > Permalinks > Copy link. | OPENSEARCH_URL
|
||||
`-a`, `--auth` | The authentication type for the report. | You can specify either Basic `basic`, Cognito `cognito`, SAML `saml`, or No Auth `none`. If no value is specified, the Reporting CLI tool defaults to no authentication, type `none`. Basic, Cognito, and SAML require credentials with the `-c` flag. | N/A
|
||||
`-c`, `--credentials` | The OpenSearch login credentials. | Enter your username and password separated by a colon. For example, username:password. Required for Basic, Cognito, and SAML authentication types. | OPENSEARCH_USERNAME and OPENSEARCH_PASSWORD
|
||||
`-t`, `--tenant` | The tenants in OpenSearch Dashboards. | The default tenant is private.| N/A
|
||||
`-f`, `--format` | The file format for the report. | Can be either `pdf`, `png`, or `csv`. The default is `pdf`.| N/A
|
||||
`-w`, `--width` | The window width in pixels for the report. | Default is `1680`.| N/A
|
||||
`-l`, `--height` | The minimum window height in pixels for the report. | Default is `600`. | N/A
|
||||
`-n`, `--filename` | The file name of the report. | Default is `reporting`. | opensearch-report-YYY-MM-DDTHH-mm-ss.sssZ
|
||||
`-e`, `--transport` | The transport mechanism for sending the email. | For Amazon SES, specify `ses`. Amazon SES requires an AWS configuration on your system to store the credentials. For SMTP, use `smtp` and also specify the login credentials with `--smtpusername` and `--smtppassword`. | OPENSEARCH_TRANSPORT
|
||||
`-s`, `--from` | The email address of the sender. | For example, `user@amazon.com`. | OPENSEARCH_FROM
|
||||
`-r`, `--to` | The email address of the recipient. | For example, `user@amazon.com`. | OPENSEARCH_TO
|
||||
`--smtphost` | The hostname of the SMTP server. | For example, `SMTP_HOST`. | OPENSEARCH_SMTP_HOST
|
||||
`--smtpport` | The port for the SMTP connection. | For example, `SMTP_PORT`. | OPENSEARCH_SMTP_PORT
|
||||
`--smtpsecure` | Specifies to use TLS when connecting to the server. | For example, `SMTP_SECURE`. | OPENSEARCH_SMTP_SECURE
|
||||
`--smtpusername` | The SMTP username.| For example, `SMTP_USERNAME`. | OPENSEARCH_SMTP_USERNAME
|
||||
`--smtppassword` | The SMTP password.| For example, `SMTP_PASSWORD`. | OPENSEARCH_SMTP_PASSWORD
|
||||
`--subject` | The email subject text encased in quotes. | Can be any string. The default is "This is an email containing your dashboard report". | OPENSEARCH_EMAIL_SUBJECT
|
||||
`--note` | The email body, either a string or a path to a text file. | The default note is "Hi,\\nHere is the latest report!" | OPENSEARCH_EMAIL_NOTE
|
||||
`-h`, `--help` | Specifies to display the list of optional arguments from the command line. | N/A
|
||||
|
||||
## Getting help
|
||||
|
||||
To get a list of all available CLI arguments, run the following command:
|
||||
|
||||
```
|
||||
$ opensearch-reporting-cli -h
|
||||
```
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 342 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
Loading…
Reference in New Issue