From 7d8131b2bc5d1d3a592f02481b6b3bcea69870c8 Mon Sep 17 00:00:00 2001 From: vincentlel <48972214+vincentlel@users.noreply.github.com> Date: Fri, 17 May 2024 12:05:42 -0500 Subject: [PATCH] Update Lambda --- Deploy/AWS Lambda Deployment.md | 4 ++-- Lifecycle_management.md | 8 ++++++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/Deploy/AWS Lambda Deployment.md b/Deploy/AWS Lambda Deployment.md index dd3fd53..a6f6711 100644 --- a/Deploy/AWS Lambda Deployment.md +++ b/Deploy/AWS Lambda Deployment.md @@ -22,7 +22,7 @@ Detailed process is available [here](https://docs.github.com/en/repositories/cre ## Ressources creation -Please refer to [here](./Provisioning.html) to create the ressources needed and use the option 1: Lambda. +Please refer to [here](../Provisioning.html#option-1-lambda) to create the ressources needed and use the option 1: Lambda. ## Github repo configuration Before configuring the deployment workflow, set the deployment variables in the GitHub repository secrets for actions. The workflow requires these variables in order to successfully push the image. @@ -36,7 +36,7 @@ Before configuring the deployment workflow, set the deployment variables in the | CONTAINER_NAME | Name of the container | | ECR_REPOSITORY | Container registry to publish your image | | EDS_API_URL | Base URL to access EarthData Store | -| EDS_AUTH_URL | Base authentication URL to access EarthData Store (information regarding this information [here](./Provisioning.html#earthdaily-authentication)) | +| EDS_AUTH_URL | Base authentication URL to access EarthData Store (information regarding this information [here](../Prerequisite.html) | | AWS_ACCESS_KEY_ID | S3 Access key to push datacube assets | | AWS_SECRET_ACCESS_KEY | S3 Secret Access key to push datacube assets | | DEPLOY_LAMBDA | Boolean value to enable Lambda deployment (deployed to Lambda if true) | diff --git a/Lifecycle_management.md b/Lifecycle_management.md index 96b1214..8ac3cbb 100644 --- a/Lifecycle_management.md +++ b/Lifecycle_management.md @@ -98,7 +98,9 @@ If you need to restore service leveraging a previous task definition, please go ## Backup and recovery For backup,please be sure to keep the various images of your service in the configured ECR repository. We recommend that you tag your images using the git SHA for the git commit that was used to build the image. -ECR repo will enable restoration of any version of your service. +ECR repo will enable restoration of any version of your service. + +You can also get source code and redeploy a service from the [main repository](https://github.com/earthdaily/reflectance-datacube-processor). ## Costs @@ -121,7 +123,9 @@ To manage running cost, you can define service limits leveraging [AWS service qu For any additional information, please contact our [support team](Api.Support@geosys.com) The following link might provide interesting information: -- ... +- [Earthdaily Github](https://github.com/earthdaily) provides additional content on data and analytics +- [Earthdaily constellation introduction](https://earthdaily.com/constellation/) +