#1 The broadest & deepest

AWS boasts the broadest and deepest capabilities for Windows of any cloud provider, with nearly twice as many Windows Server Instances compared to its closest competitor. It also offers the widest range of cloud services tailored for Microsoft technologies, seamlessly integrated within a cohesive ecosystem. This includes an array of compute, database, application, and deployment services, along with a comprehensive set of management tools, providing a solution for all your business requirements.

#2 Greater reliability & performance

With 77 Availability Zones (AZ) spread across 24 regions, the AWS Cloud guarantees that your workloads remain operational and accessible precisely when you need them. Customers can reduce their unplanned downtime by a whopping 98% by moving their Windows workloads to AWS. AWS delivers double the performance and achieved a 62% reduction in costs in comparison with the next largest cloud provider for a SQL Server workload on an EC2 R5b.8xlarge instance, according to Principled Technologies.

#3 Superior security

AWS offers a staggering 230 security, compliance, and governance services and features, five times more than its closest cloud provider counterpart. AWS also provides encryption across over a hundred distinct AWS services. By leveraging these comprehensive security offerings, customers can effectively safeguard their environments. The AWS Nitro System in EC2 instances offloads virtualization functions to dedicated hardware and software, effectively reducing the potential attack surface and ensuring minimal exposure to vulnerabilities.

#4 Cost optimization

By leveraging AWS for Windows workloads, customers benefit from accelerated growth, increased operational efficiency, and substantial long-term cost savings. According to IDC, customers can reduce their five-year cost of operations by 56% and achieve a 37% reduction in infrastructure costs. This translates to an impressive 442% return on investment (ROI) over a three-year period. Unique pricing models such as Savings Plans offer savings of up to 72% on Amazon EC2 instances, while Amazon EC2 Spot instances enable cost reductions of up to 90% for fault-tolerant workloads.

#5 Smooth migration

AWS has facilitated the seamless migration of millions of enterprises worldwide, including renowned names like Sysco, Hess, Sony DADC, Ancestry, and Expedia. With the time-tested AWS Migration Acceleration Program (MAP) methodology and the extensive expertise offered by AWS partners, customers are able to evaluate, optimize, and seamlessly shift their Windows and SQL Server workloads to AWS with minimal downtime to applications.

#6 Flexible licensing

AWS provides the broadest range of choices in the cloud for utilizing both new and existing Microsoft software licenses. With the purchase of license-included instances in Amazon Elastic Compute Cloud (Amazon EC2) or Amazon Relational Database Service (Amazon RDS), you receive fully compliant SQL Server licenses directly from AWS. You also have the flexibility to bring your existing licenses to AWS using options such as Amazon EC2 Dedicated Hosts, Amazon EC2 Dedicated Instances, or EC2 instances with default tenancy through Microsoft License Mobility via Software Assurance.

Ready to take the next step? Cloudar has unparalleled expertise in maximizing the potential of your Windows workloads on AWS. Get in touch to let us guide your way to higher performance and efficiency.

The post Unsurpassed: 6 reasons to run Microsoft Workloads on AWS appeared first on Cloudar.

#1 Assessing your current environment

The first step in planning a successful cloud migration strategy is to assess your current infrastructure. This involves identifying the applications, data, and infrastructure that are currently in use, as well as the performance and security requirements of each workload. Once you have a clear understanding of your current environment, you can determine which workloads are suitable for migration to the cloud.

#2 Choosing the right cloud provider  

Choosing the right cloud provider is an important decision that will impact the success of your cloud migration strategy. Factors to consider when choosing a cloud provider include pricing, services, security, and compliance. Speaking to different cloud providers and read customer reviews will help you choose the right provider for your business.

#3 Forming a cloud migration strategy

There are different cloud migration strategies that you can use to migrate your workloads to the cloud. These include lift-and-shift, re-platforming, and refactoring. Lift-and-shift involves moving your applications and data to the cloud without making any changes. Re-platforming involves making some changes to your applications to make them compatible with the cloud. Refactoring involves re-architecting your applications to take advantage of cloud-native services. Each strategy has its pros and cons. Choose the one that best suits your business needs.

#4 Planning the migration

Once you have chosen a cloud provider and a migration strategy, the next step is to create a migration plan. This involves setting timelines, allocating resources, and assessing risks. A detailed migration plan will help ensure that the migration process is smooth and minimizes downtime. Involve all stakeholders in the planning process to ensure that everyone is on the same page.

#5 Data migration

Data migration is a critical part of the cloud migration process. There are different data migration methods, including online and offline migration. Online migration means moving data from your on-premises environment to the cloud over the internet. Offline migration means moving data to the cloud using physical storage devices. Factors to consider when selecting a data migration method include data size, security, and downtime.

#6 Testing and validation

Testing and validation are important steps in the cloud migration process. Test your applications for compatibility, functionality, and performance before and after the migration process. This will help ensure that your applications are working correctly and that there are no issues that need to be fixed. Involving end-users in the testing process helps to ensure that the applications are meeting their needs.

#7 Managing the migration

Managing the migration process ensures that everything is running smoothly and minimizes downtime. Monitor the progress of the migration and communicate with stakeholders to keep them informed. Have a plan in place to fix any issues that may arise during the migration process.

#8 Post-migration optimization

Once the migration process is complete, it’s time to take steps to optimize costs, secure your cloud environment, and maintain compliance. This includes optimizing your cloud infrastructure to reduce costs, securing your cloud environment to protect against cyber threats, and ensuring that your cloud environment complies with industry regulations.

Migrating to the cloud can be a complex process, but with careful planning and execution, it can be a success. Reach out if you need support in navigating a smooth and successful cloud migration!

The post 8 steps to executing a successful cloud migration strategy appeared first on Cloudar.

Shared responsibility model 

Security and Compliance falls under the shared responsibility model between AWS and the customer. Under this model, AWS takes on some of the customer’s operational burden by operating, managing and controlling certain system components as well as the physical security of the facilities in which the service operates. Meanwhile the customer is responsible for the guest operating system, other associated application software as well as the configuration of the AWS provided security group firewall. This model helps share the load while providing flexibility and customer control. 

Under the shared responsibility model, AWS is responsible for the security “of the cloud”, protecting the infrastructure including the hardware, software, databases, networking, and facilities that run AWS Cloud services. The customer is charged with security “in the cloud”, and their responsibility will be determined by the AWS Cloud services they select, which impacts the amount of configuration work they must perform. Their remit includes data protection, identity and access management (IAM), OS configuration, network security and encryption.

Top security considerations 

Here are some of the top security challenges to keep in mind when migrating to the cloud:

• Regulatory and compliance requirements: The cloud environment must meet regulatory requirements and compliance requirements. AWS will have their regulatory requirements covered, but under the shared responsibility model the customer must ensure that they meet privacy requirements on their end, especially concerning sensitive information and access. They may also need specialized controls to meet certain industry requirements.
• Visibility and monitoring: Cloud environments like AWS are large and complex, and contain a wide array of settings to monitor. Security teams may struggle to understand what is going on in cloud environments, especially because cloud migrations imply dynamic change. Provisioning and decommissioning cloud assets rapidly and technical complexities can make security difficult to manage. Gaining visibility is key to identifying dark data and handling data privacy. It’s important to employ industry best practices for initial risk assessment, configuration and security, followed by careful monitoring.
• Managing DevOps: The DevOps team includes developers and infrastructure specialists who manage the DevOps pipeline: coding, building, validation and deployment. When migrating to the cloud, they are responsible for integrating security tools and addressing security issues. They also have to protect against threats when workloads and applications go live.
• Governance standards: Governance workflows and alignments need to become more agile in the Cloud, involving a wider variety of stakeholders. Establishing a set of security standards and baselines in collaboration with the governance team is key. A cloud governance committee can ensure cohesion across teams.
• Protecting network traffic: Just like traditional environments, cloud-based environments can be targets for malware, bots and data breaches. It is essential to control data privacy and protect against cyber threats while securely connecting the cloud to on-premises networks. Information security should be employed to maintain network security parameters.

The way forward 

While it’s important to always carefully account for security considerations, it should still be a no-brainer to go ahead and migrate to the cloud. After all, it’s the new normal for enterprise IT operations. Working with a consulting partner like Cloudar, companies can create a migration roadmap suited to their specific organization. This of course includes all the particulars of their industry and configuration needs. Not only will this make cloud migration more efficient and advantageous, it allows companies to benefit from Cloud Best Practices including security. 

As a Premier Consulting partner, Cloudar has a proven track record of migrating applications and infrastructure to the Cloud. Want to know more about how we execute secure migrations from start to finish? Reach out to us today. 

