Q2) One of the user delete on sever in AWS account how do you find them ?
Cloud trail
Q3)By Default how many days event should be stored ?
90 days
Q4)Can we filter events separately for a resource ?
Yes
We can not able delete the event trail
--Thanks
Content delivery network(CDN)
It will help to Steaming the browser live events
Used to deliver app from edge location
It gives fast response
ex: cricket matches ,e-commerce sales..etc
User -->Edge Location -->App server
Edge location Application information exist in the edge location also
Origin -->Original server for ex:-S3,ELB,API GATEWAY
Here below flow chart
First time user give the request it will go through cloud front fetch image from the s3 bucket
we get response from S3 bucket origin send to cloud front and then send to response user .
Second time user
Users request images through a web or mobile application.
The application constructs URLs pointing to CloudFront distributions associated with the S3 buckets.
CloudFront serves the cached images from the nearest edge location, reducing latency and improving performance.
If the requested image or transformation is not cached, CloudFront fetches it from S3. If the fetch from S3 results in a 404 error (image not found), Lambda@Edge will be triggered to serve a default image. Alternatively you can set up CloudFront with origin failover (fallback to another S3 bucket or a web server) for scenarios that require high availability.
Advantages:
1.Reduce Latency
2.Cut cost
3.Customize Delivery
4.Security
Free Tier :
1 TB of data transfer not
10,000,000 (10 million) Http or Https request
2,00,0000 Cloud front function invocations
Each month , always free
Load Balancer (Between two servers control the traffic, we used load balancer)
Create load balancer >Application load balancer
Load balancer name:Amazon
Click Create Load balancer
It will take time to create the Load balancer
Loader Balance :If 100 user hint the application we have two server equally divided the session between two servers(Server1 Server2), usually need two server for load balancer
General we can access the server using IP, but load balancer we can access though DNS
Came to Active Below screen shot
So far we can access application use public ip
http://54.198.190.185/
now we able access the server using Dns name also using below url, shown screen shot
http://amazon-542509.us-east-1.elb.amazonaws.com/
Step1:Create 2 servers and deploy amazon app --done (as of now one server exist)
Step2:Create load balancer --Done
Step3:Cloud front -->Original domain ELB(select your LB) -->Protocal :HTTP only (original Protocol)
-->Enable Origin Shield (cache will store): us-east-1b -->Protocol: HTTPS(Cloud front protocol) -->
Select WAF --> IPv6: OFF -->CREATE
AWS console type >cloud front
Create a CloudFront distribution
Distribution options
.Single website or app
Select the region where your application server exist
So far your HTTP, once protocol enabled Shield, our application will load to https also
Finally WAF(Web application firewall)enabled , Treads will control for this
Click Create distribution, it will take 2 mint enabled and last modified deployed to update the date.
Now Last modified change date and time , now Copy the distribution domain name, try to access website.
See now ,Application access https for reference , i have copied the domain name in search box .
No comments:
Post a Comment