Creating a network ACL

Creating a network ACL in the UI

To configure an ACL in the IBM Cloud console, follow these steps:

1. Go to the IBM Cloud console and log in to your account.

2. Select the menu icon , then click > VPC Infrastructure >Access control lists in the Network section.

3. Click the Create + button.

4. Select the Edit location icon and enter values for the following fields:

   • Geography - Select a continent for your access control list.
   • Region - Select a region for your access control list.

5. Enter values for the following fields under details:

   • Public gateway name - Type a unique name for your access control list.
   • Resource group - Select a resource group for your access control list. You can use the default group for this access control list, or select from the resource group list (if defined). For more information, see Best practices for organizing resources in a resource group.

   After provisioning is complete, you cannot change the resource group.

   • Tags - Add user tags. User tags are visible account-wide. For more information, see Working with tags.
   • Access management tags - Add access management tags to help organize access control relationships. For more information, see Controlling access to resources by using tags.
   • VPC - Select a VPC. You can use the default VPC for this public gateway, or select from the list (if defined). For more information, see Getting started with Virtual Private Cloud.

6. Under Rules, click the Create + button to configure inbound and outbound rules that define what traffic is allowed in or out of the subnet. For each rule, specify the following information:

   • Select whether to allow or deny the specified traffic.
   • Select the protocol to which the rule applies.
   • For the source and destination of the rule, specify the IP range and ports for which the rule applies. For example, if you want all inbound traffic to be allowed to the IP range 192.168.0.0/24 in your subnet, specify Any as the source and 192.168.0.0/24 as the destination. However, if you want to allow inbound traffic only from 169.168.0.0/24 to your entire subnet, specify 169.168.0.0/24 as the source and Any as the destination for the rule.
   • Specify the rule's priority. Rules with lower numbers are evaluated first and override rules with higher numbers. For example, if a rule with priority 2 allows HTTP traffic and a rule with priority 5 denies all traffic, HTTP traffic is still allowed.
   • Click Create.
   • Select a subnet to attach to this ACL. Click Attach to attach additional subnets.

   If the subnet has an existing ACL connection, the ACL is replaced by the ACL being created.

7. View your Total estimated cost in the Summary menu in the lower right of the page.

Creating a network ACL from the CLI

Before you begin, set up your CLI environment.

To create a network ACL from the CLI, run the following command:

ibmcloud is network-acl-create ACL_NAME VPC \
[--rules (RULES_JSON|@RULES_JSON_FILE) | --source-acl-id SOURCE_ACL_ID] \
[--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] \
[--output JSON] [-q, --quiet]

Where:

• ACL_NAME is the name of the network ACL.
• VPC is the ID of the VPC.
• --rules are the rules for the ACL in JSON or JSON file.
• --source-acl-id is the ID of the network ACL to copy rules from.
• --resource-group-id is the ID of the resource group. This option is mutually exclusive with --resource-group-name.
• --resource-group-name is the name of the resource group. This option is mutually exclusive with --resource-group-id.
• --output specifies output in JSON format.
• -q, --quiet suppresses verbose output.

For example:

• ibmcloud is network-acl-create my-acl 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479
• ibmcloud is network-acl-create my-acl 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --source-acl-id 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3

Creating a network ACL with the API

To create a network ACL with the API, follow these steps:

1. Set up your API environment.

2. Store the VpcId value in a variable to be used in the API command:

   export VpcId=<your_vpc_id>
   

3. Create a network ACL:

   curl -X POST -sH "Authorization:${iam_token}" \
   "$vpc_api_endpoint/v1/network_acls?version=$api_version&generation=2" \
   -d '{"name": "testacl", "vpc":{"id": "'$VpcId'"},"resource_group": {"id": "'$ResourceGroupId'"}}' | jq