Requirements
The baseline supported instance type on Amazon Web Services is the r7a.xlarge. This gives the best mix of performance to cost for running Anchore Enterprise in alignment with the supported system limits.
For more information on Amazon EC2 Instance types Please review the following links
- Memory Requirement - AECI requires a minimum of 32 GB of memory to operate.
- Disk Requirement - AECI requires a minimum of 128 GB of disk space for root volume and 1 TB for data volume to operate.
- Note: The data volume by default will not delete on termination of your AMI.
- CPU Requirement - AECI requires a minimum of 4 vCPU to operate.
License
The Anchore Enterprise Cloud Image requires a valid license entitlement to operate. The license is provided by Anchore during the purchase process. The license file is required to be uploaded via the Cloud Image Manager during the initial setup. Please have it available before starting the installation process.
EC2 Key Pair type
Anchore Enterprise Cloud Image is running with FIPS enabled. When creating your Key Pair, you must use an RSA key. The ED25519 key will be rejected as a non-FIPS-compliant algorithm.
Please review the AWS documentation on using Amazon EC2 Key Pairs
Security Group
The Anchore Enterprise Cloud Image requires the following ports to be open in the security group:
- TCP 22 - SSH
- TCP 443 - HTTPS
- TCP 8443 - Grafana
Please review the AWS documentation on Security Groups.
Terminals
Please review the Best Practices for the Cloud Image Manager for the recommended terminal applications to use.
Getting Started
To launch the Anchore Enterprise Cloud Image AMI, please refer to the AWS documentation on Launch an Amazon EC2 instance.
You may also want to review the AWS guide for how to Connect to your EC2 instance.
A quick Demo on getting started with Anchore Enterprise Cloud ImageOnce the instance is launched, please review the Cloud Image Manager documentation for the next steps on Accessing the Cloud Image Manager. The Cloud Image Manager will walk you through the preflight checks, configuration, and management of your Anchore Enterprise Cloud Image deployment.
Operations
With AECI up and running, there is some limited feeding and watering required. You’ll want to consider the following activities:
Backups
It is important that you have a backup and restore strategy in place to protect your data. Cloud Image Manager will prompt you to create a snapshot prior to upgrading your Anchore Enterprise Cloud Image or expanding your disks. It is also reasonable for you to consider using AWS Backup and/or creating snapshots of your EBS volume on a regular basis:
Please refer to the AWS documentation on AWS Backup and Amazon EBS Snapshots.
Disk Space
During the course of using the product, you may wish to expand the size of your disks. It is strongly recommended that you create a snapshot of your EBS volume prior to expanding your disks.
Please refer to the AWS documentation on Extend or modify disk volume
Once you have expanded your disk, you will need to resize the filesystem to take advantage of the additional space. Cloud Image Manager provides a utility to resize the filesystem. Please refer to the Cloud Image Manager Configuration Disk Expansion for more information.
Upgrading
Occasionally, Anchore will release updates to the Anchore Enterprise Cloud Image and the subsequent version of Anchore Enterprise shipped with it. The Cloud Image Manager will provide you with upgrades that are available and allow you to determine when you want to upgrade. It is strongly recommended that you create a snapshot of your EBS volume prior to upgrading your Anchore Enterprise Cloud Image.
Please refer to the Cloud Image Manager upgrade documentation for more information.
Getting Support
During operation of Anchore Enterprise Cloud Image, you may require support from Anchore Customer Success. The Cloud Image Manager provides you with a seamless way to generate a support bundle and upload it to Anchore.
Please refer to the Cloud Image Manager Support documentation for more information.