AWS Signed API deployment without load balancer #218
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Siegrift
force-pushed
the
cf-without-elb
branch
from
53e6e42 to
f7209ee
Compare
|
We have a new CloudFormation template in https://github.com/api3dao/signed-api-deployments together with other CloudFormation files to create notification service, ALB and CloudFront, etc... It is arguable whether we actually need to have the CloudFormation template in this repo. It might be useful when someone else wants to deploy the Signed API. That said, for that use case we should provide the minimal (unopinionated) deployment setup (e.g. without Loki forwarding). But let's keep this as is for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #213
Rationale
Unfortunately, It's not possible to have a static IP for AWS Fargate. This means the IP changes after each restart/redeployment and each time we need to update the CDN routing. Also, the IP cannot be listed in CloudFormation output parameters and is only available in the currently deployed task configuration (ES2 -> Clusters -> Services -> Tasks). We can get the URL via AWS CLI though.
If we relax the requirement of static IP we can use the CloudFormation template in this PR. Each Signed API redeployment/restart would require immediate change in CDN distribution, incurring some delay while the update takes place.
During my research I haven't seen other "confirmed" solutions that work around the problem that the IP is bound to the task (not service). I saw threads like this or this which support using the LB for this purpose.