𝐄𝐁𝐒 - 𝐄𝐥𝐚𝐬𝐭𝐢𝐜 𝐁𝐥𝐨𝐜𝐤 𝐒𝐭𝐨𝐫𝐚𝐠𝐞 - Its a block level storage, which means the data is stored as block chunks. An EBS volume can be shrink or expanded according to our requirement. We have various types of EBS volumes such as General purpose SSD, Provisioned IOPS, etc.
When you create an EC2 Windows instance post attaching an EBS volume, login to the EC2 instance and we can do manual partition of volumes. The root volume of an EC2 instance consists of Operating System so it has to be minimum 100 GB, The other volumes that you create for a Linux instance can be mounted by following the below steps.
- lsblk ( lists the available volumes attached to the disk)
- mkdir newdisk (creates a directory named newdisk)
- mkfs -t ext4 /volumename -- that is the unattached volume is formatted here)
- mount /dev/xvdf( un attached volume) /newdisk Thus an EBS volume gets mounted and ready for use in Linux EC2 machine. 𝐄𝐅𝐒 - 𝐄𝐥𝐚𝐬𝐭𝐢𝐜 𝐅𝐢𝐥𝐞 𝐒𝐲𝐬𝐭𝐞𝐦 - Its a file level storage which can be shared with multiple EC2 instances
- Create two or more EC2 Machine, create security groups
- Create an EFS system, create a security group, allow the EC2 machines security group as inbound rule, NFS default port. Login to your EC2 machines and create mkdir EFS, install amazon efs utils and follow the commands to mount the EFS volumes to multiple EC2 instances one by one. EFS systems is auto scalable. In the command given by amazon in pop ups/console the filesystem id has to be replaced with the EFS file system id that we created. 𝐀𝐖𝐒 𝐂𝐨𝐧𝐟𝐢𝐠 - Any configuration changes we make in our AWS account can be monitored here, AWS provides many configuration rules. For example any mfa disabled or EC2 tag name changes then it can be made to get notified to the user/customer via SNS email notification. The notifications can be stored in a S3 bucket as well using Lambda function, Cloud watch log group. AWS Cloud Trail - The activities done by an IAM user can be identified by enabling the Cloud Trail service. Any API calls made in an AWS account can be identified using Cloud Trail. AWS Backup - When you create an EC2 instance you can create a full image of it ( a kind of snapshot backup where it is point in time copy storage concept, the image you created can be used to create a new instance with all data), Its always a good practice to create a full image of your EC2 machines and name it with appropriate tags). Rather than doing these manually, we can enable AWS Backup service and specify the resources to be backed up based on intervals like 8 hours once, 12 hours once, 24 hours once etc. The resources can be EC2, Storage, Database, S3, EFS etc. #aws #awscloud #awscommunitybuilders
My articles - https://lnkd.in/gq7fdDvR
Top comments (0)