AWS Direct Connect

1.1. What is AWS Direct Connect

Linxdatacenter provides a direct dedicated Customer connection to Amazon Web Services (AWS) through a connection to the Cloud Exchange global software-defined network.

In Russia, connections are available through Linxdatacenter in Moscow and St. Petersburg, where all key carriers are present (see Appendix 1.1.) to arrange last mile connections to customer offices and data centers. On the AWS side, 28 locations are available worldwide (see Appendix 1.2.), including Europe, North America and Asia. The list of locations is constantly expanding.

DirectConnect has the following advantages:

  • flexible and scalable access speeds;
  • private access, independent of the public Internet;
  • high network performance and security;
  • improved security of data and transactions compared to using the public Internet.

Multiple virtual connections are available from a single location, providing the scalability and flexibility needed to meet business needs and create a clear cloud strategy.

Linxdatacenter Moscow Linxdatacenter Saint Petersburg 
AWS EU: Frankfurt 48 ms, 5 Mbit/s to 10 Gbit/s 38 ms, 5 Mbit/s to 10 Gbit/s
AWS EU: London 55 ms, 5 Mbit/s to 10 Gbit/s 44 ms, 5 Mbit/s to 10 Gbit/s
AWS US West: San Jose 199 ms, 5 Mbit/s to 10 Gbit/s 188 ms, 5 Mbit/s to 10 Gbit/s
AWS Asia Pacific: Singapore 273 ms, 5 Mbit/s to 10 Gbit/s 262 ms, 5 Mbit/s to 10 Gbit/s
AWS other locations By request By request

1.2 Features and Benefits
1.2.1 Working with big data:

Transferring large data sets to AWS over the Internet is time-consuming and can become costly: Internet bandwidth is divided between data and business-critical network traffic, web applications, and user access to web resources. To reduce the time it takes to transmit big data, you can increase bandwidth by turning to your existing ISP. In this case, you will need to replace or purchase expensive equipment, renew your contract, and sign a long-term commitment. Translated with www.DeepL.com/Translator (free version)

With Direct Connect, the client transmits data directly from the data center or office bypassing the Internet through a dedicated channel.

1.2.2 Real-time application data transfer

Applications that use Internet links to transmit real-time data, such as voice and video, work best with constant network performance. That said, network latency over the Internet varies because the global network consists of a large number of carriers and is constantly re-routing data from point A to point B.
Direct Connect controls data routing and ensures consistent bandwidth and network latency (jitter).

1.2.3 Hybrid environments

Direct Connect helps create hybrid environments that require private connections between distributed sites. Hybrid environments allow you to combine the flexibility and cost advantages of AWS with the Client's on-premises infrastructure.

1.3 How it works

The connection consists of a physical network connection from the customer's office or data center to Linxdatacenter's data center locations in Moscow (14, bldg. 1, 8th March street) and St. Petersburg (20a, Repischeva street), where the Cloud Exchange direct access ports are located.
Each AWS Direct Connect connection point has a high-speed fiber optic connection and API integration that simplifies ordering, provisioning and ongoing management.

1.4 Capacity

Bandwidth for the Client is scalable from 5 Mbit/s to 10 Gbit/s in 1 Mbit/s increments.

1.5 Connection options
1.5.1 Providing a direct connection to your VPC

VXC (Virtual Cross Connect) provides a direct connection to AWS VPC. A separate connection is provided for each client and each service, providing complete isolation and consistent network connectivity compared to a public Internet connection.
Direct Connect operates at Layer 3 of the OSI model (L3) and requires BGP for communication between the Client network and AWS VPC. The Customer must provide IP addressing information when ordering the connection.

1.5.2 Public virtual interface

A public virtual interface is used for guaranteed network connectivity to public AWS endpoints, such as Amazon S3, DynamoDB, and Glacier storage services.
Публичный виртуальный интерфейс позволяет подключаться ко всему пространству публичных IP-адресов AWS в глобальном масштабе и получения глобальных IP-маршрутов сетей Amazon.

Accessing AWS resources through a public virtual interface has the following requirements:

  • the public number of the autonomous system (ASN) owned by the customer;
  • agreed between the Client and Linxdatacenter VLAN_ID;
  • block of public IP addresses (/30) for BGP connection.

The connection process takes 48 hours or more, as AWS will check the allocated IP space.

1.5.3 Private Virtual Interface

A private virtual interface is used to connect to AWS private environments, such as the Amazon VPC virtual private cloud.

A private virtual interface allows you to connect to VPC resources (such as EC2 instances, load balancing, and RDS database instances) in a private address space. The private virtual interface connects to the AWS Direct Connect gateway and communicates with one or more virtual private gateways in any AWS regions. For a private virtual interface, AWS announces the entire VPC subnet over a BGP session. Translated with www.DeepL.com/Translator (free version)

