AWS
List Of content
1. Ec2
2. AMI
3. Elastic IP vs Public IP
4. Elastic Network Interface
5. EBS (Elastic Block Storage)
6. Snapshot & Snapshot copy (one location to another location)
7. EBS Encryption
8. EFS
9. Instance Tenancy
10. Reserved Instance and Spot Instance
11. ELB (Elastic Load Balancer) (classic LB, Networking LB , Application LB)
12. Elastic Load Balancing Features
13. Cross Zone Load Balancer
14. auto scaling (vertical scaling and horizontal scaling)
15. rout53, routing-policy weighted, latency Based, geo location
16. VPC (network Acl, Sub net, Routing Table , Nat gateway, Routing table)
17. RDS(relational data services) Database service () ,Rea Replica
18. Elastic Cache
19. Dynamo DB
20. REDSHIFT
21. IAM
22. Cloud formation
23. Queue services
24. Beanstalk
25. lambda
AWS Notes Start Here
1. Image Sharing Depends On Region
2. Elastic IP Public IP Both Same
3. With out elastic ip if we start or stop the instance ip will change once we set the elastic ip it will
not change
4. Once we set the elastic ip it will not change it is permanent ip
5. Backend Connectivity for other connectivity we use nicards
6. Net work interface card is used for network connectivity
7. Its not possible multiple instances one nic card
8. Ec2-user can we change? Yes we need to create a user by using this command “userdadd”
9. Iops maxim 16gib
10. Snapshot is like backup of data (point in time backup) its also called incremental back up
11. EBS is Single Volume
12. EFS (Elastic File System) shared volume for this we can not snap shot (it not our control)
13. EFS Infrequent Access storage class means backend 2 stroge class there one is Infrequent
storage class and standard storage class
14. NFS is net work protocol
15. NFS is Shared volume with multiple ec2-instances
16. NFS Start s 0 to increases
17. Advanced Option at lunch instance
18. Round robin Algorithm use for network load balancer
19. One instance can have multiple volumes in EBS
20. For one more instance attach volumes not possible
21. One instance have multiple volumes but one ebs volume only one issuance
22. Instance store means when you
23. Burstable means increase IOPS automatically
24. Disk formats in Linux “ xfs ” and “ext4”
25. You can mount your file system from an EC2 instance with an NFSv4.1 client installed.
26. Pre-Route53 talking about the DNS Server
27. A-- > a Record
28. AAAA Means Ip Address
29. In S3 we cannot store Database
30. In IP Address /16 65 thousand, /24 25 thousand, /8 lakha of ip’s
31. ICM Means ping ,ping will work every vary
32. In VPC Response is not required for OUTBOUND Rule
33. Ips Start with 251 because of aws use 5 ips 252,253,254,255,256
34. One vpc for two servers can work, we need to different instances for each vpc
35. One ec2 instance to connect another ec2 instance(because of private key) for this we need to
use ec2 instance
36. In Data base two options for backup auto manually
37. Manually Backup means Database Snapshot
38. Automatic backup Will Delete after redemption period
39. Without file system can read instance
40. One instance have multiple volume disk direct connect in EBS but one ebs volume one instance
41. Scale Out Means Adding the server
42. Scale In Means Removing the server
43. Nat gateway only for out bond connectivity
44. IAM IS web service
45. Disable Scale in Means it will Only add Delete will not happen
46. Grace period come when service working
47. Replication means copy the same data other location
48. Routing Table tell the where your traffic go
49. Any traffic coming go through the networkACL, if Everything is fine network ACL Blocking that is
not working
50. We can not block anything at security Group , we can block at ACL
51. In ACL We configure inbound & outbound Rule but this only subnet
52. Provisioned Throughput fixed at specified amount
53. Bursting Throughput scales with file system size
54. Enable encryption 2 levels , level1 :- at rest (data come in disk resize on disk ) , level2:- at
transit (accessing through the server )
55. Security Group will allow or block the traffic
56. We can cerate load balancer(classic) in different ec , not possible in different region
57. Stickiness
58. Listener only port level in classic load balancer
59. Health Check only available application side not load balancer side
60. Network load balancer run only in TCP protocol
61. Load balancer can support more than server it will work( in single server more Ram more
CPU It will Work like Load Balancer)
62. Network load balancer use more Traffic and big applications ( Means Millions of requests or
thousand of request per second)
63. For Network load balancer not check Security Group
64. Load Balancer Available Only One Region
65. Failure always based on health check , if health check is failed not send traffic
66. While creating Target group first then we use network load balancer or classic load balancer
use TCP or UDP Protocol, For Application load balancer we use HTTP or HTTPS Protocol
67. https://aws.amazon.com/elasticloadbalancing/features/
68. AAAA Mean IPV6 Address , A Record saying Name into IP Address , TTL Means Time to
Leave
69. We can not Switch off ELB We Can only Remove
R&D
1. Nic Cards 2) Instance Store 3)throughput
2. OSI MOdel Layers
3. TCP(Transmission Control Protocol ) &UDP --> transport layer
4. http http--> application layer
5. aws support horizontal scaling
6. encryption of data at rest
7. Access points
8. What is DNS (it is use for the ip address domain name)
9. VPC PEERING
10. Target group
11. Listener
12. Intelligent-tiring, Glacier ,standard- IA, One zone IA,
13. Stateful, stateless
14. Provisioned,
TCP is a connection-oriented protocol which means a connection is established and maintained
until the application programs at each end have finished exchanging messages.
UDP (User Datagram Protocol)
UDP uses a simple connectionless communication model with a minimum of protocol mechanisms. UDP
provides checksums for data integrity, and port numbers for addressing different functions at the source and
destination of the datagram. It has no handshaking dialogues, and thus exposes the user's program to
any unreliability of the underlying network; there is no guarantee of delivery, ordering, or duplicate protection. If
error-correction facilities are needed at the network interface level, an application may use Transmission
Control Protocol (TCP) or Stream Control Transmission Protocol (SCTP) which are designed for this purpose.
This is not possible in EBS
NATGATWAY
