In a previous post, I shared a bash script that enables you to effortlessly create an Amazon Machine Image (AMI) from an EC2 instance in AWS. The bash script introduced in today's post allows you deregister an AMI and delete all associated snapshots in AWS.

I wanted to let you know that we have added a new model to 4sysops AI called Perplexity PPLX 70B Online. What sets this model apart is that it conducts an online search for every query and summarizes the content from the first few result pages. This approach has the advantage of providing access to timely information.

After announcing the free use of ChatGPT 4 on 4sysops, I added four more models to 4sysops AI. Google Gemini Pro, Anthropic Claude 3 Opus, Mistral Large, and Meta Llama 2. Using multiple model increases  the probability of receiving accurate information. In case one model fails to deliver a satisfactory response, you can seek alternative solutions. All models are continuously updated with our latest IT content and thus have no cutoff date. The usage of 4sysops AI is currently free.

In my previous post, I explained how you can quickly allocate an Elastic IPv4 address and associate it with an EC2 instance. As Amazon has recently started charging for in-use IPv4 addresses, you might want to consider switching to IPv6. Using the AWS Management Console to assign an IPv6 to an EC2 instance is not really straightforward. Several AWS network components must be correctly configured to make IPv6 work. The bash script introduced here checks all components, adds any missing pieces, and then assigns the IP to an EC2 instance.

In previous articles, I explained how to create an AMI from an EC2 instance and then launch the instance with scripts. Next, you probably want to assign an Elastic IP (IPv4 address) to the instance. In this post, you will learn how to allocate, release, associate, and disassociate an Elastic IP with the AWS CLI and bash scripts.