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

reverting security group ssl port change

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

4
.ebextensions/06-https-instance-securitygroup.config
View File

@@ -4,6 +4,6 @@ Resources:
Properties: Properties:
GroupId: { "Fn::GetAtt": ["AWSEBSecurityGroup", "GroupId"] } GroupId: { "Fn::GetAtt": ["AWSEBSecurityGroup", "GroupId"] }
IpProtocol: tcp IpProtocol: tcp
ToPort: 444 ToPort: 443
FromPort: 444 FromPort: 443
CidrIp: 0.0.0.0/0 CidrIp: 0.0.0.0/0

4
todo.md
View File

@@ -44,4 +44,8 @@ Deploy the ELB environment referencing the VPC + Subnets created with Cloudforma
Check the security group defined in 06 is created successfully. 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 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