Aws overview part 3(databases, dns and management services)

1. Intro

2. AutoScaling
2
▪ AWS Auto Scaling monitors your applications and automatically adjusts
capacity to maintain steady, predictable performance at the lowest
possible cost.
▪ Using AWS Auto Scaling, it’s easy to setup application scaling for
multiple resources across multiple services in minutes.
▪ The service provides a simple, powerful user interface that lets you build
scaling plans for resources including Amazon EC2 instances and Spot
Fleets, Amazon ECStasks, Amazon DynamoDB tables and indexes,
and Amazon Aurora Replicas.
▪ AWS Auto Scaling makes scaling simple with recommendations that
allow you to optimize performance, costs, or balance between them.
▪ If you’re already using Amazon EC2 Auto Scaling to dynamically scale
your Amazon EC2 instances, you can now combine it with AWS Auto
Scaling to scale additional resources for other AWS services.
▪ With AWS Auto Scaling, your applications always have the right
resources at the right time.

3. AutoScaling
3
▪ For example, the following Auto Scaling group has a minimum size
of 1 instance, a desired capacity of 2 instances, and a maximum
size of 4 instances.The scaling policies that you define adjust the
number of instances, within your minimum and maximum number
of instances, based on the criteria that you specify.

4. Register a Domain Name
4
▪ You will connect that domain name through the Domain Name
System (DNS) to a currently running EC2 instance (such as
aWebApp, or website runningWordPress, Apache, NGINX, IIS, or
otherWebsite platform). If you already have a domain name
registered, do step 1 and then refer to your domain registrar’s
documentation for how to set the DNS record for your new site.
▪ Cost implications:
– There's an annual fee to register a domain, ranging from $9 to several
hundred dollars, depending on the top-level domain, such as .com. For more
information, see Amazon Route 53 Pricing for Domain Registration.This fee is
not refundable.
– When you register a domain, we automatically create a hosted zone that has
the same name as the domain.You use the hosted zone to specify where you
want Amazon Route 53 to route traffic for your domain.The fee for a hosted
zone is $0.50 per month.You can delete the hosted zone if you want to avoid
this charge.

5. Step 1: Obtain a Static URL
5
▪ Click https://us-east-
1.console.aws.amazon.com/ec2/v2/home?region=us-east-
1#Addresses:sort=publicIp to open the Elastic IPs part of the EC2
console in a new window and click Allocate New Address.

6. Step 1: Obtain a Static URL
6
▪ Set EIP used in: toVPC and clickYes, Allocate.
▪ Note your new IP address and click Close.

7. Step 1: Obtain a Static URL
7
▪ Select the new IP address in the Elastic IP column. Press
the Actions button and choose theAssociate Address option.

8. Step 1: Obtain a Static URL
8
▪ Click in the Instance text box and choose the option that has your
instance name.

9. Step 1: Obtain a Static URL
9
▪ Make a note of your new IP address in the Elastic IP column.
▪ Verify that your new Elastic IP address is working.

10. Step 2: Register a Domain Name
10
▪ Open the Route 53 console in a new window (Route 53 is AWS’s
DNS service).You can register new domain names with Route 53 as
well as manage DNS records for your domain.
– Select Get Started Now under Domain Registration.

11. Step 2: Register a Domain Name
11
▪ Click the Register Domain button. On the next screen, enter the
domain you want in the Choose a Domain box (cloudexamples is
shown in the image, then select aTop Level Domain(TLD) (e.g.
.com, .org, .co.uk, etc.) And click the Check button to see if the
domain is available. If the domain is available, click the Add to
cart button and scroll to the bottom of the page to click Continue.

12. Step 2: Register a Domain Name
12
▪ Enter yourContact Details.These are the details that will be
associated with your domain name.When you are done,
click Continue at the bottom of the page.

13. Step 2: Register a Domain Name
13
▪ Review the details as they are listed and, if they are correct, check
the box titled I have read and agree to the AWS Domain Name
Registration Agreement.Then click the Complete
Purchase button.

14. Step 2: Register a Domain Name
14
▪ If you registered a domain that has a generic top-level
domain (such as .com), you'll receive an email that asks you to
confirm your email address. (We don't send an email if we already
have confirmation that the email address is valid.)
– You must follow the link in this email to confirm your email address, or the
domain won't be registered.
– For all domains, you'll receive an email when your domain registration has
been approved.

15. Step 3: Configure DNS
15
▪ Open the Hosted Zones part of the Route 53 console. Next, click on
the domain name you created in step 2 (in this example we are
using cloudexamples.com but your domain will be different).

16. Step 3: Configure DNS
16
▪ If you have a static IP address for your website, virtual server, or
service; select Static IP Address below.
▪ If you have a Fully Qualified Domain Name (FQDN) for your
resource (this is common for applications launced by Elastic
Beanstalk, Lambda functions, S3 static sites and more advanced
deployments using Elastic Load Balancing) please select Fully
Qualified Domain Name (FQDN) below.
– Static IP Address
– Fully Qualified Domain Name

17. Step 3: Configure DNS: Static
IP Address
17
▪ Click the Create Record Set button. On the right side of the
window, enter www in the Nametext box. Enter the Elastic IP
address you created in step 1 in theValue box and then
click Create.

18. Step 3: Configure DNS: Static
IP Address
18
▪ Verify that you have a new entry in the main table with the value
you entered.

19. Step 3: Configure DNS: Static
IP Address
19
▪ Verify that your website is now available at your new domain by
typing your new website address into your web browser.

20. Step 3: Configure DNS: FQDN
20
▪ Click the Create Record Set button. On the right side of the
window, enter www in the Nametext box.Then selectYes for
the Alias setting. An AliasTarget box will appear, click in the Alias
Target box and you will see a list of resources that you have
available. Select the resource you want to point to (this will be
under Elastic Load Balancers and should the resource associated
with your Elastic Beanstalk deployed application), then
click Create.

21. Step 3: Configure DNS: FQDN
21
▪ Verify that you have a new entry in the main table with the value
you entered.

22. Step 3: Configure DNS: FQDN
22
▪ Verify that your website is now available at your new domain by
typing your new website address into your web browser.

23. CloudFormation
23
▪ AWS CloudFormation provides a common language for you to
describe and provision all the infrastructure resources in your cloud
environment.
▪ CloudFormation allows you to use a simple text file to model and
provision, in an automated and secure manner, all the resources
needed for your applications across all regions and accounts.This
file serves as the single source of truth for your cloud
environment.
▪ AWS CloudFormation is available at no additional charge, and you
pay only for the AWS resources needed to run your applications.

24. CloudFormation
24
▪ Templated resource provisioning •
– Create templates to describe the AWS resources used to run your application
– Provision identical copies of a stack

25. CloudFormation
25
▪ Create templates of the infrastructure and applications you want
to run onAWS
▪ Have CloudFormation automatically provision the required AWS
resources and their relationships from the templates
▪ Easily version, replicate, or update
the infrastructure and applications
using the templates
▪ Integrates with other development,
CI/CD, and management tools

26. CloudFormation
26
▪ Create templates of the infrastructure and applications you want
to run onAWS
▪ Have CloudFormation automatically provision the required AWS
resources and their relationships from the templates
▪ Easily version, replicate, or update
the infrastructure and applications
using the templates
▪ Integrates with other development,
CI/CD, and management tools

27. Cloud Best Practices
27
▪ Design for failure and nothing will fail
▪ Decouple your components
▪ Implement elasticity
– Automate your infrastructure
– Bootstrap your instances
▪ Think parallel
▪ Keep dynamic data closer to the compute and static data closer
to the end-user.