The subnets are listed with their name, AZ and CIDR block: We will create private and public subnets to match load balancers and This will alsoĪllow us to enable multi-AZ for redundancy. That each subnet is associated to the VPC we just created, that it hasĪ distinct VPC and lastly that CIDR blocks don't overlap. Now let's create some subnets in different Availability Zones. If you're setting up the Elastic File System service then select the VPCĪnd from the Actions dropdown choose Edit DNS Hostnames and select Yes. We can use 10.0.0.0/16 for the CIDR block and leave tenancy asĭefault if we don't require dedicated hardware. Start by looking for the VPC option on the web console. Public subnets will require a Route Table keep an associated We can create subnets to have public and private instances in at least We'll start by creating a VPC for our GitLab cloud infrastructure, then We'll be using to configure our cloud infrastructure. or through the URI assigned to your team such asĪmazon Web Services console from where we can choose all of the services Login to your AWS account through the My Account dropdown on Services such as RDS for our database server and ElastiCache as a RedisĬluster to finally manage them within an auto scaling group with custom In this article we'll go through a basic HA setup where we'll start byĬonfiguring our Virtual Private Cloud and subnets to later integrate These services have a lot ofįlexibility and are able to adapt to most companies, best of all is theĪbility to automate both vertical and horizontal scaling. GitLab on AWS can leverage many of the services that are alreadyĬonfigurable with High Availability. Note: We do not recommend using the AWS Elastic File System (EFS), as it can result
0 kommentar(er)
