Troubleshoot Self-hosted Environments on AWS
This feature is currently in private beta. If you wish to participate, you must first request access. A member of our team will follow up to discuss the steps to get the feature enabled.
The following steps assume you have already gone through the steps to get started and have attempted to create a Self-hosted Environment.
Preflight Check
As soon as you create your Self-hosted Environment, a preflight check will automatically run to ensure you have the access and permissions necessary as set by your IAM User policy to provision the environment in your AWS cloud account.
A preflight check is run before the environment is created. You can check this in the CLI.
- CLI
- Use the
meroxa environment describe
command to see the preflight check run on your environment.
$ meroxa environment describe my-env
UUID: 1234-1234-1234-1234-1234-1234
Name: my-env
Provider: aws
Region: us-east-1
Type: self_hosted
Created At: 2022-03-24 00:54:27 +0000 UTC
Updated At: 2022-03-24 00:54:28 +0000 UTC
Environment Status: provisioning
Environment Status Details: provisioning
Preflight Checks:
AWS EC2 Permissions Status: success
AWS EKS Permissions Status: success
AWS IAM Permissions Status: success
AWS KMS Permissions Status: success
AWS MKS Permissions Status: success
AWS S3 Permissions Status: success
AWS ServiceQuotas Permissions Status: success
AWS CloudFormation Permissions Status: success
AWS Cloudwatch Permissions Status: success
AWS EIP Limits Status: success
AWS NAT Limits Status: success
AWS VPC Limits Status: success
- Note: If you run into a failure you must check your IAM User and policy to ensure the appropriate permissions have been set.
Repair Environment
If an issue is encountered with your environment, you may see one of the following states provisioning_error
, updating_error
, or repairing_error
. Repair can be used to restart the process.
Repair will not work if your environment state is deprovisioning_error
or preflight_success
. If you run into this, please contact us and our team will be happy to help.
- CLI
- Use the
meroxa environment repair
command to repair your environment.
$ meroxa environment repair my-env
Envionrment "my-env" is being refreshed.
Run `meroxa env describe my-env for status.
- Note: If you continue to run into an error state, contact us.
What's Next?
You will receive an email notification once your environment is repaired. If you receive another error message, please contact us.