Skip to main content

Extend your datacenter with Confidence using VMware Cloud on AWS (Part-1)

As per Gartner, 100 percent of Fortune 500 and Fortune Global 100 companies use VMware, and more than 500,000 customers have saved billions of dollars worldwide. Approximately 85 percent of all virtualized applications run on VMware. 

Many companies still rely on their own data centers and manage their IT infrastructure with long-standing, proven solutions from VMware. But many would also like to benefit from the advantages of a public cloud solution, such as high scalability, reliability, and flexible costs. This is made possible with VMware Cloud on AWS. It enables companies to bring their vSphere-based workloads into the public cloud and combine them with modern services from AWS, such as S3 object storage or an RDS database service, if required.

Why move to Cloud: 

Common scenarios include 

1. Company strategy to implement cloud-first mandates
2. Aging infrastructure or major hardware refreshes
3. Expiring contracts or co-location lease expiration
4.     Accelerate migrations with operational consistency and flexibility
5.     Reduce costs while scaling global business demand
6.     Modernize workloads and increase innovation with cloud-native services 

There are also those who prefer to use the overhead devoted to managing datacenters to focus on building applications. According to a recent survey, on average, 40% of server hardware is over three years old — and respondents whose entire service fleet is three-plus years old say they have higher costs and slower time-to-market as a result.

What customer Say: 

 "Rather than datacenters, we are moving toward centers of data, placed and optimized to provide the most business value. This also expands the role and responsibilities of central IT to one of a business enabler, rather than a purveyor of equipment and software. "

What is VMware Cloud on AWS: 

VMware Cloud on AWS brings VMware’s enterprise-class SDDC software to the AWS Cloud with optimized access to native AWS services. VMC is an innovative service built on a joint engineering relationship between AWS and VMware powered by VMware Cloud Foundation, VMware Cloud on AWS integrates VMware's compute, storage, and network virtualization products (VMware vSphere, VMware vSAN, and VMware NSX) along with VMware vCenter Server management, optimized to run on dedicated, elastic, bare-metal AWS infrastructure and continue innovating your business.  

Why customer should use VMware Cloud on AWS?

AWS is VMware's preferred public cloud partner for all vSphere-based workloads. VMware Cloud on AWS provides customers with consistent and interoperable infrastructure and services between VMware-based datacenters and the AWS cloud, which minimizes the complexity and associated risks of managing diverse environments. 

1. Customer is already pursuing a cloud strategy
2. Expand the VMware environment into the cloud
3. VMware Cloud on AWS seamlessly moves the traditional workloads into VMware Cloud on AWS
4. Customer can continue to use VMware technology that is proven in the On-premise environment
5. Park the VMware based workloads in the Cloud and plan for the modernization at the pace with which the company can adapt

You set the pace: modernize VMware workloads in simple steps

Lift & shift: Migrate your VMware workloads to the AWS Cloud. This allows you to continue operations seamlessly without changing or adjusting workloads.

Enhance: Add >150 native AWS services such as S3 object storage or the RDS database service to existing workloads.

Refactor: Completely transform your traditional applications on AWS into native cloud solutions. Do so according to your needs and at your own pace.

To be continued … part 2 – Migration strategy 

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N