Set up Virtual Private Cloud (VPC) and a Subnet
Posted: Sat Jan 25, 2025 9:14 am
Probably the best approach is to use AWS Lambda, which are private by default, but this service will not be as configurable as Elastic Beanstalk to be able to run your own backend configuration, so we will keep the services within a private cloud (a “VPC” in Amazon terminology) and provide access to this service only through the API Gateway.
This guide aims to explain the basics of setting up a private effective pakistan mobile numbers list backend/service using an Elastic Beanstalk (EBS) residing within a VPC. EBS methods will be available through API Gateway using a VPC Link.
First you will need to set up a virtual private cloud (VPC). This setup is complex and requires networking knowledge. I share with you the following video which explains in great detail the creation of your own public and private network, default security group configuration, and the configuration of a router and NAT to provide access to your new VPC.
Please accept cookie consent
2. Set up Elastic Beanstalk privately
The second step is to set up an Elastic Beanstalk (EBS) application. One of the advantages of using EBS over pure EC2 instances is that EBS comes with many preconfigured features, such as auto-scaling and rolling updates.
We'll start by creating an EBS application by creating a new environment. The environment is actually where all the configuration takes place. Check out the Elastic Beanstalk (EBS) documentation for more information on how EBS actually works.
2.1. Setting up the environment
Let's see step by step how to configure a new environment:
Choose the “Web server environment”.
Name your environment and assign a domain name
Choose the platform that suits your needs, Go, Java, Node.js, etc.
Choose which application you want to deploy. You can use the “Sample application” or you can also upload your application “Upload your code”.
Configure the deployment type, in this case you will have to choose the “High availability” option. This will give us the option later to configure a network load balancer, very important that it is a network load balancer, since what we want is for the API Gateway to access our APP deployed in EBS via the network.
2.2. Configuring access to the service
Configuring service access will allow you to access the configuration of the permissions and users that will generate the infrastructure, that is, the servers with EC2 and the network load balancer as we mentioned above.
To configure access to the service you must:
Next, you will need to specify the IAMs associated with the EBS server deployment. To do this, you will need to have the “aws-elasticbeanstalk-service-role” in place. To configure the aws-elasticbeanstalk-ec2-role for Elastic Beanstalk, you can follow these steps:
Navigate to IAM: Go to the IAM (Identity and Managed Access) service.
Select Roles: In the left navigation panel.
Find the role: In the list of roles, find or create the aws-elasticbeanstalk-ec2-role role.
This guide aims to explain the basics of setting up a private effective pakistan mobile numbers list backend/service using an Elastic Beanstalk (EBS) residing within a VPC. EBS methods will be available through API Gateway using a VPC Link.
First you will need to set up a virtual private cloud (VPC). This setup is complex and requires networking knowledge. I share with you the following video which explains in great detail the creation of your own public and private network, default security group configuration, and the configuration of a router and NAT to provide access to your new VPC.
Please accept cookie consent
2. Set up Elastic Beanstalk privately
The second step is to set up an Elastic Beanstalk (EBS) application. One of the advantages of using EBS over pure EC2 instances is that EBS comes with many preconfigured features, such as auto-scaling and rolling updates.
We'll start by creating an EBS application by creating a new environment. The environment is actually where all the configuration takes place. Check out the Elastic Beanstalk (EBS) documentation for more information on how EBS actually works.
2.1. Setting up the environment
Let's see step by step how to configure a new environment:
Choose the “Web server environment”.
Name your environment and assign a domain name
Choose the platform that suits your needs, Go, Java, Node.js, etc.
Choose which application you want to deploy. You can use the “Sample application” or you can also upload your application “Upload your code”.
Configure the deployment type, in this case you will have to choose the “High availability” option. This will give us the option later to configure a network load balancer, very important that it is a network load balancer, since what we want is for the API Gateway to access our APP deployed in EBS via the network.
2.2. Configuring access to the service
Configuring service access will allow you to access the configuration of the permissions and users that will generate the infrastructure, that is, the servers with EC2 and the network load balancer as we mentioned above.
To configure access to the service you must:
Next, you will need to specify the IAMs associated with the EBS server deployment. To do this, you will need to have the “aws-elasticbeanstalk-service-role” in place. To configure the aws-elasticbeanstalk-ec2-role for Elastic Beanstalk, you can follow these steps:
Navigate to IAM: Go to the IAM (Identity and Managed Access) service.
Select Roles: In the left navigation panel.
Find the role: In the list of roles, find or create the aws-elasticbeanstalk-ec2-role role.