Accessing AWS resources through a private virtual interface has the following requirements:

  • private number of the autonomous system (ASN);
  • supported private range ASN 64512-65535;
  • agreed between the Client and Linxdatacenter VLAN_ID;
  • block of private IP addresses (/30) in the range 169. x. x. x for the BGP session.

Depending on the Customer's requirements, several connection options to AWS are provided - single, redundant and redundant connections to achieve maximum SLA.

1.6 How to order

  • Develop a communications scheme in collaboration with Linxdatacenter network engineers.
  • Order Direct Connect through AWS.
  • Tell Linxdatacenter the Direct Connect service key.
  • Set up routing on the Client side of the network and start using it.

1.7 Tariffication

  • The customer pays for AWS services himself.
  • Linxdatacenter charges for:
    - channel bandwidth - according to the resources used;
    - services to technical support - for man-hours.

Write to us

How we optimized customer data center management

Data center is a complex IT and engineering object, which requires professionalism at all levels of management: from managers to technical specialists and executors of maintenance works. Here's how we helped our client put operational management in corporate data centers in order.
 

Taras Chirkov, Head of Data Center in St. Petersburg  in St. Petersburg 

Konstantin Nagorny, chief engineer of data center in St. Petersburg.  in St. Petersburg 

Data center is a complex IT and engineering object, which requires professionalism at all levels of management: from managers to technical specialists and executors of maintenance works. Here's how we helped our client put operational management in corporate data centers in order.  

Management is in the lead 

The most advanced and expensive IT equipment will not bring the expected economic benefits if proper processes of engineering systems operation in the data center, where it is located, are not established.  

The role of reliable and productive data centers in today's economy is constantly growing along with the requirements for their uninterrupted operation. However, there is a big systemic problem on this front.  

A high level of "uptime" - failure-free operation of a data center without downtime - depends very much on the engineering team that manages the site. And there is no single formalized school of data center management.  

And there is no single formalized school of data center management.    

Nationwide  

In practice, the situation with the operation of data centers in Russia is as follows.  

Data centers in the commercial segment usually have certificates confirming their management competence. Not all of them do, but the very specifics of the business model, when a provider is responsible to the client for the quality of service, money and reputation in the market, obligates them to own the subject. 

The segment of corporate data centers that serve companies' own needs lags far behind commercial data centers in terms of operational quality. The internal customer is not treated as carefully as the external customer, not every company understands the potential of well-configured management processes. 

Finally, government departmental data centers - in this regard, they are often unknown territory due to their closed nature. An international audit of such facilities is understandably impossible. Russian state standards are just being developed.  

This all translates into a "who knows what" situation. "Diverse" composition of operation teams composed of specialists with different backgrounds, different approaches to the organization of corporate architecture, different views and requirements to IT departments.  

There are many factors that lead to this state of affairs, one of the most important is the lack of systematic documentation of operational processes. There are a couple of introductory articles by Uptime Institute which give an idea of the problem and how to overcome it. But then it's necessary to build the system by your own efforts. And not every business has enough resources and competence for that.  ⠀⠀  

Meanwhile, even a small systematization of management processes according to industry best practices always yields excellent results in terms of improving the resilience of engineering and IT systems.  

Case: through thorns to the relative order 

Let's illustrate by the example of an implemented project. A large international company with its own data center network approached us. The request was for help to optimize the management processes at three sites where IT systems and business-critical applications are deployed.  

The company had recently undergone an audit of its headquarters and received a list of inconsistencies with corporate standards with orders to eliminate them. We were brought in as a consultant for this as a bearer of industry competence: we have been developing our own data center management system and have been educating on the role of quality in operational processes for several years.  

Communication with the client's team began. The specialists wanted to get a well-established system of data center engineering systems operation, documented on the processes of monitoring, maintenance and troubleshooting. All this had to ensure optimization of the infrastructure component in terms of IT equipment continuity.  

And here began the most interesting part.  

Know thyself 

To assess the level of data centers in terms of compliance with standards, you need to know the exact requirements of the business to IT systems: what is the level of internal SLA, the allowable period of equipment downtime, etc.  

It became clear right away that the IT department did not know exactly what the business wanted. There were no internal criteria of service quality, no understanding of the logic of their own infrastructure.  

Colleagues simply had no idea what the permissible downtime for IT-related operations was, what the optimal system recovery time in case of a disaster was, or how the architecture of their own applications was structured. For example, we had to figure out whether a "crash" of one of the data centers would be critical to the application, or if there were no components affecting the application.  

Without knowing such things, it is impossible to calculate any specific operational requirements. The client recognized the problem and increased coordination between IT and the business to develop internal requirements and establish relationships to align operations.  

Once an understanding of the IT systems architecture was achieved, the team was able to summarize the requirements for operations, contractors, and equipment reliability levels.  

Improvements in the process 

Our specialists traveled to sites to assess infrastructure, read existing documentation, and checked the level of compliance of data center projects with actual implementation.  

