Instructions to launch a test instance from a VM #348
Merged
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
phbnf
added
documentation
Draft
AlCutter
approved these changes
Dec 2, 2024
| This codelab helps you bring a test Trillian Tessera stack on AWS, | ||
| and to use it running a test personality server on an EC2 VM. | ||
| The Tessera test stack will be comprised of an Aurora RDS MySQL database | ||
| and a private S3 bubket. This codelab will also guide you to connect both |
|
|
||
| aws s3 ls --profile AdministratorAccess-<REDACTED> | ||
| ``` | ||
| 1. Set these environment variables according to the you chose when configuring |
| ``` | ||
| git clone https://github.com/transparency-dev/trillian-tessera | ||
| ``` | ||
| 1. Init terragrunt: |
There was a problem hiding this comment.
Does this need to be done in a particular directory?
| terragrunt apply --terragrunt-working-dir=deployment/live/aws/codelab/ | ||
| ``` | ||
| This brings up the Terraform infrastructure (S3 bucket + dynanoDB table | ||
| for locking) and the Trillian Tessera stack: an RDS Aurora instance, |
There was a problem hiding this comment.
Suggested change
| for locking) and the Trillian Tessera stack: an RDS Aurora instance, | |
| for terraform state locking only) and the Trillian Tessera stack: an RDS Aurora instance, |
| ``` | ||
| mkdir -p /home/ec2-user/tessera-keys | ||
| go run github.com/transparency-dev/serverless-log/cmd/generate_keys@80334bc9dc573e8f6c5b3694efad6358da50abd4 \ | ||
| --key_name=$LOG_NAME/test/conformance \ |
There was a problem hiding this comment.
What's in ${LOG_NAME} output from terragrunt?
Should it also contain ".../test/conformance"?
There was a problem hiding this comment.
This is the prefix that is used to name resources. It doesn't use slashes, but dashes. For the purpose of this example, it will be trillian-tessera-codelab-<ACCOUNT_ID>. I've aligned the name of the key with this.
| Log entries can be read directly from S3 without going through the server, | ||
| at `READ_URL=https://$LOG_BUCKET.s3.$AWS_REGION.amazonaws.com/` | ||
| 1. Head over to the [remainder of this codelab](https://github.com/transparency-dev/trillian-tessera/tree/main/cmd/conformance#codelab) | ||
| add leaves to the log. |
There was a problem hiding this comment.
Suggested change
| add leaves to the log. | |
| to add leaves to the log. |
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.
Towards #312 and #24
This PR adds a terraform module, terragrunt config and documentation to launch a Trillian Tessera test stack from an AWS EC2 VM, and to launch a conformance binary on that VM.
It brings minor modifications to the base /storage module, which will be also relied on for the CI environment.