Run Airseeker, signed APIs and Pushers on AWS with Polygon testnet #110
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 #97
Intention
I want to open this PR to show the CF templates and configurations used for visibility. It should not be merged.
Rationale
I've used the CloudFormation templates for Pushers and Signed APIs and and modified the e2e configurations so they can be used for AWS deployments. I chose to commit for reference, but they are quite easy to re-create from the official templates.
I had troubles building docker with linux platform on my macOS because of solidity (used to build TypeChain fixtures in the docker image) so I did a hack and reused the files that I have built locally.
I was running into user limits for VPC count and internet gateway count (5 is the limit) but I overcome it by deploying the services across multiple regions.
Airseeker image is pusher on my personal Docker Hub account here.
These are the contracts: