AWS Solution Architect

  • Home
  • /
  • AWS Solution Architect

AWS Solution Architect

  • Overview
  • Syllabus
  • Project
  • Interview Questions

Amazon Web Services (AWS) Certification is fast becoming the must have certificates for any IT professional working with AWS. This course is designed to help you pass the AWS Certified Solutions Architect (CSA) - Associate Exam. Even if you have never logged in to the AWS platform before, by the end of our AWS training you will be able to take the CSA exam. No programming knowledge needed and no prior AWS experience required. With this AWS certification under your belt (and optionally after completing our AWS Certified Developer 2017 - also available on Udemy), you will be in high demand by many employers and you can command a superior salary.
In this course we will start with a broad overview of the AWS platform and then deep dive into the individual elements of the AWS platform. You will explore Route53, EC2, S3, Cloud Front, Autoscaling, Load Balancing, RDS, RedShift, DynamoDB, EMR, VPC etc.

Syllabus

    1.Introduction to virtualization 

    • Hardware virtualization(hypervisors) 
    • OS-level virtualization
    • Network virtualization

    3.Aws services and Global infrastructure

    • AWS Global Infrastructure
    • AWS  features & Services and  its Limits
    • AWS pricing and physical Data Center.

    5.Aws storage services(EBS,EFS,S3)

    • Creating EBS volumes
    • Resizing  Exiting volumes 
    • Attaching and detaching volumes with in the Availability zone
    • Backup and restore EBS volumes using Snapshots 

    7.ELB (Elastic Load Balancer ) & High Availability and Clustering

    • Creating aws ELB with different Regions 
    • Create Classic ELB and maintaining backend instances 
    • Create High availability using Application ELB 
    • Path based routing 

    9.AWS DNS Service(Route53)

    • Domain Registration with aws and DNS providers
    • Configuring sites public 
    • Different Record sets creation 
    • Create private DNS 

    11.AWS Monitoring services(Cloudwatch) and Opensource Monitoring 

    • Monitoring different services like EC2,EBS,ELB,RDS..etc
    • Create custom metrics 
    • Create billing alerts, rules, aws logs 

    13.AWS S3 services and its policies 

    • Create S3 buckets different regions
    • Create static websites and route with own domain name
    • Versioning, cross region replications policies
    • Create Different set of Events of bucket

    15.AWS Commandline Interface(AWS CLI)

    • Install and configure aws cli on linux and windows 
    • Aws services managed by commands 

    17.AWS S3 With longtime data storage glacier (Glacier)

    • S3 Storage 

    19.Aws Cloud Migration Steps 

    • Cloud migrations

    21.Vmware vm's migrating from on premise to cloud in aws 

    • Migrating VMs to AWS
     

    2.Cloud computing and Deploy model

    • Public Clouds
    • Community Clouds
    • Private Clouds
    • Hybrid Clouds

    4.Provisioning and Planning instances based on Business(EC2)

    • Launch and connect instances from different Region's Availability zones
    • Create AMI and launch instance from images 
    • Upgrading exiting instances 
    • Modifying exiting instances on storage levels and network 

    6.Aws Networking services(VPC)

    • Designing and Creating Own Network on AWS 
    • Connecting vpc's on same Regions using vpc peering connection
    • VPC peering connection same region different accounts
    • Adding New ENIC(Elastic Network Cards)
    • Associate and reassociate EIP's 
    • Assigning secondary private ip's and configuring instances 

    8.Scaling instances based on the Business Requirements(ASG)

    • Create and setup Auto scaling group from the templates
    • POC for auto scaling with ELB and load test best practice

    10.Alerting Services for Problem causes and quickly fix issues(SNS) 

    • Create and configure different services alerting using SNS topics 

    12.Database services and high Fault Tolerance(RDS)

    • Create RDS Databases for mysql,aurora db engine
    • Create and Restore, copy snapshot of RDS DBs 
    • Create backup with different Availability zones
    • Create cross region Replication (Master-Slave setup)

    14.AWS Identity Access Management (IAM)

    • Create different polices 
    • Create users, groups, create custom managed polices

    16.Site-to-Site VPN Tunnelling setup (open source)

    • Create and set up vpn tunnel connection with different vpc's

    18.Aws Auditing Service (Cloudtrail)

    • Aws account auditing 

    20.AWS Security Best Practies 

    • Encrypt EBS volumes 
    • Setup up NACL for VPC 's
    • Instances and EBS volumes Termination Protection 

