AWS Direct Connect Reviews

We use Direct Connect to connect our cloud to on-premises data centers. We also used to use it for connecting multiple clouds together, but we don't use it for that anymore.

The general benefits of the cloud, such as being a managed service with relatively low maintenance, high availability, and scalability, help us in our operations. Direct Connect provides better connection quality and link diversification for high availability.

The general benefits of a managed service include low maintenance, high availability, and scalability as required. 

Direct Connect provides an improved connection quality and a diversified link, which contributes to high availability and failover capabilities.

I would like to see better traffic visibility and higher throughput security, especially for organizations that require more than what the current limit allows.

I have worked with the direct link for three years in different positions and companies.

There haven't been any issues with Direct Connect, and it's highly available.

Direct Connect is scalable for our needs, although we are not heavily invested in AWS.

We haven't had issues with Direct Connect that required escalation to technical support.

Positive

Before Direct Connect, I worked with ExpressRoute in Azure for similar purposes and they work equally well.

If you are somewhat familiar with Direct Connect, the initial setup is not really too complex. It is a set-and-forget solution.

It always comes down to expertise. Networking and cloud knowledge are required, and for us, we have the right people to manage it.

Not really. Direct Connect is a requirement rather than a solution that provides specific savings.

The cost is in line with what other cloud providers offer. As a customer, you always want something to be cheaper, but it aligns with industry standards.

We use ExpressRoute in Azure and have used similar solutions in other clouds.

I would recommend the service, but it isn't always the right solution for every problem.

I'd rate the solution eight out of ten.

We use AWS Direct Connect to create a virtual interface, configure AWS resources, test connectivity, and security.

AWS Direct Connect provides a secure and encrypted connection over the internet. The solution allows users to access resources, share data, and communicate privately across a public network.

It would be good if we could connect AWS Direct Connect from different networks.

I have been using AWS Direct Connect for three years.

Around three to four users are working with the solution in our organization.

The solution’s initial setup is easy.

Sometimes, we face problems in creating a setup or installing AWS Direct Connect. We select a Direct Connect gateway, then create a Direct Connect gateway, then attach the gateway with the VPC, and create a customer gateway. Sometimes, it creates an issue, but we completely create and install the solution.

I would recommend the solution to other users. AWS Direct Connect provides a dedicated physical network connection. After establishing a physical connection, we can create a virtual interface to connect to our virtual private cloud in AWS. We provide private network connectivity for accessing resources within our VPC.

We can configure the solution to create a hybrid network that combines the private connectivity of AWS Direct Connect with the flexibility of a VPN connection. It is useful where redundancy and failover are critical.

Overall, I rate the solution ten out of ten.

We use it for migration only, specifically to transfer storage from our normal data center to AWS for migration purposes.

AWS Direct Connect is highly secure and much faster compared to normal network infrastructure. It can be difficult to configure compared to cloud-based GUIs, but that's also the main advantage of using it.

It would be better if the setup and configuration of credentials were easier.

We are using Amazon S3 buckets for storage and the software UCS 3 bucket and Cloud Network Director. We have also been using AWS Direct Connect for the past year.

It is a stable solution. 15 members are using it for migration purposes. We use the data connector for migration and direct connector setup for networking.

It is a scalable solution. 

Initially, it was difficult for us as we not only wanted to use Direct Connect but also link it with our existing data center. So we faced difficulties at the architectural level. We even had difficulties configuring security policies and credentials such as user ID and password. It took almost five to six months to completely setup the solution. 

I would recommend it because it is secure and faster compared to conventional networking. Moreover, it's designed primarily for migration purposes.

Overall, I would rate the solution a nine out of ten.