feat(vpc): add first use case #4140
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RoRoJ
added
type: new content
Co-authored-by: ldecarvalho-doc <[email protected]>
RoRoJ
commented
Dec 20, 2024
nerda-codes
reviewed
Dec 23, 2024
|
|
||
| The architecture diagram below shows the infrastructure for this use-case. | ||
|
|
||
| <Lightbox src="scaleway-vpc-infra-1.webp" size="large" alt="An architecture diagram shows how a Load Balancer inside a Scaleway VPC is attached to a Private Network. Also attached to the Private Network are three Instances (connected to Block Storage), a Managed Database, and a Public Gateway. Users access resources via a domain name which a Domains and DNS entry points to the Load Balancer's public flexible IP address. The Load Balancer distributes requests to the three Instances, which do not have public IP addresses. Instances can privately retrieve and store data in the Managed Database and Block Storage. The Public Gateway also has a flexible IP address, which allows admins to connect to resources in the Private Network via SSH bastion. The gateway's public flexible IP also allows connections to Scaleway resources outside the VPC, e.g. Object Storage, Transactional Email, Nats, Queues, Topics and Events, Serverless products, and Secret Manager." /> |
There was a problem hiding this comment.
"Users access resources via a domain name which a Domains and DNS entry points to the Load Balancer's public flexible IP address." I feel like something is missing between "which" and "a Domains and DNS"
|
|
||
| ### Cost control | ||
|
|
||
| Creating Scaleway resources without their own public IP addresses saves money, as these addresses are billed resource, while the creation, configuration and assignment of IP addresses from a Private Network is free of charge. |
There was a problem hiding this comment.
Suggested change
| Creating Scaleway resources without their own public IP addresses saves money, as these addresses are billed resource, while the creation, configuration and assignment of IP addresses from a Private Network is free of charge. | |
| Creating Scaleway resources without their own public IP addresses saves money, as these addresses are billed resources, while the creation, configuration and assignment of IP addresses from a Private Network is free of charge. |
| Follow the steps below to create this infrastructure using the [Scaleway console](https://console.scaleway.com/organization): | ||
|
|
||
| 1. [Create a VPC](/network/vpc/how-to/create-vpc/) (or use the [default VPC](/network/vpc/how-to/create-vpc/#how-to-identify-your-default-vpcs) pre-created for each Scaleway Project in the appropriate [region](/network/vpc/concepts/#region-and-availability-zone)). | ||
| 2. [Create a Private Network](/network/vpc/how-to/create-private-network/) inside the VPC. You can either let Scaleway create the network with an auto-generate subnet, which will provide the private IP addresses for attached resources, or specify a self-defined subnet. |
There was a problem hiding this comment.
Suggested change
| 2. [Create a Private Network](/network/vpc/how-to/create-private-network/) inside the VPC. You can either let Scaleway create the network with an auto-generate subnet, which will provide the private IP addresses for attached resources, or specify a self-defined subnet. | |
| 2. [Create a Private Network](/network/vpc/how-to/create-private-network/) inside the VPC. You can either let Scaleway create the network with an auto-generated subnet, which will provide the private IP addresses for attached resources, or specify a self-defined subnet. |
| 2. [Create a Private Network](/network/vpc/how-to/create-private-network/) inside the VPC. You can either let Scaleway create the network with an auto-generate subnet, which will provide the private IP addresses for attached resources, or specify a self-defined subnet. | ||
| 3. [Create a Public Gateway](/network/public-gateways/how-to/create-a-public-gateway/) (set it to advertise the [default route](/network/public-gateways/concepts/#default-route)) and [attach it to the Private Network](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network). | ||
| 4. [Set up SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/) on the Public Gateway, to allow administrator access. | ||
| 5. [Create a Managed Database](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) |
There was a problem hiding this comment.
Suggested change
| 5. [Create a Managed Database](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) | |
| 5. [Create a Managed Database](/managed-databases/postgresql-and-mysql/how-to/create-a-database/). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add first VPC use case