This page covers the essentials of what you need before the process of getting a website online begins. You need to secure a name with a Registrar, and then provide your registrar with name servers, which are typically provided by your host.
Aside from the AWS account, of course, and the IAM role setup here, which is used here as a best practice way to implement Burris Builder infrastructure, this is standard for any website domain. The usage of AWS Route 53 for domain registration is completely optional, though you will have to follow directions specific to the provider you choose. We highly recommend Route 53 service for you name servers.
Your Amazon Account
After signing up for Amazon Web Services, the Amazon Console is where you have complete control over your resources. After some initial setup, however, the console will generally be left alone, as you primarily build or manage through the servers themselves.
The capabilities and services offered through the console go well beyond the scope of what Burris Builder documentation aims to provide. These steps will help you, the developer, get a website up and running quickly. You will learn more about this as documentation progresses. More in-depth topics related to specific tasks may be found in the Deep Dive section of our documentation.
You will choose a domain through a domain registrar. Popular choices include namecheap.com or Google Domains. AWS also offer domains to be purchased directly through Route 53 through a 3rd party. Once your domain name is secured, you will provide your registrar with name servers, which then will then direct traffic to your web server.
Illumine Digital does not endorse any specific name registration services. The registrar you choose may be entirely independent of your host, and your registrar has no impact on quality of AWS services. There are some considerations, however:
- Beware of recurring fees and how much fees will increase after the first year.
- Beware of add-on services. Although privacy is popular choice, you will also need to beware of price increases after the first year. Most other add-ons are not necessary.
- SSL Certs, or secure socket layer certificates, are commonly bundled. Generally, wildcard SSLs or multi-domain SSLs are preferred instead. Bundled SSLs typically only cover the primary domain and "www", while wildcard will cover dev.example.com, stage.example.com and cdn.example.com, for instance. An SSL certificate may be purchased anywhere, and it is not necessary to bundle it with your domain purchase.
- Beware of default, automatic renewal options. Some companies aggressively set automatic renewals to two years at a time, which can inflate the expected charge considerably.
Once you have completed the sign up domain sign-up and registration services, proceed to the next step.
This is how the internet will find your web server. "Zones" are essentially domains. You will create a new zone for each domain you host at Amazon. Inside each zone, you then create record sets which server any number of functions, from email to domain ownership verification and other external service regarding your domain.
IAM Role Setup
IAM describes credentials and access permissions to various parts of your infrastructure. Users may be created to allow limited access to various resources such as Ec2, S3 bucket management, domain management and so on. For the purpose of this section, you want to create a role which Burris Builder will use to create and manipulate infrastructure resources.
Roles in IAM are slightly different than some traditional user management models. Roles do not represent physical users. They are primarily meant for automation, and a way to define access given to scripts or other resources. In our case for AWS, you will create a role which will then be assigned to your Ec2 server when it is built. This will ensure your server has the correct permissions to build other infrastructure such as RDS servers and CloudFront Distributions
From your console, select IAM under the Services menu. From the IAM dashboard, select Roles from the left hand menu. Select, "Create New Role".
Step 1: Set Role Name
This can be any name you like, we recommend "builder"
Step 2: Select Role Type
We're going to be building Ec2 Resources with this role, so click Select in the "Amazon Ec2" row.
Step 3: Establish Trust
This stepped will be skipped in our case, you will be automatically brought to Step 4
Step 4: Attach Policy
Next to "Filter" on this pge, there is a Search box. Type "Power" which should narrow a the selection to power users. Check the box next to "PowerUserAccess" and click Next Step.
Step 5: Review
There are no options to change here, just a final panel to double check your work. Click "Finish", and you will have a role available for your Burris Builder web server.
You only need to worry about a VPC if your account was created before December 4th, 2013. After this date, any Amazon account created automatically has a VPC created for it. Before this date, resources created outside a VPC are referred to as "Amazon Classic" resources. While these resources are unofficially supported by Burris Builder, documentation and maintenance will support VPC only. Documentation for creating a VPC for a Classic account is not yet available. Features and documentation are heavily influenced by demand, so if you are on a classic account and would like help getting it up to speed, send us an email.