The post Seamless & secure cloud migration: top things to consider appeared first on Cloudar.

#1 Act first, think later

Once you realize what the cloud can do for you, you might feel inclined to jump right in. Act first, think later. Before you know it, you will feel lost in a haphazardly put together collection of tools. Start by identifying your needs and key objectives. Do your research. Get trustworthy advice. Determine which features and functionalities you want to focus on and stick to them, especially in the beginning. This way you will end up with an efficient, effective and well thought out cloud infrastructure with a guaranteed return on investment.

#2 Too much, too soon

AWS offers a plethora of tools and applications. The possibilities are endless. But not everything that is possible, is also necessary. At least not right now. We would strongly suggest you focus on building a manageable cloud environment that meets your current needs first. Over the long term you can expand and finetune your infrastructure with more advanced applications. If you need any help with selecting the right tools for you, Cloudar is happy to lend a hand.

#3 Compliancy anxiety

Getting started with the cloud might be very daunting at first. You want to build a scalable workspace in the cloud, but how are you going to keep it secure and stay compliant? Data safety in the cloud is one of the biggest concerns when you are considering making the jump. Don’t let this overwhelm you into staying away from the cloud altogether. Security is always job zero. So make sure you have a clear overview of which data needs to be stored in the cloud exactly. Consider the best location for each type of data. Then you can work out your strategy on how to ensure the security of your data. You can absolutely stay compliant without any loss of efficiency or speed. With AWS, you have access to compliant and secure cloud infrastructure. So don’t let compliance anxiety stop you from migrating to the cloud.

#4 Lack of legacy

Many business processes are embedded in legacy systems. They are by far the most important systems, and the backbone of an organization. Migrating these systems to the cloud might be the biggest challenge. Processes can’t stop or be interrupted for too long without significant loss of productivity. Map out your essential processes and define the possible cloud solutions for the immediate and the more distant future. While transitioning, or maybe even in the long term, a hybrid cloud structure might be the solution. That way you can start your cloud migration immediately while combining the legacy system and cloud applications. In time, you can gradually move your entire operation to the cloud.

#5 Resistance to change

Implementing new tools is one thing. But if you do this without paying attention to user adoption, it will fall flat. Change is difficult. People are creatures of habit. Accepting new technology is no exception. To maximize your users’ cooperation and acceptance, it’s important for them to contribute and weigh in during the design process. If you involve your colleagues from the very start, they will feel much more invested in the new way of working. Not only that, they will look at each development phase from the specific point of view of their tasks. That way you make sure that no person or task gets overlooked and they will embrace the new way of working.

Have you encountered some of these challenges in your company’s cloud migration? Do you want to get ahead of them? Or do you just want to spar with an official Next Generation AWS Managed Service Provider Partner? Contact us at Cloudar, no strings attached. Let’s talk!

The post Growing pains: 5 Key Challenges of AWS Cloud Migration appeared first on Cloudar.

“We want to cut costs”

Aren’t we all concerned about our bottom line? When we research a new tool or solution, budget will always be one of the main deciding factors. AWS prides itself on reducing operational costs by 51%. Eliminating costs for hardware and maintenance will significantly limit your recurring data storage costs. Is your business prone to high peaks and off-seasons? With cloud-based computing, you can increase your capacity (and the subsequent costs) when you need them and scale back when business is slow. 

“We want to increase our flexibility”

Technology has supercharged the rate at which businesses evolve, so being able to respond swiftly to market changes is integral to running a successful business. Does your software allow you to scale or pivot with minimum friction and maximum flexibility? A smart cloud migration & configuration can help you to boost productivity, enable more efficient data storage, and facilitate collaboration. 

“We want a solution that is safe and secure”

AWS has several high-profile clients who can’t afford to compromise on data safety. And you will benefit from those security needs. Enjoy AWS’s state-of-the-art data security when you do your cloud migration. Have you considered what will happen to your data in case of a natural disaster? A fire or a flood on-premise could be devastating and keep you offline for weeks, if not months. In the Cloud, data is stored and backed up across several data centers. So no matter what happens, you know that all vital information will stay safe and secure.

What is your reason for considering the Cloud? Get in touch for a personalized assessment.

The post 3 Business Drivers for Cloud Migration According to Our Customers appeared first on Cloudar.

