Cloud Connector-AWS cloud link: establishing, editing and deleting

This article provides instructions on how to link AWS from Telstra clouds to Cloud Connector. If you're looking to link a BYO AWS cloud to Cloud Connector, we have another page with instructions for that.

You'll need to be logged in as an Admin or Manager at workspace layer or higher.

Learn more about the Cloud Sight management layers

Learn more about user and access management

On the 'Cloud services' page (home page), click on the name of a Cloud Connector you've already added and linked to your Telstra Next IP® network.

This takes you to the Connections tab on the details page for that Cloud Connector.  

This is where you can:

• Establish a link between a Cloud Connector and an AWS cloud
• Edit the link 
• Delete the link

Establishing a link between a Cloud Connector and an AWS cloud 

Prerequisites

• A Telstra Next IP network service in place with an allocated and known Full National Number (FNN).
• An AWS cloud service
• IP addresses must not overlap with these ranges: 0.0.0.0/8, 127.0.0.0/8, 169.254.0.0/16, 224.0.0.0/4, 240.0.0.0/4, 255.255.255.255/32
• One /30 network for interconnect addressing. This is subnetted into two /31 blocks of IPv4 addresses and must be unique across your sites
•  

Steps to link Cloud Connector to AWS cloud

The steps described below refer to the details page for a Cloud Connector already linked to your Next IP network (the image shows a details page that's connected to Next IP but not a cloud). You can link more than one cloud to a cloud connector.

1. Select Link a cloud. 

2. Answer the questions to choose the cloud you want to link to the Cloud Connector.

2.1. You'll be asked if the cloud you want to link is already on Cloud Sight. Click on Yes.

2. 2. You'll see a list of clouds on Cloud Sight. Select the AWS cloud you want to link. 

3. Configure the link between your AWS cloud and your Cloud Connector.

You'll need to:

• Enter a link name – a reference name for this cloud link
• Select a link location – select where the link is located
• Allocate Bandwidth to the link – this bandwidth will be a portion of the total bandwidth you've allocated to the Cloud Connector. (If you've connected other clouds to your Cloud Connector, the aggregate of bandwidths allocated to those links cannot exceed that of your Cloud Connector.)

If you don't have enough bandwidth on your Cloud Connector to assign the value you've chosen to the link, you'll be given the option of upgrading your Cloud Connector bandwidth.

The available bandwidth will depend on the location you've selected:  

• If you've selected the 'Sydney - Equinix SY3' location, you can choose from
  • 50Mbps
  • 100Mbps
  • 200Mbps
  • 300Mbps
  • 400Mbps
  • 500Mbps
  • 1Gbps
  • 2Gbps
  • 5Gbps
• If you've selected 'Sydney - Global Switch' you'll have
  • 50Mbps
  • 100Mbps
  • 200Mbps
  • 300Mbps
  • 400Mbps
  • 500Mbps

• Choose your peering type. You can choose between
  • Private peering
    • Choose whether you want route summarisation – route summarisation allows you to limit the number of routes advertised into your Virtual Private Clouds (VPCs) on your virtual private interface. This is useful because AWS routing tables have a 100-route limit per VPC.
      • Choose your route summarisation type:
        
        • RFC1918 drop public routes
        • RFC1918 allow public routes
        • Default route summarisation
        • No route summarisation

Learn more about route summarisation types

• • • • Enter interconnect subnet – You must provide a /30 IP subnet block for the network interconnect
      • Enter an Amazon-side ASN. Learn more about Amazon-side ASN

• • Public peering
    • Enter interconnect subnet – You must provide a /28 IP subnet block for the network interconnect
• Click on Next

4. Complete the post-connection configuration. 

This step depends on what peering type you've chosen. 

If you've chosen public peering  you'll need to follow these instructions.

If you've chosen private peering you can choose how you'd like to extend connectivity to your Virtual Private Clouds (VPCs).You can choose to:

• Connect the VPCs via Cloud Sight
  • Select 'Yes, I'll select the VPCs that need to be connected'
  • Name your AWS Direct Connect Gateway 
  • Select your Virtual Private Clouds
    • Select the region and VPCs.
    • You can add more VPCs by selecting the + Add another Virtual Private Cloud button.
    • If there are no VPCs available, you can save and exit this form, log in to your AWS console and create one.

Or:

• Connect the VPCs yourself (via the AWS Management Console)
  • Select 'No, I'll connect the VPCs myself on the AWS console.'

Remember, the link to your cloud isn't activated until you've completed connecting your VPCs, even if you've submitted this form.

Click on Next

When you connect VPCs via Cloud Sight

Cloud Sight connects to your VPCs by creating an AWS Direct Connect Gateway. Read our article on connecting your VPCs via Cloud Sight for more details. 

When connecting VPCs yourself

This option allows you to choose how your AWS Direct Connect is connected to your VPCs via the AWS Management Console. This allows you to connect your VPCs with or without an AWS Direct Connect Gateway.

Refer to AWS documentation on creating AWS Direct Connect Connections.

Note that we recommend using the AWS default BGP ASN (65422) when you're creating Virtual Private Interfaces.

You will also need to complete the following post-setup steps:

• Configure your VPC
• Test end-to-end connectivity (from your Next IP network to your AWS cloud)

5.  Review your configuration and (if necessary) buy additional bandwidth.

• You'll only be charged for any upgrades to your Cloud Connector bandwidth - if you have, please accept the Terms and Conditions.

Select the Link button to submit the form. Note that you can save the details you've entered at any time, and return to complete the form later.

Edit the link between your Cloud Connector and AWS Cloud

The steps described below refer to the details page for a Cloud Connector already linked to your Next IP network and an AWS cloud. 

1. Select View from the drop down menu on the cloud tile (three dots on a tile on the right of your Cloud Connector).

2.  Inline editing is available on the View page.

2.1 Click on the edit (pencil icon) icon next to the field you want to edit.

The following fields can be edited via the View page:

• Route summarisation. Learn more about Route summarisation 
• Amazon-side ASN. Learn more about Amazon-side ASN

Please note that if you want a different bandwidth you must establish a new link between your Cloud Connector and your cloud and then delete the previous link.

3. Post-connection configuration can't be edited via Cloud Sight.

To manually edit your post-connection configuration:

If you've chosen public peering  you'll need to follow these instructions.

If you've chosen public peering you'll need to connect the VPCs yourself (via the AWS Management Console)

Connect the VPCs yourself

You can do this via the AWS Management Console. This allows you to connect your VPCs with or without an AWS Direct Connect Gateway.

See AWS documentation on creating AWS Direct Connect Connections for instructions.

Note that we recommend using the AWS default BGP ASN (65422) when you're creating Virtual Private Interfaces.

You will also need to complete the following post-setup steps:

• Configure your VPC
• Test end-to-end connectivity (from your Next IP network to your AWS cloud)

4. After you've completed editing, click on the tick to submit your changes. To cancel the changes click on the cross.

 

Delete the link between your Cloud Connector and AWS Cloud

The steps described below refer to the details page for a Cloud Connector already linked to your Next IP network and a cloud. 

1. Select Delete from the drop down menu on the cloud (three dots on a tile on the right of your Cloud Connector) you want to delete.

2. Type the word 'Delete' in the text box.

3. Select Yes, delete.