To create your buckets and upload your website content for hosting

1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.
2. Create two buckets that match your domain name and subdomain. For instance, example.com and www.example.com.
For step-by-step instructions, see How Do I Create an S3 Bucket? in the Amazon Simple Storage Service Console User Guide.
3. Upload your website data to the example.com bucket.
You will host your content out of the root domain bucket (example.com), and you will redirect requests for www.example.com to the root domain bucket. You can store content in either bucket. For this example, you host content in the example.com bucket. The content can be text files, family photos, videos—whatever you want. If you have not yet created a website, then you only need one file for this example. You can upload any file. For example, you can create a file using the following HTML and upload it to the bucket. The file name of the home page of a website is typically index.html, but you can give it any name. In a later step, you provide this file name as the index document name for your website.
 

For step-by-step instructions, see How Do I Upload an Object to an S3 Bucket? in the Amazon Simple Storage Service Console User Guide.

  1. Configure permissions for your objects to make them publicly accessible.

Attach the following bucket policy to the example.com bucket, substituting the name of your bucket for example.com. For step-by-step instructions to attach a bucket policy, see How Do I Add an S3 Bucket Policy? in the Amazon Simple Storage Service Console User Guide.

You now have two buckets, example.com and www.example.com, and you have uploaded your website content to the example.com bucket. In the next step, you configure www.example.com to redirect requests to your example.com bucket. By redirecting requests, you can maintain only one copy of your website content. Visitors who type www in their browsers and those who specify only the root domain are routed to the same website content in your example.com bucket. 

Step 2.2: Configure Buckets for Website Hosting

When you configure a bucket for website hosting, you can access the website using the Amazon S3 assigned bucket website endpoint.
In this step, you configure both buckets for website hosting. First, you configureexample.com as a website and then you configure www.example.com to redirect all requests to the example.com bucket.
To configure your buckets for website hosting
1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.
2. In the Bucket name list, choose the name of the bucket that you want to enable static website hosting for.
3. Choose Properties.
4. Choose Static website hosting.
5. Configure the example.com bucket for website hosting. In the Index Documentbox, type the name that you gave your index page.

6. Choose Save.

Step 2.3: Configure Your Website Redirect

Now that you have configured your bucket for website hosting, configure the www.example.com bucket to redirect all requests for www.example.com to example.com.
To redirect requests from www.example.com to example.com
1. In the Amazon S3 console, in the Buckets list, choose your bucket (www.example.com, in this example).
2. Choose Properties.
3. Choose Static website hosting.
4. Choose Redirect requests. In the Target bucket or domain box, type example.com.

Step 2.4: Configure Logging for Website Traffic

Optionally, you can configure logging to track the number of visitors accessing your website. To do that, you enable logging for the root domain bucket. For more information, see (Optional) Configuring Web Traffic Logging.

Step 2.5: Test Your Endpoint and Redirect

To test the website, type the URL of the endpoint in your browser. Your request is redirected, and the browser displays the index document for example.com.

You have now successfully redirected requests from one bucket to another, and the following Amazon S3 bucket website endpoints are accessible to any internet user:

  • example.com.s3-website-us-east-1.amazonaws.com
  • http://www.example.com.s3-website-us-east-1.amazonaws.com

In the next step, you use Amazon Route 53 to enable customers to use all of the URLs to navigate to your site.

Step 3: Create and Configure Amazon Route 53 Hosted Zone

Configure Amazon Route 53 as your Domain Name System (DNS) provider. If you want to serve content from your root domain, such as example.com, you must use Amazon Route 53. You create a hosted zone, which holds the DNS records associated with your domain:

  • An alias record that maps the domain example.com to the example.com bucket. This is the bucket that you configured as a website endpoint in step 2.2.
  • Another alias record that maps the subdomain www.example.com to the www.example.com bucket. You configured this bucket to redirect requests to the example.com bucket in step 2.2.