MYTH 1: cloud is more expensive than a data center

Yes, if you put the price of a cloud solution next to the price of a data center, the cloud will be more expensive. But you are comparing apples and oranges. Once you take the total cost of ownership into account, you will see that the cloud is cheaper than an on-premise solution. Another major benefit: cloud offers you insights into your end-to-end. Its transparency helps you to optimize your solution and cut unnecessary costs. Finding out the true cost of your on-premise solution can be difficult.

Source: AWS

MYTH 2: the Cloud is not secure

AWS has a couple of very high-profile customers. The company simply can’t afford any security mishaps. How is this good news for you? Easy: every single AWS customer benefits from that need for rigorous safety mechanisms. Of course, your company also has its part to play. Security and compliance are a shared responsibility between AWS and your organization. AWS operates, manages, and controls components, from the host operating system and visualization layer to the physical security of the facilities in which the system operates. Your job is to ensure the security of the guest operating system (including updates and security patches), other associated application software, and the AWS-provided security group firewall. Some services require more responsibility on the client’s side than others. You can choose and integrate your services based on how comfortable you are with your share of responsibility in keeping everything secure. Maximum flexibility, maximum comfort.

MYTH 3: AWS has access to my data

We understand that privacy and full control over your data are important to you. That’s why we provide APIs for you to configure access control permissions for any of the services you develop or deploy in an AWS environment. 

Here are the services we offer to help you access, encrypt, and log data:

• AWS Identity and Access Management
• AWS Organizations
• AWS CloudTrail

As for us? We do not access or use your content for any purpose without your consent. We never use your content or derive information from it for marketing or advertising. Another concern is the storage of data. You choose where and how your data is stored. With the ability to replicate and back up content in multiple AWS regions. Oh, and you also have full control over how your content is secured. We offer strong encryption, and you can manage your own encryption keys. 

MYTH 4: I’ll be stuck with my cloud vendor

It’s true. Choosing a vendor is a commitment, but it offers enormous flexibility in services and solutions. And moving data cloud-to-cloud is a lot easier than moving information between legacy systems.  

Here are three ways our customers find freedom in cloud technology:

• No long-term commitments: customers can adopt cloud tech on their own terms. AWS customers only use the services they find valuable.
• Customer’s choice: our customers are free to use alternatives to proprietary tools, along with a range of ‘as-a-service’ capabilities. They choose how to invest and create their ideal ecosystem.
• Moving into and out of AWS: AWS services are built to support both migrations into and out of AWS, and we provide many tools and documented techniques to make it easy to do both. 

While some say that combining technology stacks offers you the best of both worlds, we believe the opposite. Learning how to get the most out of a single technology stack will give you a major business advantage.

MYTH 5: The Cloud is killing IT jobs

Au contraire. Cloud helps IT professionals to thrive. When companies transition from on-premise services to the cloud, IT administrators don’t automatically lose their jobs. Most of them transition into the role of a trusted advisor and technical solutions facilitator. 

Cloud computing is growing rapidly at around 17% per year. It is projected to become an 800 billion industry by 2025. That kind of growth requires skilled technical professionals. The World Economic Forum estimates that cloud technology will generate 133 million jobs by 2022.

Do you have any other concerns? Would you like to talk about what cloud computing can do for your business? I’d be happy to chat! Contact me today for a free introductory call.

The post Hey, have you heard? 5 common myths about cloud technology appeared first on Cloudar.

One of the key take-aways, is to travel in good company. Good travelling buddies make you strong and resilient in order to overcome roadblocks. They make you persistent. I have had the joy and luck to travel in very good company the past few years.

Today is the day to stop at a Milestone and enjoy the scenery.

At Cloudar, we are glad to announce that we officially have achieved our AWS Migration Competency Delivery partnership.

With this competency, Cloudar has proven to be a reliable partner and expert for Customers to assist and guide them in their Digital Migration journey.

It will get its place besides all of the other AWS competencies we already achieved.

Look at it as climbing a mountain, you have to be well-prepared for it , and well-equipped. But it will still take quite some effort and make you sweat. But when you arrive at your goal, you will see the clear perspective of where you’re going to. New roads reveil.

Today, with this competency, and with strong support of AWS, we are ready to even help our customers even more with reaching their goals and become a trustworthy travel companion in their Digital Migration Journey.

