Skip to main content

How to create a subnet in AWS


If you haven't created the VPC in which you are going to create a new subnet, then check the article here.





A subnet is simply the subset of the IPv4 CIDR block which you defined while creating a VPC. It provides a demarcation for the broadcast domains.





Requirements:





  • An AWS account
  • Virtual Private Cloud (VPC) - A subnet always resides in a VPC and hence a VPC should be present prior to creating it
  • The subnet must be the wholly contained within the IPv4 CIDR block that you defined in the VPC




Steps:





  1. Sign in to your AWS account.
  2. Under Services >> Networking >> VPC
  3. VPC Dashboard >> Your VPCs >> Click on your VPC
  4. Select Subnets >> Click on "Create Subnet"












Details:





  1. Name tag: Name of the subnet (self evident)
  2. VPC: Select the VPC that you want this subnet to be the part of
  3. VPC CIDRs would be automatically populated (since it was defined at the time of VPC creation)
  4. Availability Zone: You get an option to select the AZ (in the same region as that of the VPC), where the subnet should be created. If you select "No preference" Amazon would select the AZ for you, automatically.
  5. IPv4 CIDR block : The actual subnet for which we are doing all this configuration..

Labels:

Comments

Post a Comment

Popular posts from this blog

Alibaba Cloud Networking Services List

Virtual Private Cloud - Isolated tenant containing IP address range, network segment, route tables and gateway. NAT Gateway - Allows Alibaba ECS instances to be source NAT'd with public IP to communicate on Internet. Cloud Enterprise Network VPN Gateway Express Connect Smart Access Gateway Alibaba Cloud PrivateZone PrivateLink Network Intelligence Services (NIS) Global Traffic Manager CDN and Edge Alibaba Cloud CDN Secure Content Delivery Dynamic CDN Edge Node Service (ENS) Global Accelerator
Post a Comment
Read more

MITRE ATT&CK - Kerberos Vulnerabilities and Security

From the previous post, the summary of Kerberos authentication process is as below: For the initial authentication, the user’s client machine sends a request to the KDC  Authentication Service (AS) . The request includes details like the user’s username, and the date and time. All information except the username is encrypted using the hash of the user’s password. The KDC AS uses the username to look up its copy of the user’s password hash and uses it to decrypt the rest of the request. If the decryption is successful, that means the client used the correct password hash and the user has successfully authenticated. Once the user is authenticated, the KDC AS sends the user’s client a  ticket granting ticket   (TGT) . The TGT includes a unique session key and a timestamp that specifies how long that session is valid (normally 8 or 10 hours). Importantly, before sending the TGT, the KDC encrypts it using the password hash for a special account, the  KRBTGT account. ...
7 comments
Read more

Checkpoint - Exporting Objects in CSV format

Be it a Network Operations Manager, Security Architect or a Security Auditor, the people up the hierarchy always harangue the Security Engineers to compile the list of firewall objects or rules or policies or the traffic statistics and so on.. This can turn out to be quite hectic especially if there are no built in features to systematically provide the output in a "layman-readable" format. Come, Checkpoint's "Object Explorer..."  which not only provides the output in the "layman-readable" format, but also provides in-built filtering mechanisms, thereby ensuring that the Security Engineer doesn't have to rely on Google for building his scarce Microsoft Excel data filtering skills. The following screenshots will show how easy it is, with Checkpoint R80.10 to generate the firewall configuration inventory. On the SmartConsole Unified Portal, navigate to Menu >> Open Object Explorer... Select the Categories you wish to see in your output: Click o...
Post a Comment
Read more