Creating a VPC Endpoint

You can create a VPC endpoint in your Virtual Private Cloud (VPC) to enable your instances to access another OUTSCALE service through a private connection.

Creating a VPC Endpoint Using Cockpit

  1. Click VPC > VPC Endpoints.

  2. Click Create .
    The CREATE VPC ENDPOINT dialog box appears.

  3. (optional) In the Name field, type a name for the VPC endpoint.

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

  4. From the VPC list, click the VPC you want to create an endpoint for.

  5. From the Service Names list, click the service for which you want to create a public connection through a VPC endpoint.

  6. From the Route table(s) section, select the route table that you want to associate with the VPC endpoint.

    Multiselection is available.

  7. Click Create to validate.
    The VPC endpoint is created and appears on the VPC Endpoints page.

Creating a VPC Endpoint Using AWS CLI

Before you begin: Get the name of the prefix list corresponding to the service you want to access using the VPC endpoint. For more information, see Getting Information About Prefix Lists.

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 VPC Endpoint.

  • 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 VPC Endpoints.

    • 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 Method

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