How to List Edera AMIs
Overview
This guide shows you how to list all available Edera AMIs (Amazon Machine Images) in your AWS environment. This command also serves as a verification that your AWS account has been granted access to the Edera AMIs.
Prerequisites
- AWS CLI installed and configured with appropriate credentials
- Your AWS account has been granted access to Edera AMIs (completed during onboarding)
Command
Use the following AWS CLI command to list all Edera AMIs:
aws ec2 describe-images \
--owners 207567768011 \
--query 'reverse(sort_by(Images[*].[CreationDate, ImageId, Name, State], &[0]))' \
--output tableUnderstanding the Command
--owners 207567768011: Filters to show only AMIs owned by Edera (AWS Account ID: 207567768011)--query: Sorts results by creation date (newest first) and formats the output--output table: Displays results in a readable table format
Expected Output
You should see a table showing:
- CreationDate: When the AMI was created
- ImageId: The unique AMI identifier (e.g., ami-xxxxxxxxx)
- Name: The descriptive name of the AMI
- State: The current state of the AMI (should be “available”)
Example output:
| DescribeImages |
+---------------------------------------------------------+
| 2024-01-15T10:30:00.000Z| ami-0123456789abcdef0| edera-runtime-v1.2.3| available|
| 2024-01-10T14:20:00.000Z| ami-0987654321fedcba0| edera-runtime-v1.2.2| available|Troubleshooting
No AMIs Listed
If the command returns no results:
- Verify account access: Contact support@edera.dev to confirm your AWS account has been granted access
- Check AWS credentials: Ensure your AWS CLI is configured with the correct account credentials
- Verify region: Make sure you’re querying the correct AWS region where AMIs were shared
Permission Denied Error
If you receive a permission denied error:
- Verify your AWS credentials have the necessary EC2 permissions
- Ensure the
ec2:DescribeImagespermission is included in your IAM policy
Next Steps
Once you can successfully list the Edera AMIs:
- Note the latest AMI ID for your deployment
- Proceed with your Edera installation using the identified AMI
- Reference our deployment documentation for next steps
Need Help?
If you encounter issues or have questions about AMI access:
- Email: support@edera.dev
- Review our other Knowledge Base articles
Last updated on
