ReleaseEngineering/How To/Add New AWS Subnets: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 5: Line 5:
== Create new subnets ==
== Create new subnets ==
* Add subnets to https://github.com/mozilla/build-cloud-tools/blob/master/configs/subnets.yml
* Add subnets to https://github.com/mozilla/build-cloud-tools/blob/master/configs/subnets.yml
** run `scripts/aws_manage_subnets.py configs/subnets.yml` from aws-manager server  
** run `scripts/aws_manage_subnets.py configs/subnets.yml` from aws-manager server to create the subnets in VPC


Please check in AWS the new VPC subnets
Please check in AWS the new VPC subnets
Line 14: Line 14:
* Open bugs with netops to include new flows {{bug|1254144}}
* Open bugs with netops to include new flows {{bug|1254144}}
* Add the subnets to https://github.com/mozilla/build-cloud-tools/blob/master/configs/securitygroups.yml
* Add the subnets to https://github.com/mozilla/build-cloud-tools/blob/master/configs/securitygroups.yml
** run `scripts/aws_manage_subnets.py configs/subnets.yml` from aws-manager server to create the security groups


'''NOTE:''' After the firewall rules has been added by netops team and the new subnets in securitygroups.yml, the changes will be applied overnight.  Or you can ask dustin to run the command manually. (We don't have permissions to sudo to fwunit)
'''NOTE:''' After the firewall rules has been added by netops team and the new subnets in securitygroups.yml, the changes will be applied overnight.  Or you can ask dustin to run the command manually. (We don't have permissions to sudo to fwunit)
Confirmed users
108

edits

Navigation menu