AppsCode Cloud w/ Usage Billing

Launch the Product to Create a New Application

CLOUDFORMATION PARAMETERS:

• InstanceType: Select an EC2 instance to deploy the application. The instance must have at least 4 CPU cores and 16 GB of memory.

• ApplicationAccessIpCIDR: Enter the CIDR range from which the site will be accessed. Use x.x.x.x/32 to allow access from a specific IP address. The public access is RECOMMENDED, use 0.0.0.0/0 to allow all IPs. You can further restrict access by applying a domain whitelist.

• SSHIpCIDR: Enter the CIDR range for SSH access to the application instance. Use x.x.x.x/32 for a specific IP address, 0.0.0.0/0 to allow access from all IPs, or specify another CIDR range. SSH access is required to retrieve the application admin username and password.

• KeyPair: Select an existing key pair. This key pair will be added to the instance to enable remote SSH access.

• DomainWhiteList: Enter a valid and existing domain with an MX record for domain whitelisting. This domain will be used to validate users' email addresses during signup. You may use a public domain (e.g., gmail.com) or your organization's private domain (e.g., appscode.com). Ensure the domain has an MX record; otherwise, application creation will fail.

ADMIN CREDENTIALS:

You will find the site URL in the Output of the cloudformation template. Follow these steps to retrieve the admin credentials:

• Connect to the EC2 instance created in the previous step. Use one of the connection methods available under the Connect option.
• Run cat /etc/appscode/login.txt command to view the application URL, admin username, and password. Use the retrieved username and password to log in to the application.

Access the application via a browser at https://<public_ip>. To connect to the operating system, use SSH and the username ec2-user. This product requires an internet connection to deploy properly. One or more the following packages are downloaded on deployment: https://github.com/appscode-cloud/installer/blob/master/catalog/ace.yaml . This product collects usage data to report metered usage to AWS. This products creates and associates necessary IAM permissions to the instance profile to report metered usage as documented here: https://docs.aws.amazon.com/marketplace/latest/userguide/iam-user-policy-for-aws-marketplace-actions.html#iam-user-policy-for-ami-products 

This product requires an ongoing internet connection. The following ongoing external services are required to properly function: https://appscode.com/ .

This product collects usage information anonymously. This information is sent to and stored by AppsCode Inc. This information will only be used in regards to the AppsCode Cloud.

This product creates IAM roles and policies. The purpose for each AWS Identity and Access Management (IAM) role and policies are described below:

Role: The IAM role will include all the necessary permissions required by the EC2 instance. This allows the ACE Application to manage your Kubernetes clusters.

Policy: A user-managed policy will be created to grant the required permissions for the following tasks:

• Create/Delete EKS clusters: Necessary permissions for creating/deleting/managing your EKS cluster. For detailed permission list see: https://cluster-api-aws.sigs.k8s.io/topics/iam-permissions.html .

• Import clusters to the console: Necessary permissions for listing regions, availability zones, listing and describing EKS clusters.

• Create/Delete S3 buckets: Necessary permissions for storing backups.

InstanceProfile: The instance profile will encapsulate the IAM role and be attached to the EC2 instance, allowing it to assume the role and use the associated permissions.