Step 3.1: Create a Hosted Zone for Your Domain

Go to the Amazon Route 53 console at https://console.aws.amazon.com/route53 and then create a hosted zone for your domain. For instructions, go to Creating a Hosted Zone in the http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/.

The following example shows the hosted zone created for the example.com domain. Write down the Amazon Route 53 name servers (NS) for this domain. You will need them later.

Step 3.2: Add Alias Records for example.com and www.example.com

The alias records that you add to the hosted zone for your domain maps example.com and www.example.com to the corresponding S3 buckets. Instead of using IP addresses, the alias records use the Amazon S3 website endpoints. Amazon Route 53 maintains a mapping between the alias records and the IP addresses where the S3 buckets reside.

For step-by-step instructions, see Creating Resource Record Sets by Using the Amazon Route 53 Console in the Amazon Route 53 Developer Guide.

The following screenshot shows the alias record for example.com as an illustration. You also need to create an alias record for www.example.com.

To enable this hosted zone, you must use Amazon Route 53 as the DNS server for your domain example.com. If you are moving an existing website to Amazon S3, first you must transfer DNS records associated with your domain example.com to the hosted zone that you created in Amazon Route 53 for your domain. If you are creating a new website, you can go directly to step 4.

Note

Creating, changing, and deleting resource record sets take time to propagate to the Amazon Route 53 DNS servers. Changes generally propagate to all Amazon Route 53 name servers in a couple of minutes. In rare circumstances, propagation can take up to 30 minutes.

Step 3.3: Transfer Other DNS Records from Your Current DNS Provider to Amazon Route 53

Before you switch to Amazon Route 53 as your DNS provider, you must transfer the remaining DNS records—including MX records, CNAME records, and A records—from your DNS provider to Amazon Route 53. You don't need to transfer the following records:

  • NS records– Instead of transferring these, replace their values with the name server values that are provided by Amazon Route 53.
  • SOA record– Amazon Route 53 provides this record in the hosted zone with a default value.

Migrating required DNS records is a critical step to ensure the continued availability of all the existing services hosted under the domain name.

Step 3.4: Create A Type DNS Records

If you're not transferring your website from another existing website, you need to create new A type DNS records.

Note

If you've already transferred A type records for this website from a different DNS provider, you can skip the rest of this step.

To create A type DNS records in the Amazon Route 53 console

  1. Open the Amazon Route 53 console in your web browser.
  2. On the Dashboard, choose Hosted zones.
  3. Choose your domain name in the table of hosted zones.
  4. Choose Create Record Set.
  5. In the Create Record Set form that appears on the right, choose Yes for Alias.
  6. In Alias Target, provide the Amazon S3 website endpoint—for example, s3-website-us-west-2.amazonaws.com.
  7. Choose Save Record Set.

Now that you've added an A type DNS record to your record set, it appears in the table as in the following example.

Step 4: Switch to Amazon Route 53 as Your DNS Provider

To switch to Amazon Route 53 as your DNS provider, contact your DNS provider and update the name server (NS) record to use the name servers in the delegation that you set in Amazon Route 53.

On your DNS provider's site, update the NS record with the delegation set values of the hosted zone as shown in the following Amazon Route 53 console screenshot. For more information, see Updating Your DNS Service's Name Server Records in Amazon Route 53 Developer Guide.

When the transfer to Amazon Route 53 is complete, verify that the name server for your domain has indeed changed. On a Linux computer, use the dig DNS lookup utility. For example, use this dig command:

It returns the following output (only partial output is shown). The output shows the same name servers on the Amazon Route 53 hosted zone that you created for the example.com domain.

Step 5: Testing

To verify that the website is working correctly, in your browser, try the following URLs:
  •  http://example.com - Displays the index document in the example.com bucket.
  •  http://www.example.com- Redirects your request to http://example.com.
In some cases, you might need to clear the cache of your web browser to see the expected behavior.