Skip to main content

Prerequisites

Setting up the Ahana Compute Plane follows the AWS best-practice of using cross-account access with trust relationships.

There are certain prerequisites required to setup cross-account access.

An AWS Account#

You will need an AWS Account. If you don't have one, you can create one on AWS.

Before setting up Ahana, your AWS account needs to be verified. Typically when your account is fully activated, you receive a confirmation email from AWS. This can take up to 24 hours after account creation. Check your email and spam folder for the confirmation email. After you receive this email, you have full access to all AWS services. More details

AWS IAM Access#

To setup cross-account access, you will need to be able to create a new AWS IAM policy and attach it to a new role. This requires your account / user to have the IAMFullAccess policy attached to it.

Access to AWS Services#

The Ahana Compute Plane is built to be cloud native and uses a range of AWS services for the best cloud experience. Ensure your account has access to the following AWS services: Amazon CloudFormation, Amazon EKS. You can visit these services linked above to make sure you have access to them and can provision them in your account.

AWS Resource quotas#

If necessary, request service quota increases for the following resources. You might request quota increases to avoid exceeding the default limits for any resources that are shared across multiple deployments. The Service Quotas console displays your usage and quotas for some aspects of some services. For more information, see What is Service Quotas? and AWS service quotas.

ServiceNumber of resources requiredDefaultLink to quota increase
EC2 running On-Demand Standard instances2 per compute plane
1 per presto coordinator
1 per worker node
1 per Hive metastore
5EC2 instances Quotas
EC2-VPC Elastic IPs1 per VPC5EIP Quotas
Active VPC peering connections per VPC1 per peering connection50VPC Quotas
ACM certificates1 per compute plane2,500ACM Quotas
EKS Managed node groups per cluster2 per clusters30EKS Quotas
S3 Buckets1 or 2 per clusters
(if Hive metastore attached)
100S3 Buckets Quotas