Your EC2 instance is assigned a fixed public IP from a list of Elastic IPs. But Amazon charges a considerable amount of money for the Elastic IP. Is there a way to automatically update the IP address of a DNS record defined in Amazon Route53 from the EC2 instance? Yes, there is, and it’s not hard. You can write a “bootstrap” script that is executed when the instance is started. The script will update the public DNS record according to the public IP of the instance.

1. Allow EC2 changing Route53 records

Detailed instructions for creating an IAM role

Log into your AWS management console.

Proceed to AIM (“Identity and Access Management”). Click on Roles. Click on Create role.

Select AWS service as the trusted entity type.

Select EC2 for the Use Case, then select EC2 (“Allows EC2 instances to call AWS services on your behalf”)

In the Permission policies, select AmazonRoute53FullAccess.

Click on Next: Tags (optional step, you can add tags to organize and manage your role).

Click on Next: Review.

Name your role. Choose a name that makes sense for its purpose, like EC2Route53UpdateRole.

(Optional) Add a description that explains the role’s purpose, like “Allows EC2 instances to update Route 53 DNS records.”

Review your choices and click on Create role.

Finalize and use the Role

After creating the role, … >>> Click to read the full post...

Here is how you can accelerate MacOS running in VMWare virtual machine in Windows 10/11.

The key performance factor: MacOS VM must run with “Virtualize Intel VT-x/EPT or AMD-V/RVI” enabled, otherwise it will run slowly.

You may not be able to enable this checkbox if your processor does not support virtualization. You need to consult with your CPU documentation to figure that out. For example, for Intel i7-10700K, we can see that the virtualization is supported:

If your CPU supports virtualization, you still may experience the following error message when enabling the needed feature in VMWare:

If it happens, do the following:

Reboot, go to BIOS and make sure that:

• Intel Virtualization is enabled
• Intel VT-d is enabled

Boot into Windows.

Under Start, search for “Core isolation”, and turn it off:

Under Start, search for “Turn Windows features on and off”, and then:

• disable “Hyper-V”
• disable “Virtual Machine Platform”

Reboot.

Go to ‘cmd’, and run the following command: systeminfo

At the very end of the report, if you see this:

then you are good to go.

However, if you see this:

then run ‘cmd’ as administrator, and run the following command:

bcdedit /set hypervisorlaunchtype off

Reboot.

Once done, make sure that the virtualization under ‘systeminfo‘ is reported as: