Managing networks within Laravel Vapor.
network
directive to your vapor.yml
file; however, sometimes you may want to manually specify that a Vapor environment should be placed within a given network. This may be the case when you are accessing private AWS resources, such as ElasticSearch, that are not created through Vapor. To place an environment within a network, add the network
directive to your vapor.yml
configuration file:
jump
CLI command:
ec2-user
user and the private SSH key.
vapor.yml
file, Vapor will automatically ensure that the network associated with that database / cache contains a NAT Gateway. If it doesn’t, Vapor will automatically begin provisioning one. Unfortunately, AWS bills for NAT Gateways by the hour, resulting in a monthly fee of about $32 / month.
To totally avoid using NAT Gateways, you can use publicly accessible RDS databases (Vapor automatically assigns a long, random password) and a DynamoDB cache table, which Vapor automatically creates for each of your projects. You may also manually add or remove NAT Gateways from your networks using the Vapor UI or using the network:nat
and network:delete-nat
CLI commands.
balancer
CLI command. When using the CLI command:
balancer
key to the environment’s configuration in your vapor.yml
file and deploy your application. The value of this key should be the name of the load balancer.
us-east-1
region, regardless of the region of your project. When your application is using API Gateway, AWS will automatically replicate your certificate to all regions behind the scenes.However, when using an Application Load Balancer to route traffic to your application, you will need to create a certificate in the region that the project is actually deployed to.balancer:delete
CLI command: