Skip to content
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.

Tear down the old event recorder service #16

Open
masih opened this issue Mar 3, 2023 · 2 comments
Open

Tear down the old event recorder service #16

masih opened this issue Mar 3, 2023 · 2 comments
Assignees

Comments

@masih
Copy link
Member

masih commented Mar 3, 2023

Tear down all resources created to run the old version now that the new one is up.

@kylehuntsman
Copy link
Contributor

kylehuntsman commented Mar 15, 2023

The CDK event recorder implementation for Saturn has been torn down, but there's still an instance up for Autoretrieve.

We currently have an instance of this implementation up for Saturn. I'm thinking we also need to spin up one for Autoretrieve so that we can tear down the old implementation. Saturn is going to produce so much traffic I feel it needs it's own event recorder instance so that it has it's own scalable resources.

@masih
Copy link
Member Author

masih commented Mar 16, 2023

I think autoretrieve should use the same instance with different credentials. The basic auth system I have set up allows you to create multiple username:password auth records. You can then differentiate records that way on the processing side assuming differentiation on who is sending events between the two is needed.

Re scale, i would not worry as the current setup is horizontally scalable unless there is evidence that suggests separate instances is a better fit.

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

No branches or pull requests

2 participants