Portal For Cloud, Citrix & VDI Technologies !!

Monday, 27 May 2019

AWS Route 53 Tutorial

AWS Route 53 Tutorial 


AWS Route 53 Part -I  


This is first part of Route 53 Tutorials in which I have described the basics of DNS, Resource records, Difference between CNAME and ALIAS records, and agencies involved in domain registration 



AWS Route 53 Part -II 


In This video I have demonstrated How to register a domain with ROUTE 53 in AWS, I have also shown some finer points to remember while configuring the registration of domain names. In the end of video we have checked the availability of our newly registered domain name as well by




AWS Route 53 Part -III 


This is the IIIrd video for ROUTE 53 series in which I have demonstrated how many types of routing policies are there in the ROUTE 53 and How to configure our first Simple routing policy, with demonstration



AWS Route 53 Part -IV 


In This Video I have demonstrated AWS Route 53 Weighted Routing Policy, along with the explanation of numbers we use to denote the weight of the resource records. The video also has a diagram to depict the EC2 Setup which has been used for configuring and testing the weighted routing policy.




AWS Route 53 Part -V  


In this video I have demonstrated the configuration of the Latency based routing and the points to remember while configuring the same in ROUTE 53





AWS Route 53 Part -VI 


In This Video I have demonstrated AWS Route 53 Failover Routing Policy, along with the explanation of Failover Routing I have also created and explained health check for your Active/Primary resource,





AWS Route 53 Part -VII  


In This video, we have demonstrated and configured the Geo-Location Routing in AWS Route 53. I have also discussed the use cases for using Geo location routing in Route 53,I have used Avira Phantom VPN to help in demonstration of this routing.




Share:

EC2 IAM Tutorials

EC2 IAM Tutorials 

Using IAM Roles over IAM Access Keys to sign AWS API requests has multiple benefits. For example, once enabled, you or your administrators don't have to manage credentials anymore as the credentials provided by the IAM roles are temporary and rotated automatically behind the scenes. 


You can use a single role for multiple EC2 instances within your stack, manage its access policies in one place and allow these to propagate automatically to all instances. 


Also, you can easily restrict which role a IAM user can assign to an EC2 instance during the launch process in order to stop the user from trying to gain elevated (overly permissive) privileges.

AWS IAM Part-1





AWS IAM Part-2 





AWS IAM Part-3 




AWS IAM Part-4 










Share:

Wednesday, 22 May 2019

EC2 PlacementGroups 2019|AWS EC2 Placement Group|Clustered, Partition, S...


EC2 PlacementGroups 2019|


AWS EC2 Placement Group|Clustered, Partition, S...




Share:

LinkedIN