Step 2: VPC with a Single Public Subnet - Fluid Topics - 3.7 - Technical Notes

Prepare AWS for an Installation of Fluid Topics on Multiple Servers

Product
Fluid Topics
Fluid Topics Version
3.7
Category
Technical Notes
Target Audience
public

In this step, you can configure the VPC.


VPC with a Single Public Subnet
  1. Fill in the following fields:
    • IP CIDR block: 10.0.0.0/24

      This addressing block (or network block) is only used as an example to keep the documentation coherent and should be the responsibility of the customer. It must be followed by "/24" (meaning that 251 IP addresses are available) to allow for future addition of subdivisions within the VPC.

    • VPC Name: Fluid Topics VPC

      This information is optional and only used as an example to keep the documentation coherent and should be the responsibility of the customer. We recommend using a name easy to remember.

    • Public subnet: 10.0.0.0/27

      The subnet is a subdivision of the VPC, meaning it is set according to the IP CIDR block parameter. This IP is only used as an example to keep the documentation coherent and should be the responsibility of the customer, but we strongly recommend to use "/27" (meaning that 27 IP addresses are available) to allow for future addition of subdivisions within the VPC.

    • Availability Zone: you must select at least one of the proposed availability zones for the subnet.
      Attention: This step is very important as remaining availability zones will be used for future addition of subdivisions within the VPC.
    • Subnet name: Subnet 1

      This information is optional and only used as an example to keep the documentation coherent and should be the responsibility of the customer. We recommend using a name easy to remember.

    • Add endpoints for S3 to your subnets: None
    • Enable DNS hostname: select "Yes"
    • Hardware tenancy: Default
  2. Click Create VPC.
    The VPC Dashboard is displayed.
  3. Click Your VPCs to consult the newly created VPC:

    The VPC dashboard
    Attention: If the DNS resolution is not enabled for the VPC, errors may occur later.