Maybe the travel metaphor seems less relevant in these times of staycations, but it is the journey itself and your next target that counts. It doesn’t always need to be far, just enjoy the road and your next success.

So, I think we arrived at a conclusion : you now know that Cloudar is an AWS Migration delivery partner ready to roll, staycations can be quite enjoyable too, and I also believe we even have got the people, process, tooling triangle covered along the way…

Please allow me to say special thanks to the travel companions that made it happen : AWS & AWS Partner Migration team, Cloudar Teams and especially our Customers ! Thank you.

Please consult the Public Migration Customer cases on our website and reach out.

The post Great News : Cloudar is an official AWS Migration Competency Delivery Partner ! appeared first on Cloudar.

In IT we have learned to embrace change and new technology. We all need to change if we want our businesses to stay relevant, don’t we? But change, and certainly positive change, doesn’t always happen overnight. It is a process in which we will need to make decisions that will define the desired output.

Since systems, including people and organizations, are interconnected, we have to approach change holistically to make it happen. Therefore, processes exist to guide you during the transformation and help you to arrive at the desired state. In our digital transformation journey and in Cloud Migration it’s not different.

Our approach towards Cloud Migration is a tried and true, structured approach, in which we will first prepare ourselves, then acquire the right methodologies and tools to lay solid foundations and from there on, start practicing and building. During this execution phase, we will iteratively ‘Slice and Dice’ your workloads and business capabilities into reasonable and practical actionables, following an agile approach. Practice makes perfect and before you know it, you’re migrating at scale.

In this perspective, the setup of a highly efficient Migration Factory is utterly important. Here we will make use of the technology and tools at hand to facilitate and automate the migration as much as we can. You can for example make use of CloudEndure, which delivers flexible and innovative migration solutions. Cloudendure offers Continuous block-level replication, cross-infrastructure machine conversion, does automated orchestration and this with a minimal footprint.

Once you’re in the AWS cloud, possibilities to improve, optimize and reinvent are numerous.

Business capabilities will be transformed with available Cloud-Native Services and Technology.

Choosing a partner or MSP that guides you and will help you make the right decisions during the journey, is a direction that you should make as early in the process as possible. It’s an important decision, because once you started your Cloud journey, you will start to see opportunities in which a trusted advisor is a valuable resource to ensure you make the right choices.

Do you want to know where you are in your Cloud journey or where to get started ? Contact your partner for an AWS Migration Readiness Assessment or a AWS Well-Architected Review. It’s a small step, but an essential one to keep your business moving forward in a fast-pace world.

The post Slice and Dice your Cloud Migration and Keep Moving appeared first on Cloudar.

Luckily this does not have to be: VMware Cloud on AWS can help you with the intermediate step of getting your on-premise VMware environment closer to AWS. And this is just one of the many use-cases of the VMware Cloud (VMC) on AWS solution.

What is VMC on AWS?

It is a VMware Software Defined Data Center (SDDC) running on top of AWS EC2 bare-metal instances. VMware sells this solution, operates it, and supports it together with its partners. The same building blocks are used as in an on-premise VMware environment. Therefore, the VMC on AWS provides the same operational consistency as an on-premise VMware SDDC.

Your on-premise environment can be linked with the VMC on AWS environment to easily go back and forth with your virtual machines. On the other side, the VMC on AWS environment is close to the rest of the AWS services and allows your virtual machines in this environment to interact with these services with low latency.

When to use VMC on AWS?

As the introduction stated, VMC on AWS can be used for migrating your VMware workloads to AWS. Scenarios where this can be applicable are simply moving to the cloud. This allows you to reduce the on-premise footprint and get you closer to native cloud services. This migration scenario can also serve as an intermediate step. Imagine your current contract with your datacenter provider is expiring, but the new location is not yet decided. In that case, VMC on AWS can provide you with the temporary infrastructure to keep everything running with minimal setup effort.

VMware Cloud on AWS – Usecases

But what if your on-premise environment runs just fine but you need extra capacity for some time? You can extend to VMC on AWS and run your dev/test workloads or extra on-demand workloads during peak loads. The use of NSX allows for extending your L2 networks so you don’t even need to change your IP addresses. This can be a solution for when capacity planning was wrong and the necessary hardware is not in-place to cope with the higher-than-expected demand.

