Creating a Net Access Point

You can create a Net access point in your Net to enable your virtual machines (VMs) to access another OUTSCALE service through a private connection.

Creating a Net Access Point Using Cockpit v2

Before you begin: Make sure you have enough quota to allocate one public IP to your account, as one is automatically allocated when creating a Net access point. For more information, see Getting Information About Your Account and Quotas and About Net Access Points.

  1. In the Net Access Points dashboard, click IconAddFull Create Net Access Point.
    The CREATE NET ACCESS POINT dialog box appears.

  2. In the Name field, type a name for the Net access point.

    This action adds a Name tag of 255 characters maximum. You can use any character, including accented letters.

  3. From the Net list, select the Net you want to create an access point for.

  4. From the Service list, select the service for which you want to create a public connection through a Net access point.

  5. From the Route table(s) section, check the box of the route table that you want to associate with the Net access point.

    Multiselection is available.

  6. Click Create.
    The Net access point is created.

Creating a Net Access Point Using OSC CLI

Before you begin:

The CreateNetAccessPoint command creates a Net access point to access an OUTSCALE service from this Net without using the Internet and public IPs.
You specify the service using its name. For more information about the available services, see ReadNetAccessPointServices.

To control the routing of traffic between the Net and the specified service, you can specify one or more route tables. Virtual machines placed in Subnets associated with the specified route table thus use the Net access point to access the service. When you specify a route table, a route is automatically added to it with the destination set to the prefix list ID of the service, and the target set to the ID of the access point.

When a Net access point is created, a public IP is automatically allocated to your account and used for the Net access point. This public IP is not connected to the Internet. It is counted in your quota, but it is not billed.

For more information, see About Net Access Points.

Request sample
$ osc-cli api CreateNetAccessPoint --profile "default" \
    --NetId "vpc-12345678" \
    --RouteTableIds '["rtb-12345678"]' \
    --ServiceName "com.outscale.eu-west-2.oos"

This command contains the following attributes that you need to specify:

  • DryRun: (optional) If true, checks whether you have the required permissions to perform the action.

  • NetId: The ID of the Net.

  • RouteTableIds: (optional) One or more IDs of route tables to use for the connection.

  • ServiceName: The name of the service (in the format com.outscale.region.service).

The CreateNetAccessPoint command returns the following elements:

  • NetAccessPoint: Information about the Net access point.

  • ResponseContext: Information about the context of the response.

Result sample
{
  "ResponseContext": {
    "RequestId": "0475ca1e-d0c5-441d-712a-da55a4175157"
  },
  "NetAccessPoint": {
    "Tags": [],
    "NetAccessPointId": "vpce-12345678",
    "RouteTableIds": [
      "rtb-12345678"
    ],
    "State": "pending",
    "NetId": "vpc-12345678",
    "ServiceName": "com.outscale.eu-west-2.oos"
  }
}

Creating a VPC Endpoint Using AWS CLI

Before you begin:

To create a VPC endpoint, use the create-vpc-endpoint command following this syntax:

Request sample
$ aws ec2 create-vpc-endpoint \
    --profile YOUR_PROFILE \
    --vpc-id vpc-1234abcd \
    --service-name com.outscale.eu-west-2.oos \
    --route-table-ids rtb-12345678 \
    --endpoint https://fcu.eu-west-2.outscale.com

This command contains the following attributes that you need to specify:

  • (optional) profile: The named profile you want to use, created when configuring AWS CLI. For more information, see Installing and Configuring AWS CLI.

  • vpc-id: The ID of the VPC.

  • service-name: The name of the prefix list corresponding to the service.

  • (optional) route-table-ids: One or more IDs of route tables to which you want to add a route to the service using the VPC endpoint.

    • Instances placed in subnets associated with the specified route tables use the VPC endpoint to access the service within the VPC Region. When you specify a route table, a route is automatically added to it with the destination set to the ID of the service prefix list, and the target set to the ID of the VPC endpoint.

    • If you do not specify any route table ID, no route is added in any route table. You then need to associate one or more route tables with the VPC endpoint to automatically create the appropriate route into them. For more information, see Adding or Removing a Route Table Associated with a Net Access Point.

  • endpoint: The endpoint corresponding to the Region you want to send the request to.

The create-vpc-endpoint command returns the following elements:

  • VpcEndpoint: Information about the newly created VPC endpoint. This element contains the following information:

    • VpcId: The ID of the VPC in which the VPC endpoint is.

    • State: The state of the VPC endpoint. For more information, see About Net Access Points.

    • ServiceName: The name of the prefix list corresponding to the service.

    • RouteTableIds: One or more IDs of route tables routing traffic to the service using the VPC endpoint.

    • VpcEndpointId: The ID of the VPC endpoint.

    • CreationTimestamp: The date and time of creation of the VPC endpoint.

Result sample
{
  "VpcEndpoint": {
                 "VpcId": "vpc-12345678",
                 "State": "pending",
                 "ServiceName": "com.outscale.eu-west-2.oos",
                 "RouteTableIds": [
                                   "rtb-1234abcd"
                                  ],
                 "VpcEndpointId": "vpce-87654321",
                 "CreationTimestamp": "2016-11-07T10:32:14Z"
                }
}

The VPC endpoint is created and a route to the service using it is added to the specified route tables.

Related Pages

Corresponding API Methods

AWS™ and Amazon Web Services™ are trademarks of Amazon Technologies, Inc or its affiliates in the United States and/or other countries.