The following lists common issues that can occur during deployment.
Custom DNS resolvers: Some organizations configure custom DNS resolvers (via DHCP) for EC2 instances in their VPCs. For the TetraScience platform to function correctly, it's essential that the DNS resolver delegate to AWS's Route53 resolver for domain names such as
*.internalthat are outside the organization's private cloud/on-premises network.
Rollback: Some organizations install TetraScience using an IAM user that has permissions to create certain resources, but not destroy them. This can be a problem during rollback scenarios, because it becomes impossible to undo the upgrade and leaves the system in an intermediate state that requires manual maintenance. Organizations should provide a user with full permissions, or plan ahead for manual workarounds.
Updated 10 months ago