{"_id":"58127592a1a9360f00ab3126","parentDoc":null,"version":{"_id":"55d535cb988e130d000b3f5f","__v":13,"project":"55d535ca988e130d000b3f5c","hasDoc":true,"hasReference":false,"createdAt":"2015-08-20T02:04:59.052Z","releaseDate":"2015-08-20T02:04:59.052Z","categories":["55d535cc988e130d000b3f60","55d6b238d2a8eb1900109eef","55d6b4f3250d7d0d004274cd","55d7967960fc730d00fc2852","55da9804e835f20d009fc5d0","55e75b1de06f4b190080dbfd","55e75b39e06f4b190080dbfe","55e75b7ae06f4b190080dbff","564f5a4e33082f0d001bb709","570fb64aa38d470e0060cbff","586d0dd89a854123001acd65","586d0e3b9a854123001acd66","5a613b28da07540012e8ca4a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"user":"57ebf6b80db1190e0094a3ba","category":{"_id":"55e75b7ae06f4b190080dbff","__v":10,"project":"55d535ca988e130d000b3f5c","version":"55d535cb988e130d000b3f5f","pages":["5637e17197666c0d008656a5","569591a4fcb1032d0089e037","569622eafe18811700c9c19b","5696c9588560a60d00e2c1e0","569709ca0b09a41900b2442b","5697129ac8ded91700307b77","5697190a59a6692d003fad6a","5697192969393517000c8280","569f11908f6d4b0d00f13bb2","56a0030b5b981c2b00383df0"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-02T20:26:34.258Z","from_sync":false,"order":4,"slug":"frame-platform","title":"Frame Platform"},"project":"55d535ca988e130d000b3f5c","__v":1,"githubsync":"","updates":["58a63a893239fa0f00857595"],"next":{"pages":[],"description":""},"createdAt":"2016-10-27T21:45:54.615Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":18,"body":"Frame provides Strategic tier customers with the ability to “Bring Your Own” (BYO) Amazon Web Services (AWS) account. You may choose to have your Frame accounts use infrastructure provisioned under your own AWS accounts because: \n\n* You wish to take advantage of your existing billing arrangements with AWS for convenience and/or pricing \n* You wish to use Amazon’s Consolidated Billing feature to pay for the Frame infrastructure \n* You want to have direct administrative access to your Frame workloads for additional monitoring and metrics. \n\nEach Frame Platform installation has a default AWS account associated with it. This default AWS account is used for provisioning infrastructure like EC2 instances, EBS volumes, etc. The default account is also used for storing Gold Master Images, known as Amazon Machine Images (AMIs). With the BYO AWS Account option, these components are instead provisioned in your AWS account, rather than in the default AWS account. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Requirements\"\n}\n[/block]\nThis AWS account must be dedicated to Frame and you should not make any manual changes to it in the AWS Console. Ensure that no servers, storage, or any other items exist or are being used for any other purposes. If this is one of many accounts that you manage, consider setting up [Consolidated Billing](http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/consolidated-billing.html) through AWS. \n\nNote that Frame Linux Desktops are not yet supported on BYO accounts. You will also need a valid email address in your organization for each Frame Platform Enterprise Admin, who will manage your account. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"AWS Setup Steps\"\n}\n[/block]\nIn order to setup your BYO AWS Account with Frame, we will need you to perform the following tasks (for detailed step-by-step instructions see [this doc](https://docs.fra.me/v1.0/docs/finding-byo-credentials)): \n\n1. Create your own AWS account. \n2. Create an IAM account with an Access Key ID and a Secret Access Key. Set permissions to “AmazonEC2FullAccess\" to your AWS account. This IAM account will be used by Frame to programmatically access resources. \n3. Create an IAM account with user name, password and account name. Set permissions to “AmazonEC2FullAccess\" to your AWS account. This IAM account will be used by our operators to access the account via the AWS Web Console for management purposes. \n4. Send us the details and credentials for your new AWS account and IAM accounts from the steps above, including your IAM Account Name, User Name, Password, Access Key ID, and Secret Access Key. Work with one of our team members to transfer this info to us securely. Also send a list of names and email addresses of the Frame Platform Enterprise Admins, who will manage this account. \n\nNote that if you plan on using Frame's file server capabilities, such as the Frame Personal Drive or the Frame Team Drive, you will need additional, custom IAM policies. Please contact the Frame Support team for these policies and instructions on how to apply them to your new IAM accounts. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"AWS Instance, Storage and Networking Configurations\"\n}\n[/block]\nIn order for the Frame platform to properly provision and manage instances, you will also need to set up appropriate service limits for certain AWS components, as follows: \n\n- Increase the maximum number of running on-demand instances for each instance type by 220%. For example, if you are planning to have your Max capacity in the Dashboard set to 100, you will need to increase your limit to 220. This enables the Frame platform to publish app updates from the Sandbox without issue, because the publishing process creates new instances without affecting existing user sessions. \n- Increase the amount of EBS storage according to the following formula: Number of instances (both stopped and running, ie your Max capacity as set in the Dashboard) multiplied by the disk size, plus an additional 20%. For example, for a maximum number of instances of 100 and a drive size of 60 GB, you will need 220 x 60 x 1.2, which equals approximately 16 TB. \n- Frame will create one new Amazon Virtual Private Cloud (VPC) for each of your Frame accounts. Frame Strategic tier customers have the ability to create multiple Frame sub-accounts; therefore multiple VPC's will be needed at the Strategic Tier. Since the default VPC limit per AWS account is 5, you may need to increase the limit of VPCs on your AWS account. \n- If using Air instances that leverage t-series instances types, increase the number of t2 starts/launches to match the number of systems you plan to start in a 24 hour period, in a particular region. This ensures that when systems are started they start with full CPU credits. More information [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/t2-std.html#launch-credits). Contact Frame support to also enable Frame functionality that ensures that systems low on CPU credits are not used for user sessions.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"AWS Service Categories and Usage\"\n}\n[/block]\nFor a BYO AWS account, Frame uses EC2 instances, EBS-backed volumes and AWS networking as the basis for service. Your total cost of AWS service depends on your service tier with Amazon and any custom pricing arrangements you may have. Full details of AWS pricing for these areas are listed in [Amazon's pricing information online](https://aws.amazon.com/pricing/). \n\nFrame's default settings configure the following EC2 instance types, which correspond to the Air and Pro system models: \n\n- t2.small \n- t2.medium\n- t2.large\n- g2.2xlarge\n- g2.8xlarge\n\nUtility servers are assigned t2.small instance types by default. \n\nEBS storage sizing is based on several factors specific to your apps: The base system image of the Windows OS, the size of your applications plus application data and any user data. Additional EBS data is consumed, if you are also using a utility server. \n\nThe default base system image for the Sandbox is 45 GB, but can be increased via a Support request. The general formula for estimating the total amount of storage is the Sandbox image size multiplied by the maximum number of instances multiplied by the monthly hours consumed. Total storage also includes the system image size of all Utility Servers multiplied by the number of hours consumed per month. Note that even if instances are stopped, storage is still consumed. \n\nYour networking usage on Amazon also depends on your apps and work patterns of users. AWS networking limits and data transfer pricing are based on inbound and outbound data sent to or from AWS regions or the internet. Typical data transfer costs for Frame customers are between 1% and 2% of their overall monthly bill. For details about how your account will be charged for data transfers, please refer to AWS documentation. \n\nYour AWS expenses are separate from the cost of Frame service for our BYO accounts. Amazon bills your account according to your usage patterns on Frame, as described in [our documentation regarding capacity and scaling](doc:set-up-capacity-and-scaling).","excerpt":"Bring Your Own Amazon Web Services Account to Frame","slug":"byo-aws-account","type":"basic","title":"BYO AWS Account"}

BYO AWS Account

Bring Your Own Amazon Web Services Account to Frame

Frame provides Strategic tier customers with the ability to “Bring Your Own” (BYO) Amazon Web Services (AWS) account. You may choose to have your Frame accounts use infrastructure provisioned under your own AWS accounts because: * You wish to take advantage of your existing billing arrangements with AWS for convenience and/or pricing * You wish to use Amazon’s Consolidated Billing feature to pay for the Frame infrastructure * You want to have direct administrative access to your Frame workloads for additional monitoring and metrics. Each Frame Platform installation has a default AWS account associated with it. This default AWS account is used for provisioning infrastructure like EC2 instances, EBS volumes, etc. The default account is also used for storing Gold Master Images, known as Amazon Machine Images (AMIs). With the BYO AWS Account option, these components are instead provisioned in your AWS account, rather than in the default AWS account. [block:api-header] { "type": "basic", "title": "Requirements" } [/block] This AWS account must be dedicated to Frame and you should not make any manual changes to it in the AWS Console. Ensure that no servers, storage, or any other items exist or are being used for any other purposes. If this is one of many accounts that you manage, consider setting up [Consolidated Billing](http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/consolidated-billing.html) through AWS. Note that Frame Linux Desktops are not yet supported on BYO accounts. You will also need a valid email address in your organization for each Frame Platform Enterprise Admin, who will manage your account. [block:api-header] { "type": "basic", "title": "AWS Setup Steps" } [/block] In order to setup your BYO AWS Account with Frame, we will need you to perform the following tasks (for detailed step-by-step instructions see [this doc](https://docs.fra.me/v1.0/docs/finding-byo-credentials)): 1. Create your own AWS account. 2. Create an IAM account with an Access Key ID and a Secret Access Key. Set permissions to “AmazonEC2FullAccess" to your AWS account. This IAM account will be used by Frame to programmatically access resources. 3. Create an IAM account with user name, password and account name. Set permissions to “AmazonEC2FullAccess" to your AWS account. This IAM account will be used by our operators to access the account via the AWS Web Console for management purposes. 4. Send us the details and credentials for your new AWS account and IAM accounts from the steps above, including your IAM Account Name, User Name, Password, Access Key ID, and Secret Access Key. Work with one of our team members to transfer this info to us securely. Also send a list of names and email addresses of the Frame Platform Enterprise Admins, who will manage this account. Note that if you plan on using Frame's file server capabilities, such as the Frame Personal Drive or the Frame Team Drive, you will need additional, custom IAM policies. Please contact the Frame Support team for these policies and instructions on how to apply them to your new IAM accounts. [block:api-header] { "type": "basic", "title": "AWS Instance, Storage and Networking Configurations" } [/block] In order for the Frame platform to properly provision and manage instances, you will also need to set up appropriate service limits for certain AWS components, as follows: - Increase the maximum number of running on-demand instances for each instance type by 220%. For example, if you are planning to have your Max capacity in the Dashboard set to 100, you will need to increase your limit to 220. This enables the Frame platform to publish app updates from the Sandbox without issue, because the publishing process creates new instances without affecting existing user sessions. - Increase the amount of EBS storage according to the following formula: Number of instances (both stopped and running, ie your Max capacity as set in the Dashboard) multiplied by the disk size, plus an additional 20%. For example, for a maximum number of instances of 100 and a drive size of 60 GB, you will need 220 x 60 x 1.2, which equals approximately 16 TB. - Frame will create one new Amazon Virtual Private Cloud (VPC) for each of your Frame accounts. Frame Strategic tier customers have the ability to create multiple Frame sub-accounts; therefore multiple VPC's will be needed at the Strategic Tier. Since the default VPC limit per AWS account is 5, you may need to increase the limit of VPCs on your AWS account. - If using Air instances that leverage t-series instances types, increase the number of t2 starts/launches to match the number of systems you plan to start in a 24 hour period, in a particular region. This ensures that when systems are started they start with full CPU credits. More information [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/t2-std.html#launch-credits). Contact Frame support to also enable Frame functionality that ensures that systems low on CPU credits are not used for user sessions. [block:api-header] { "type": "basic", "title": "AWS Service Categories and Usage" } [/block] For a BYO AWS account, Frame uses EC2 instances, EBS-backed volumes and AWS networking as the basis for service. Your total cost of AWS service depends on your service tier with Amazon and any custom pricing arrangements you may have. Full details of AWS pricing for these areas are listed in [Amazon's pricing information online](https://aws.amazon.com/pricing/). Frame's default settings configure the following EC2 instance types, which correspond to the Air and Pro system models: - t2.small - t2.medium - t2.large - g2.2xlarge - g2.8xlarge Utility servers are assigned t2.small instance types by default. EBS storage sizing is based on several factors specific to your apps: The base system image of the Windows OS, the size of your applications plus application data and any user data. Additional EBS data is consumed, if you are also using a utility server. The default base system image for the Sandbox is 45 GB, but can be increased via a Support request. The general formula for estimating the total amount of storage is the Sandbox image size multiplied by the maximum number of instances multiplied by the monthly hours consumed. Total storage also includes the system image size of all Utility Servers multiplied by the number of hours consumed per month. Note that even if instances are stopped, storage is still consumed. Your networking usage on Amazon also depends on your apps and work patterns of users. AWS networking limits and data transfer pricing are based on inbound and outbound data sent to or from AWS regions or the internet. Typical data transfer costs for Frame customers are between 1% and 2% of their overall monthly bill. For details about how your account will be charged for data transfers, please refer to AWS documentation. Your AWS expenses are separate from the cost of Frame service for our BYO accounts. Amazon bills your account according to your usage patterns on Frame, as described in [our documentation regarding capacity and scaling](doc:set-up-capacity-and-scaling).