Welcome to Infrastructure Optimizer! 🎉 👏
We are excited to help you to maximize your cloud resource efficiency and savings!
Before you begin, use this checklist to confirm that your environment satisfies the specifications required to operate Infrastructure Optimizer.
The pre-check commands will require the IAM principal to have at least the ec2:Describe* permissions
Network
By default, Infrastructure Optimizer schedules workload in private subnets to protect them from direct external accesses.
Use the following commands to ensure that the AWS VPC where Infrastructure Optimizer will run has at least one private subnet with public NAT Gateways.
Check private subnets that are suitable for running the Infrastructure Optimizer workload Workers:
aws ec2 describe-subnets --filter Name=vpc-id,Values=<vpc_id> --query 'Subnets[?MapPublicIpOnLaunch==`false`].SubnetId'
Check whether there is a public NAT Gateway attached:
aws ec2 describe-nat-gateways --filter Name=vpc-id,Values=<vpc_id> --output json | jq '.NatGateways[] | {NatGatewayId, SubnetId, ConnectivityType}'
If no private subnets exist, follow the AWS documentation to create a private subnet and a public NAT Gateway.
EKS only: the Infrastructure Optimizer must run in the same VPC as the EKS cluster
Security
A pre-provisioned, user-managed SSH key pair is required to access the Infrastructure Optimizer Management Server.
OPTIONAL: Follow the AWS EC2 documentation to generate a SSH key pair.
For environments with existing PKI setup, the x509 certificates, private key, and optionally, intermediate chain certificates and CA certificates will also be needed.
Compute
Infrastructure Optimizer runs on the following OSes:
Rocky Linux
CentOS
Permissions
Installations and Deployment
The following file contains the minimum IAM permissions required by the AWS IAM principal used to install Infrastructure Optimizer:
EC2 Instance Profiles
The Infrastructure Optimizer Controllers and Workers require a set of IAM permissions to manage and scale your workloads efficiently. Use this CloudFormation template to create the EC2 instance profiles.
When completed, the roles and instance profile ARNs outputs by CloudFormation will be needed for subsequent installation steps.