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

Figure out how to automate shared services API GW #511

Open
galenatjpl opened this issue Nov 12, 2024 · 0 comments
Open

Figure out how to automate shared services API GW #511

galenatjpl opened this issue Nov 12, 2024 · 0 comments
Labels

Comments

@galenatjpl
Copy link
Collaborator

galenatjpl commented Nov 12, 2024

Figure out how to automate the update of the shared services API GW, upon deployment of a new project/venue.
A new APIGW resource needs to be created, so that API calls will properly get routed to the venue API GW.
The SS APIGW, should reference the URL of the venue APIGW.
Potentially, we can leverage a similar mechanism that the SS HTTPD update process uses, which is to update a configuration file in a SS S3 bucket.

Make sure to think about security issues here.

IDEAS:
-- store/update venue SSM params that specify the proj/venue API Gateway resource config
-- cross-account lambda invoke?

@galenatjpl galenatjpl converted this from a draft issue Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

1 participant