Similar to extending your datacenter, you could also use the solution as a second datacenter for when things go bad in your primary. You can run a minimal cluster that has enough storage in combination with VMware SRM and use this environment as a disaster recovery site. During a disaster, you could scale out your VMC on AWS cluster in minutes if there would be insufficient CPU or memory. This scenario in combination with the previous one, where you would extend your datacenter and run your dev/test environment on VMC on AWS, can be a very powerful one. You can still decide whether you power off your dev/test environment during a disaster, but you do not really have to since hosts are added within minutes if necessary.

I have mentioned the dev/test workloads several times already, and when building applications this flexibility of adding and removing hosts can be very handy. It prevents having idle resources in-between projects by scaling down the amount of hosts where possible.

How to use VMC on AWS?

You can already start with VMC on AWS with just one host. The Single Host SDDC is a starter configuration limited to 30 days. This offers a lower-cost entry point for customers. The Single Host SDDC should be upgraded to a 3-host SDDC to retain the data. Otherwise, after 30 days, the single host environment is deleted. In terms of support, you get the same services from VMware and the partner as for a 3-host SDDC. However, no SLA is given for the Single Host SDDC as there is no redundancy for component or host failure and you may lose your data.

A production cluster has a minimum of 3 hosts. This allows you to choose RAID 1 for your virtual machines, with a “failures to tolerate” of 1. If you want RAID 5 or RAID 6 for your virtual machines, VMware requires you to scale to 4 or 5 hosts respectively. In general, the more hosts in your cluster, the better optimized your storage will be. Moreover, if you need a VMC on AWS environment that can survive a complete Availability Zone (AZ) failure, then you can choose for Multi-AZ deployment during setup. This will deploy a stretched cluster over two AZ’s with a vSAN witness in another AZ. Each AZ will require a minimum of 3 hosts so this brings the minimum number of hosts in a Multi-AZ deployment to 6 hosts.

VMware Cloud on AWS – Multi-AZ deployment

When setting up your SDDC, you can choose between two host types, either a i3.metal or r5.metal. The main difference between the two is the storage architecture. The former has 8 local NVMe hard disks and offers better performance but a fixed compute/storage ratio, while the latter has EBS-backed storage (Elastic Block Storage). This allows storage to range from 15 TiB to 35 TiB per host and has the advantage that when a host fails, the EBS volumes can be re-attached to the new host, and thus reducing the rebuild time. Other differences between the two host types are CPU and memory. The r5.metal has slightly higher specifications. However, the main criteria for choosing between the two will mostly be storage related.

Additional to the operational consistency to an on-premise VMware SDDC, the VMC on AWS SDDC has some neat features to increase flexibility. You can add/remove hosts to/from your cluster manually within minutes, but you can also configure Elastic DRS. This feature allows for automatic scale up or down by using the resource management features from vSphere. When a certain capacity threshold is reached, eDRS will add a host to your cluster. It would take around 10-15 minutes to add a host to an existing cluster. This will add both compute (CPU/memory) and storage capacity. eDRS will also scale down your cluster when it is lightly loaded. The process of adding a host to the cluster, either manual or using eDRS, is depicted below:

VMware Cloud on AWS - Automatic Cluster Configuration: adding a host

Furthermore, VMC on AWS can react quickly when a component or host fails. It will insert a new server into your cluster and vSphere HA will restart the VM's which were running on the failed host. In the meantime, the data from the failed host is rebuilt or moved to the new host. The failed host is removed from the cluster when this process is done, resulting in a healthy cluster with still the same amount of hosts as before the component or host failure occurred.

VMware Cloud on AWS - Self Healing: recovering from a host failure

As VMware manages this environment for you in terms of infrastructure, they use this flexibility as well during patching of your hosts. At the beginning of the patch window, they insert an extra host to your cluster without any additional cost. This allows them to patch all the hosts while you still have all resources available, even if one of your regular hosts is in maintenance mode.

How to leverage AWS services?

So your workload is now running on VMC on AWS, but how do you connect to AWS services? During set up of your SDDC, you connect to an AWS account and select a VPC and subnet. The setup will deploy several Elastic Network Interfaces (ENI) to your VPC, of which one will be active. These ENI's have a maximum throughput of 25Gbps. You can then connect to AWS services privately using this VPC connectivity. You could set up VPC endpoints for connecting to public AWS services without going over the internet.

The post How to get closer to the cloud: VMware Cloud on AWS appeared first on Cloudar.