Welcome to your first step towards cloud efficiency and savings with Infrastructure Optimizer!
Before you begin, use this checklist to confirm your environment satisfies the specifications required to operate Infrastructure Optimizer.
Network
| Anchor | ||||
|---|---|---|---|---|
|
...
Component
...
Requirements
...
VPC
...
By default, Infrastructure Optimizer schedules workload workers to run in private subnets to protect them from direct external accesses.
Run the following command to ensure that the AWS VPC where Infrastructure Optimizer will run has at least one private
...
subnets with public NAT Gateways:
| Code Block | ||
|---|---|---|
| ||
aws ec2 describe-subnets --filter Name=vpc-id,Values= |
...
<vpc_id> --query 'Subnets[?MapPublicIpOnLaunch==`false`].SubnetId' |
...
NAT Gateway
Has a NAT Gateway with public connectivity. Verify with this command:
...
| language | bash |
|---|
...
aws ec2 describe-nat-gateways --filter Name=vpc-id,Values= |
...
<vpc_id> --output json | jq '.NatGateways[] | {NatGatewayId, SubnetId, ConnectivityType}' |
These commands will provide a list of private subnets suitable for running the Infrastructure Optimizer workload workers.
If no private subnets exist, follow the AWS documentation to create a private subnet and a public NAT Gateway.
Security
| Anchor | ||||
|---|---|---|---|---|
|
...
Component
...
Details
...
SSH Key
...
This will be used to attach to the Management Server.
...
Trusted Certificate
...
A pre-provisioned, user-managed SSH key pair is required to access the Infrastructure Optimizer head node. If needed, 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 be needed.
Compute
| Anchor | ||||
|---|---|---|---|---|
|
...
Component
...
Requirements
...
Operating System
...
Infrastructure Optimizer runs on the following OSes:
Rocky Linux
CentOS
Permissions
| Anchor | ||||
|---|---|---|---|---|
|
...