Interviews with the responsible employees and their managers became a separate area of focus. They told what and how they do in different work situations, how the key processes of engineering systems' operation are arranged.  

After starting the work and getting acquainted with the specifics of the task the client "gave up" a little: we heard the request "just to write all the necessary documentation", quickly and without deep diving into the processes.  

However, proper optimization of data center "engineering" management implies the task to teach people to properly assess the processes and write unique documentation for them based on the specifics of the object.  

It is impossible to come up with a working document for a specific maintenance area manager - unless you work with him at the site continuously for several months. Therefore this approach was rejected: We found local leaders who were willing to learn themselves and lead their subordinates.  

Having explained the algorithm of documents creation, requirements to their contents and principles of instructions ecosystem organization, for the next six months we controlled the process of detailed writing of documentation and step-by-step transition of the personnel to work in a new way. 

This was followed by a phase of initial support for work on the updated regulations, which lasted one year in a remote format. Then we moved on to training and drills - the only way to put the new material into practice.  

What's been done 

In the process, we were able to resolve several serious issues.  

First of all, we avoided double documentation, which the client's employees feared. To this end, we combined in the new regulations the regulatory requirements applied to various engineering systems as standard (electrics, cooling, access control), with industry best practices, creating a transparent documentation structure with simple and logical navigation.   

The principle of "easy to find, easy to understand, easy to remember" was complemented by the fact that the new information was linked to the old experience and knowledge of the employees. 

Next, we reshuffled the staff of service engineers: several people turned out to be completely unprepared for the change. The resistance of some was successfully overcome in the course of the project through the demonstration of benefits, but a certain percentage of employees turned out to be untrained and unresponsive to new things.  

But we were surprised by the company's frivolous attitude to its IT infrastructure: from the lack of redundancy of critical systems to the chaos in the structure and management.  

In 1.5 years the engineering systems management processes have been pumped up to the level that allowed the company's specialists to successfully report "for quality" to the auditors from the headquarters.  

With the support of the operating component development pace the company will be able to pass any existing certification of data centers from leading international agencies.  

Summary 

In general, the prospects of consulting in the field of operational management of data centers, in our opinion, are the brightest.  

The process of digitalization of the economy and the public sector is in full swing. Yes, there will be a lot of adjustments in the launch of new projects and plans for the development of old ones, but this will not change the essence - the operation should be improved at least to improve the efficiency of already built sites.  

The main problem here: many managers do not understand what thin ice they are walking on, not paying proper attention to this point. The human factor is still the main source of the most unpleasant accidents and failures. And it needs to be explained.  

Government data center projects are also becoming more relevant now and require increased attention in terms of operations: the scope of government IT systems is growing. Here, too, the development and introduction of a system of standardization and certification of sites will be required.  

When the requirements to public data centers in Russia at the level of legislation will be reduced to a standard, it can be applied to commercial data centers, including for the placement of public IT resources.  

The work in this area is ongoing, we are participating in this process in consultation with the Ministry of Digital and by building competencies for teaching courses on data center operation at the ANO Data Center. There is not much experience on such tasks in Russia, and we believe that we should share it with colleagues and clients. 

AWS Direct Connect

BEST, money transfer and payments operator

business challenge

The customer faced a technical issue with a persistent BGP session flag with Linxdatacenter hardware. We examined the problem and found out that one of customer’s hosts was under a DDoS attack.

Because of the distributed nature of the attack, traffic couldn’t be filtered effectively, and disconnecting the host from the external network wasn’t an option. The attack stopped after changes in the server configuration, but resumed the day after. A 5.5 Gbps attack overloaded the junctions with internet providers, affecting other Linx Cloud users. To mitigate the effects of the attack, we employed a dedicated DDoS protection service.

Solution

To ensure the continuous availability of resources hosted in Linx Cloud, we rerouted all the customer’s traffic through StormWall Anti-DDoS system. The attack was stopped within half an hour. To prevent future cyberattacks, we organized all connections to the customer’s resources through the StormWall network.

client:

BEST, money transfer and payments operator

business challenge

The customer faced a technical issue with a persistent BGP session flag with Linxdatacenter hardware. We examined the problem and found out that one of customer’s hosts was under a DDoS attack.

Because of the distributed nature of the attack, traffic couldn’t be filtered effectively, and disconnecting the host from the external network wasn’t an option. The attack stopped after changes in the server configuration, but resumed the day after. A 5.5 Gbps attack overloaded the junctions with internet providers, affecting other Linx Cloud users. To mitigate the effects of the attack, we employed a dedicated DDoS protection service.

Solution

To ensure the continuous availability of resources hosted in Linx Cloud, we rerouted all the customer’s traffic through StormWall Anti-DDoS system. The attack was stopped within half an hour. To prevent future cyberattacks, we organized all connections to the customer’s resources through the StormWall network.

Thank you for your inquiry, we will get back to you shortly!