Advanced Topics and Troubleshooting
Last updated
The CLI can automatically handle the list of things below in case of SSH permission issues:
VPC creation/configuration
Subnet management
Internet gateway attachment
Route table configuration
Security group rules
Firewall settings
The CLI manages SSH access by:
Creating SSH key pairs
Configuring security groups
Setting up instance metadata
Managing key permissions
Handling different OS users
Single region deployment per configuration
No direct support for:
Multi-cloud deployments
Azure resources
Custom VPC peering
Advanced networking features
No support for stateful workloads
Relatively static Ansible integration
Resources must be defined in .cloud file
Manual changes to resources may cause sync issues
Key pairs are managed automatically
Some resource types require manual cleanup
Use different names for all resources within each .cloudfile
Separate configurations by deployment zone
Document file references
Maintain backup copies
Convert Command Fails
Solution: Ensure you're providing the correct path and the .cloud file exists.
Network Access Issues
Solution:
Check security group rules
Verify instance has public IP
Confirm SSH key permissions
Check OS user configuration
Permission Issues
Solution:
Verify AWS credentials
Check IAM permissions
Ensure role/policy attachments
Infrastructure Errors
Resource creation failures
Network configuration issues
Permission problems
Container Errors
Image pull failures
Configuration issues
Resource constraints
Configuration Errors
Ansible playbook failures
Package installation issues
Service configuration problems
Check the logs
Verify credentials
Validate configurations
Check resource availability
Review network settings
Multi-cloud support
Azure integration
Advanced networking features
Enhanced state management
Error Mapping
Last updated
Error: No .cloud file found in the specified pathError: Could not establish SSH connection to instanceError: AWS API call failed: AccessDenied