Select it from the table, and then under the Actions dropdown list chooseĬhoose gitlab-vpc from the list and hit Attach. Select Create internet gateway, give it the name gitlab-gateway and Select Internet Gateways from the left menu. Now, still on the same dashboard, go to Internet Gateways and Select each public subnet in turn, select Actions, and select Modify auto-assign IP settings.Once all the subnets are created, enable Auto-assign IPv4 for the two public subnets: Give it a descriptive name tag based on the IP,įor example gitlab-public-10.0.0.0, select the VPC we created previously, select an availability zone (we use us-west-2a),Īnd at the IPv4 CIDR block let's give it a 24 subnet 10.0.0.0/24:įollow the same steps to create all subnets: Name tag We create private and public subnets to match load balancers and This alsoĪllows us to enable multi AZ for redundancy. That each subnet is associated to the VPC we just created and Now, let's create some subnets in different Availability Zones. Select the VPC, select Actions, select Edit DNS resolution, and enable DNS resolution. If you don't require dedicated hardware, you can leave ![]() Select Your VPCs from the left menu and then select Create VPC.Īt the "Name tag" enter gitlab-vpc and at the "IPv4 CIDR block" enterġ0.0.0.0/16. We now create a VPC, a virtual networking environment that you control: Public subnets require a Route Table keep and an associated We can create subnets to have public and private instances in at least We start by creating a VPC for our GitLab cloud infrastructure, then ![]() We use this role when we create a launch configuration later on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |