web-development/strapi-elb
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

adding custom VPC

Browse Source
This commit is contained in:
dtomlinson
2020-04-29 02:57:39 +01:00
parent dd90c2dcc4
commit 01cfc11c4a
2 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
.ebextensions/07-custom-vpc.config Normal file
View File

@@ -0,0 +1,5 @@
option_settings:
aws:ec2:vpc:
VPCId: "vpc-003597eb63a0a3efe"
Subnets: "subnet-02cd8f7981ddfe345,subnet-02d9e1338e8d92d09,subnet-0e07d4d35394db524"

8
todo.md
View File

@@ -42,10 +42,6 @@ Decouple an exisitng RDS instance from ELB to RDS: <https://aws.amazon.com/premi
Deploy the ELB environment referencing the VPC + Subnets created with Cloudformation. Use https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/vpc-rds.html as a reference.
Check the security group defined in 06 is created successfully.
When you reference a resource in a config file with resources, if it exists in ELB it will apply that to the existing ELB resource. You can overwrite/append values this way.
For example setting `sslSecurityGroupIngress:` in a config resources will edit the security group for ssl ingress for your ec2.
Recreate env with database, check the DB subnets - are they the same as the EC2 subnets? If so we can reference them in https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-ec2vpc with ELBSubnets
Can we use cloudformation functions (imports) in .config files under option_settings? (reference a VPC that already exists?)