AWS Training

• Basic Configuration
• Hybris Building Blocks
• Hybris Logical Architecture
• Final Architecture Diagram

• Creating and deleting buckets
• Adding objects to buckets
• Accessing objects
• Deleting objects
• Lifecycle of s3 .
• Versioning in s3 .
• Replication .
• Uses of S3 storage
• Permissions of S3
• Discussing lifecycles in s3
• Glacier

• Different types of instance
• Pricing model in EC2 instances
• Regions and Availability Zones
• Amazon Machine Images (AMI)
• EC2 Windows instance & Linux Instance
• Security Groups
• Key Pairs
• Volumes
• Elastic IPs
• Launching an instance
• Logging into the instance
• Deployment
• Load balancing
• Auto scaling

• Different types of networks that can be setup in AWS
• Public subnets & private subnets
• Route tables
• CIDR
• Creating a new VPC
• ACL & Security Groups
• Creation of Internet Gateway
• Connecting to instances in the gateway

• Creation of user accounts in AWS
• Setting up multi-factor Authentication (MFA)
• Roles in IAM
• Groups in IAM
• AWS key & Secret Key
• Permissions for user
• Creation of custom policies
• Account settings
• Credential Report

• Selecting the Engine
• Configuring the Database Engine
• Creating your Database
• Setting up automatic backups
• Authorizing access to the DB via DB Security Groups

• Creating and deleting volumes
• Attaching and detaching volumes
• Creating snapshots
• Increasing the volume size
• Simple Queue Service (SQS)

• Sending messages to the queue
• Setting SNS to SQS
• Retrieving messages from SQS
• Simple Email Services (SES)

• Limits of SES
• Test Email setup
• Cloud watch

• Monitoring with Cloud watch
• Getting statistics for a specific EC2 instance
• Getting aggregated statistics
• Metrics for other AWS Services and related namespaces
• Setting up notifications

Auto-scaling is a function that allows you to provision and launch new instances whenever there is a demand. It allows you to automatically increase or decrease resource capacity in relation to the demand.

You can know that you are paying the correct amount for the resources that you are using by employing the following resources:

●   Check the Top Services Table

It is a dashboard in the cost management console that shows you the top five most used services. This will let you know how much money you are spending on the resources in question.
●   Cost Explorer
There are cost explorer services available which will help you to view and analyze your usage costs for the last 13 months. You can also get a cost forecast for the upcoming three months.
●   AWS Budgets
This allows you to plan a budget for the services. Also, it will enable you to check if the current plan meets your budget and the details of how you use the services.
●   Cost Allocation Tags
This helps in identifying the resource that has cost more in a particular month. 
It lets you organize your resources and cost allocation tags to keep track of your AWS costs.

The essential services that you can use are Amazon CloudWatch Logs, store them in Amazon S3, and then use Amazon Elastic Search to visualize them. You can use Amazon Kinesis Firehose to move the data from Amazon S3 to Amazon ElasticSearch.

DDoS is a cyber-attack in which the perpetrator accesses a website and creates multiple sessions so that the other legitimate users cannot access the service. The native tools that can help you deny the DDoS attacks on your AWS services are:

●   AWS Shield
●   AWS WAF
●   Amazon Route53
●   Amazon CloudFront
●   ELB
●   VPC

Amazon CloudWatch helps you to monitor the application status of various AWS services and custom events. It helps you to monitor:

●   State changes in Amazon EC2
●   Auto-scaling lifecycle events
●   Scheduled events
●   AWS API calls
●   Console sign-in events

AWS services that are not region-specific are:

●   IAM
●   Route 53
●   Web Application Firewall 
●   CloudFront

While you may think that both stopping and terminating are the same, there is a difference. When you stop an EC2 instance, it performs a normal shutdown on the instance and moves to a stopped state. However, when you terminate the instance, it is transferred to a stopped state, and the EBS volumes attached to it are deleted and can never be recovered.

Here’s how you accomplish this:

1.  Go to your PuTTY Configuration
2.  Go to the category SSH -> Auth
3.  Enable SSH agent forwarding to your instance

Here’s how you can configure them:

●   Create an Alarm using Amazon CloudWatch
●   In the Alarm, go to Define Alarm -> Actions tab
●   Choose Recover this instance option

Follow the steps provided below to recover an EC2 instance if you have lost the key:

1.  Verify that the EC2Config service is running
2.  Detach the root volume for the instance
3.  Attach the volume to a temporary instance
4.  Modify the configuration file
5.  Restart the original instance

You need to follow the four steps provided below to allow access. They are:

1.  Categorize your instances
2.  Define how authorized users can manage specific servers.
3.  Lockdown your tags
4.  Attach your policies to IAM users

To fix this problem, you need to enable the DNS hostname resolution, so that the problem resolves itself.

Here is a selection of security products and features:

●   Security groups - This acts as a firewall for the EC2 instances, controlling inbound and outbound traffic at the instance level.
●   Network access control lists - It acts as a firewall for the subnets, controlling inbound and outbound traffic at the subnet level.
●   Flow logs - These capture the inbound and outbound traffic from the network interfaces in your VPC.

RTO or Recovery Time Objective is the maximum time your business or organization is willing to wait for a recovery to complete in the wake of an outage. On the other hand, RPO or Recovery Point Objective is the maximum amount of data loss your company is willing to accept as measured in time.

You can monitor VPC by using:

●   CloudWatch and CloudWatch logs
●   VPC Flow Logs

If the resource in the stack cannot be created, then the CloudFormation automatically rolls back and terminates all the resources that were created in the CloudFormation template. This is a handy feature when you accidentally exceed your limit of Elastic IP addresses or don’t have access to an EC2 AMI.

EBS is a kind of permanent storage in which the data can be restored at a later point. When you save data in the EBS, it stays even after the lifetime of the EC2 instance. On the other hand, Instance Store is temporary storage that is physically attached to a host machine. With an Instance Store, you cannot detach one instance and attach it to another. Unlike in EBS, data in an Instance Store is lost if any instance is stopped or terminated.

There are three types of load balancers that are supported by Elastic Load Balancing:

1.  Application Load Balancer
2.  Network Load Balancer
3.  Classic Load Balancer

AWS WAF or AWS Web Application Firewall protects your web applications from web exploitations. It helps you control the traffic flow to your applications. With WAF, you can also create custom rules that block common attack patterns. It can be used for three cases: allow all requests, prevent all requests, and count all requests for a new policy.