AWS Notes - Migrations - AWS Storage Gateway

-

Summary: A bridge between on-premise data and S3, Mount S3 to on-premise as a storage device.

Use case: Disaster recovery, backup & Restore, Tiered storage

Type :

  1. (S3) File Gateway : NFS/SMB protocols
    • Replicate the local data to Amazon S3
    • Support S3/S3-IA/S3 One zone - IA
    • Support Object Versioning
    • Support Object Lock
    • Examples: Extensions(AWS services), Read-only Replicas, Backup and Lifecycle Policies
  2. Tape Gateway
    1. Replace the Tape to S3(Glacier/Glacier Deep Archive)
  3. Volume Gateway : iSCSI protocal
    • Up to 32 volumes per Gateway
    1. Cached Volumes : Frequently accessed S3 Data
    2. Stored Volumes : low-latency, as a Snapshot 
  4. FXs File Gateway
    • Local cache for frequently accessed data
    • Used for File shares.
    • Windows native compatibility


    Reference
    1. https://docs.aws.amazon.com/storagegateway/index.html
    2. https://tutorialsdojo.com/aws-storage-gateway/

    Comments

    Post a Comment

    Popular posts from this blog

    AWS Notes - Network - TransferFamily(Transfer) connect with EFS

    -
    1. AWS EC2 connects to EFS create EFS and create EC2 EFS's DNS:fs-XXXXXXX.efs.ap-northeast-1.amazonaws.com add security group add nfs port(2049) to EFS inbound rules (IP: EC2's local IP) use the command below to mound the EFS to EC2 a. install efs tools sudo yum install amazon-efs-utils b.mount the EFS sudo mount -t efs -o tls fs-XXXXX:/ ~/efs-mount 2. Create Transfer Create transferFamily's Endpoint Protocols: SFTP Identity Provider: Service Managed Endpoint : s-XXXXXXXXX.server.transfer.ap-northeast-1.amazonaws.com Endpoint Type: Public 3. Create User to connect Transfer to EFS Create a role to connect transfer to EFS a.Create Policies { "Version": "2012-10-17", "Statement": [ { "Sid": "GrantTransferRoleAccess", "Effect": "Allow", "Action": [ "elasticfilesystem:ClientRootAccess", "elasticfilesystem:ClientWrite", "elasticfilesystem:ClientMount" ], "Resource...
    Read more

    Build JupyterNotebook(Anaconda) environment in AWS EC2

    -
    Key words: JupyterNotebook, Anaconda, AWS, EC2, Proxy, Winscp, Putty, DeepLearning <Background> The company employs a proxy server, through which all external connections must pass. Company computers utilize Virtual Desktop Infrastructure (VDI), restricting the installation of large software such as Anaconda. <Task> As a Deep Learning engineer, it is necessary to set up a Jupyter Notebook environment on AWS cloud. However, services like SageMaker are costly, thus requiring a self-built environment on AWS EC2. <AWS EC2 Configuration> Create an EC2 Instance with the following specifications: AMI: Ubuntu/Amazon Linux 2 AMI CPU: t3.large VPC: Public subnet with an Internet Gateway (IGW) Elastic IP: Required, as dynamic IP addresses are prone to firewall interception. Security Group: Inbound ports 8081 (Jupyter) and 22 (SSH) should be open; all outbound ports should be accessible. Storage: Minimum of 16GB, as Anaconda alone requires 9GB. Key Pair: Generate an RSA key pair,...
    Read more

    AWS Notes - DevOps - OpsWorks

    -
    AWS OpsWorks = Managed Chef & Puppet Feature Chef & Puppet help you perform server configuration automatically, or repetitive actions. Work Great with EC2 & On-premise VM Better for users of Chef & Pupper, Not good to migrating from other tech. Chef has more detailed configuration than Beanstalk
    Read more