Not able to create an EC2 instance in free tier

I apologize for the inconvenience you're experiencing. The "AMI no longer exists" error typically occurs when the Amazon Machine Image (AMI) you're trying to use has been deprecated or removed. Here are some suggestions to resolve this issue:

1. Refresh AMI list: Try refreshing the AMI list in the EC2 launch wizard. Sometimes, the list may not be up-to-date.

2. Choose a different AMI: Select a more recent Amazon Linux AMI. AWS regularly updates their AMIs, so choosing a newer version might resolve the issue.

3. Check region availability: Ensure that the AMI you're trying to use is available in the us-east-1 region. Some AMIs might be region-specific.

4. Verify Free Tier eligibility: Make sure you're selecting an instance type that's eligible for the Free Tier, such as t2.micro or t3.micro (depending on the region).

5. Use AWS Marketplace: You can try finding a suitable Amazon Linux AMI through the AWS Marketplace, which often has the most up-to-date images.

6. Check account status: Ensure your AWS account is in good standing and fully verified, as some features may be limited for new or unverified accounts.

If you continue to face issues after trying these steps, it might be helpful to contact AWS Support for further assistance. They can provide more specific guidance based on your account status and the exact AMI you're attempting to use.

Remember, while troubleshooting, always make sure you're selecting options that are compatible with the Free Tier to avoid unexpected charges.
Sources
problem in creating Amazon EC2 instance | AWS re:Post
Trying to Create a Free Tier EC2 Instance, but I Keep Getting the Error: 'This account is currently blocked and not recognized as a valid account.' | AWS re:Post

Hi, This issue typically occurs because Amazon regularly updates their AMIs, and older AMI IDs become obsolete. To resolve this, start by accessing the EC2 Dashboard and clicking "Launch Instance." Under "Quick Start," select the current Amazon Linux 2023 AMI, ensuring you choose the 64-bit (x86) architecture. Make sure to select either t2.micro or t3.micro instance types, which are free tier eligible. If the issue persists, try clearing your browser cache or use the AWS CLI command to get the latest AMI ID. For detailed guidance, you can refer to the AWS documentation at https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/finding-an-ami.html.