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.

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

Use SM2A endpoint in Eventbridge Lambda function #248

Open
1 task
smohiudd opened this issue Oct 21, 2024 · 1 comment
Open
1 task

Use SM2A endpoint in Eventbridge Lambda function #248

smohiudd opened this issue Oct 21, 2024 · 1 comment
Assignees

Comments

@smohiudd
Copy link
Contributor

smohiudd commented Oct 21, 2024

Description

The Eventbridge Lambda that triggers EIS vector ingests uses MWAA authorization and endpoints. To support the eventual cutover to SM2A, the function must be modified to support SM2A endpoints.

Acceptance Criteria

  • Eventbridge lambda uses SM2A endpoints and is tested with dev features api and dev SM2A
@anayeaye
Copy link
Contributor

@amarouane-ABDELHAK I will set up these prefixes in VEDA-Prod for testing. In the event bridge lambda can you change these prefixes for testing? I still plan to look more closely at the fire detection ingest events that are successfully being processed but I think these are the only changes we will need in the dev lambda

Around line 25
bucket_key_prefix = "EIS/FEDSoutput/Snapshot/" --> bucket_key_prefix = "EIS/FEDSoutput/Snapshot_COPY/"

Around line 28
bucket_key_prefix = "EIS/FEDSoutput/LFArchive/" --> bucket_key_prefix = "EIS/FEDSoutput/LFArchive_COPY/"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants