Answers: <p>Solution was pretty simple: you have to choose ARM architecture on the first step, AMI selection. Accustomed to choose x86 architecture, I didn't pay attention to that radio button. Also I didn't bother to hover over the forbidden icon on the first column in the image posted on question, which clearly stated what was the problem:</p>
  <p><a href="https://i.sstatic.net/K3gzT.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/K3gzT.png" alt="enter image description here" /></a></p>
  <p>So solution is to select ARM on the previous step:</p>
  <p><a href="https://i.sstatic.net/uudR9.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/uudR9.png" alt="enter image description here" /></a></p>
  
Answers: CC BY-SA 4.0
Answers: 2020-11-05T15:40:18.460Z
Answers: 2020-11-05T15:40:18.460Z
Answers: FLC
Body: <p>According to the <a href="https://aws.amazon.com/blogs/aws/new-t4g-instances-burstable-performance-powered-by-aws-graviton2/" rel="nofollow noreferrer">blog post</a> since september/2020 and up to december/2020 instance type t4g will be available. I'm trying to create a machine, on one of the right zones (Oregon) according the FAQ, and using the right AMI, also according to the <a href="https://aws.amazon.com/ec2/faqs/#t4g-instances" rel="nofollow noreferrer">FAQ</a></p>
  <p>So why I cannot choose those machines?</p>
  <p>As you can see on the screenshot, t3a are eligible, but all t4g not:</p>
  <p><a href="https://i.sstatic.net/ZIKv8.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/ZIKv8.png" alt="enter image description here" /></a></p>
  
Tags: <amazon-ec2>
Title: AWS t4g instance type not eligible
UserDisplayName: FLC
ThreadText: # AWS t4g instance type not eligible
  
  (Asked by: username_0 on 2020-11-04)
  
  According to the [blog post](https://aws.amazon.com/blogs/aws/new-t4g-instances-burstable-performance-powered-by-aws-graviton2/) since september/2020 and up to december/2020 instance type t4g will be available. I'm trying to create a machine, on one of the right zones (Oregon) according the FAQ, and using the right AMI, also according to the [FAQ](https://aws.amazon.com/ec2/faqs/#t4g-instances)
  
  So why I cannot choose those machines?
  
  As you can see on the screenshot, t3a are eligible, but all t4g not:
  
  [![enter image description here](https://i.sstatic.net/ZIKv8.png)](https://i.sstatic.net/ZIKv8.png)
  
  **Tags:** amazon-ec2
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2020-11-05. Score: 2 | Accepted answer
  
  Solution was pretty simple: you have to choose ARM architecture on the first step, AMI selection. Accustomed to choose x86 architecture, I didn't pay attention to that radio button. Also I didn't bother to hover over the forbidden icon on the first column in the image posted on question, which clearly stated what was the problem:
  
  [![enter image description here](https://i.sstatic.net/K3gzT.png)](https://i.sstatic.net/K3gzT.png)
  
  So solution is to select ARM on the previous step:
  
  [![enter image description here](https://i.sstatic.net/uudR9.png)](https://i.sstatic.net/uudR9.png)
  
  
  ---
  
  