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.

Sign up for GitHub

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

Increase API size #135

Merged
merged 2 commits into from
Oct 19, 2023
Merged

Increase API size #135

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a779d7b
Fix a typo
slifty Oct 12, 2023
fd7d058
Increase api image size
slifty Oct 12, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ This is the general workflow for provisioning and deploying a new images. Reason
6. Click "Queue plan" in the top right corner, and confirm once the workflow reaches the "Plan Finished" state.
7. Repeat steps 5-6 for each workspace once the new configuration has been rolled out across the entire fleet.

## Infrastructure Modification Worflow
## Infrastructure Modification Workflow

The `instances` directory contains the Terraform configuration. You would want to make changes to Terraform to modify the infrastructure layout or hardware (e.g. new autoscaling groups, larger or more EC2 instances, etc). Our Terraform configuration currently manages all Permanent AMIs, EC2 instances, Autoscaling Groups, Launch Configurations, and Target Groups for the Load Balacers. Terraform does NOT manage: the Load Balancer itself, S3 buckets, SQS queues, VPCs, Security Groups, subnets, IAM, etc. To make changes to the infrastructure, push your changes to a branch, open a PR, and get a code review. Once the PR is merged, the change (depending on the directory they are in), should queue a `terraform plan` job our [Terraform Cloud organization](https://app.terraform.io/app/PermanentOrg/workspaces). Review the plan, and approve the changes if they look good. Terraform will then roll-out the new infrastructure.

Expand Down
2 changes: 1 addition & 1 deletion instances/dev/main.tf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ variable "perm_env" {

resource "aws_instance" "api" {
ami = module.perm_env_data.backend_ami
instance_type = "m4.large"
instance_type = "c7g.xlarge"
vpc_security_group_ids = [module.perm_env_data.security_group]
monitoring = true
private_ip = "172.31.0.80"
Expand Down
2 changes: 1 addition & 1 deletion instances/production/main.tf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ variable "perm_env" {

resource "aws_instance" "api" {
ami = module.perm_env_data.backend_ami
instance_type = "m4.large"
instance_type = "c7g.xlarge"
vpc_security_group_ids = [module.perm_env_data.security_group]
monitoring = true
subnet_id = module.perm_env_data.subnet
Expand Down
2 changes: 1 addition & 1 deletion instances/staging/main.tf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ variable "perm_env" {

resource "aws_instance" "api" {
ami = module.perm_env_data.backend_ami
instance_type = "m4.large"
instance_type = "c7g.xlarge"
vpc_security_group_ids = [module.perm_env_data.security_group]
monitoring = true
subnet_id = module.perm_env_data.subnet
Expand Down