AWS Artifact LAB

1. Enable Artifact in Your Account

• Navigate to the Artifact console: In the AWS Management Console, search for "Artifact" and select the Artifact service.
• Enable Artifact: Click on "Enable Artifact".

enabling Artifact in the AWS Management Console

2. Select Your Region

• Choose a region: Select the region where you want to create your Artifact repository.
 
selecting a region in the AWS Artifact console

3. Create an Artifact Repository

• Create a repository: Click on "Create repository".
• Name your repository: Give your repository a unique name.
• Choose a format: Select the desired report format (PDF, CSV, or JSON).
• Create the repository: Click on "Create repository".

creating an Artifact repository in the AWS Artifact console

4. Configure Your Repository

• Add reports: Add the desired reports to your repository. Artifact supports a variety of reports, including compliance reports, configuration reports, and usage reports.

adding reports to an Artifact repository

• Schedule reports: Schedule reports to be generated automatically on a regular basis.

scheduling reports in the AWS Artifact console

5. Access Your Reports

• View reports: Once your reports are generated, you can view them in the Artifact console.

viewing reports in the AWS Artifact console

• Download reports: Download reports in your desired format.

downloading reports from the AWS Artifact console

6. Manage Your Repository

• Delete reports: Delete reports that are no longer needed.
• Modify repository settings: Modify repository settings as needed.
• Share reports: Share reports with others within your organization or with third-party auditors.

 

AWS Storage Gateway Labs

 

AWS Storage Gateway is a hybrid cloud storage service that extends your on-premises storage to the cloud. It provides file gateway, volume gateway, and tape gateway options to seamlessly integrate your on-premises storage with AWS services.

File Gateway Labs

1. Create a File Gateway

• Navigate to the Storage Gateway console: In the AWS Management Console, search for "Storage Gateway" and select the Storage Gateway service.
• Create a file gateway: Click on "Create file gateway".
• Choose a gateway type: Select "File gateway".
• Configure gateway settings: Specify the desired gateway settings, such as the VPC, subnet, and storage capacity.
• Create the gateway: Click on "Create gateway".

creating a file gateway in the AWS Management Console

2. Mount the File Gateway

• Mount target: In the Storage Gateway console, click on the file gateway you created.
• Create a mount target: Click on "Create mount target".
• Choose a subnet: Select the subnet where you want to mount the file gateway.
• Create the mount target: Click on "Create mount target".

creating a mount target for a file gateway

• Mount the gateway: Using an SSH client or EC2 instance, mount the file gateway using the provided mount point and security credentials. For example:

Bash

sudo mount -t nfs -o nfsvers=4.1,addr=<mount_target_dns_name> <mount_point>

Use code with caution.

Replace <mount_target_dns_name> with the DNS name of your mount target and <mount_point> with the desired mount point on your instance.

Volume Gateway Labs

1. Create a Volume Gateway

• Navigate to the Storage Gateway console: In the AWS Management Console, search for "Storage Gateway" and select the Storage Gateway service.
• Create a volume gateway: Click on "Create volume gateway".
• Choose a gateway type: Select "Volume gateway".
• Configure gateway settings: Specify the desired gateway settings, such as the VPC, subnet, and storage capacity.
• Create the gateway: Click on "Create gateway".

creating a volume gateway in the AWS Management Console

2. Attach a Volume

• Attach a volume: In the Storage Gateway console, click on the volume gateway you created.
• Attach a volume: Click on "Attach volume".
• Choose a volume: Select the volume you want to attach.
• Attach the volume: Click on "Attach volume".

attaching a volume to a volume gateway

• Mount the volume: Using an SSH client or EC2 instance, mount the volume using the provided mount point and security credentials. For example:

Bash

sudo mount -t nfs -o nfsvers=4.1,addr=<mount_target_dns_name> <mount_point>

Use code with caution.

Replace <mount_target_dns_name> with the DNS name of your mount target and <mount_point> with the desired mount point on your instance.

Tape Gateway Labs

1. Create a Tape Gateway

• Navigate to the Storage Gateway console: In the AWS Management Console, search for "Storage Gateway" and select the Storage Gateway service.
• Create a tape gateway: Click on "Create tape gateway".
• Choose a gateway type: Select "Tape gateway".
• Configure gateway settings: Specify the desired gateway settings, such as the VPC, subnet, and storage capacity.
• Create the gateway: Click on "Create gateway".

creating a tape gateway in the AWS Management Console

2. Import Tapes

• Import tapes: In the Storage Gateway console, click on the tape gateway you created.
• Import tapes: Click on "Import tapes".
• Select tapes: Select the tapes you want to import.
• Import the tapes: Click on "Import tapes".

importing tapes to a tape gateway

3. Manage Tapes

• List tapes: View the list of tapes stored in your tape gateway.
• Retrieve tapes: Retrieve tapes from your tape gateway.
• Delete tapes: Delete tapes that are no longer needed.

S3 Glacier LAB

 

1. Create an S3 Glacier Vault

• Navigate to the S3 Glacier console: In the AWS Management Console, search for "Glacier" and select the S3 Glacier service.
• Create a vault: Click on "Create vault".
• Name your vault: Give your vault a unique name.
• Choose a region: Select the region where you want to store your vault.
• Create the vault: Click on "Create vault".

creating an S3 Glacier vault in the AWS Management Console

2. Archive Data to the Vault

• Archive data: Use the AWS CLI, AWS SDKs, or the S3 Glacier console to archive data to your vault.
• Specify a job: When archiving data, you need to specify a job that defines the source data, destination vault, and other relevant parameters.

archiving data to an S3 Glacier vault using the AWS CLI

3. Retrieve Data from the Vault

• Retrieve data: Use the AWS CLI, AWS SDKs, or the S3 Glacier console to retrieve data from your vault.
• Specify a job: When retrieving data, you need to specify a job that defines the source vault, destination, and other relevant parameters.

retrieving data from an S3 Glacier vault using the AWS CLI

4. Manage Your Vault

• List jobs: View the list of jobs associated with your vault.
• Cancel jobs: Cancel jobs that are in progress.
• Delete vaults: Delete vaults that are no longer needed.

5. Consider Different Storage Classes

• Standard: For data that needs to be retrieved within a few hours.
• Deep Archive: For data that is rarely accessed and can be retrieved within days.
• Expedited: For data that needs to be retrieved within minutes.

S3 LAB

 

1. Create an S3 Bucket

• Navigate to the S3 console: In the AWS Management Console, search for "S3" and select the S3 service.
• Create a bucket: Click on "Create bucket".
• Name your bucket: Give your bucket a unique name.
• Choose a region: Select the region where you want to store your bucket.
• Create the bucket: Click on "Create bucket".

creating an S3 bucket in the AWS Management Console

2. Upload Objects to the Bucket

• Upload objects: Click on the name of your bucket.
• Upload files: Drag and drop files or folders into the bucket, or use the "Upload" button to select files.
• Configure upload options: You can configure upload options such as object properties, encryption, and storage class.

uploading objects to an S3 bucket

3. Access and Manage Objects

• List objects: View the list of objects stored in your bucket.
• Download objects: Download objects to your local machine.
• Delete objects: Delete objects that you no longer need.
• Manage object properties: Modify object properties such as metadata, tags, and lifecycle rules.

4. Configure Bucket Properties

• Bucket policies: Control access to your bucket using bucket policies.
• Bucket encryption: Enable server-side encryption for your bucket.
• Bucket lifecycle rules: Configure lifecycle rules to automatically manage object retention and transition.
• Bucket versioning: Enable versioning to track changes to objects and recover deleted objects.

configuring bucket properties in the AWS Management Console

5. Integrate with Other AWS Services

• S3 Transfer Acceleration: Improve data transfer speeds to and from S3.
• Amazon CloudFront: Distribute content from S3 to users worldwide.
• AWS Lambda: Trigger Lambda functions in response to S3 events.
• Amazon Glacier: Store data in S3 Glacier for long-term, low-cost storage.

AWS FSx Labs

 

AWS FSx Labs

AWS FSx is a managed file system service that provides high-performance file storage for your cloud applications. It offers two main file system types: Windows File Server (FSx-Windows) and Lustre (FSx-Lustre).

FSx-Windows Labs

1. Create an FSx-Windows File System

• Navigate to the FSx console: In the AWS Management Console, search for "FSx" and select the FSx service.
• Create a file system: Click on "Create file system".
• Choose a file system type: Select "Windows File Server".
• Configure file system settings: Specify the desired file system settings, such as the VPC, subnet, and storage capacity.
• Create the file system: Click on "Create file system".

creating an FSxWindows file system in the AWS Management Console

2. Mount the FSx-Windows File System

• Mount target: In the FSx console, click on the file system you created.
• Create a mount target: Click on "Create mount target".
• Choose a subnet: Select the subnet where you want to mount the file system.
• Create the mount target: Click on "Create mount target".

creating a mount target for an FSxWindows file system

• Mount the file system: Using an SSH client or EC2 instance, mount the FSx-Windows file system using the provided mount point and security credentials. For example:

Bash

sudo mount -t nfs -o nfsvers=4.1,addr=<mount_target_dns_name> <mount_point>

Use code with caution.

Replace <mount_target_dns_name> with the DNS name of your mount target and <mount_point> with the desired mount point on your instance.

FSx-Lustre Labs

1. Create an FSx-Lustre File System

• Navigate to the FSx console: In the AWS Management Console, search for "FSx" and select the FSx service.
• Create a file system: Click on "Create file system".
• Choose a file system type: Select "Lustre".
• Configure file system settings: Specify the desired file system settings, such as the VPC, subnet, storage capacity, and performance mode.
• Create the file system: Click on "Create file system".

creating an FSxLustre file system in the AWS Management Console

2. Mount the FSx-Lustre File System

• Mount target: In the FSx console, click on the file system you created.
• Create a mount target: Click on "Create mount target".
• Choose a subnet: Select the subnet where you want to mount the file system.
• Create the mount target: Click on "Create mount target".

creating a mount target for an FSxLustre file system

• Mount the file system: Using an SSH client or EC2 instance, mount the FSx-Lustre file system using the provided mount point and security credentials. For example:

Bash

sudo mount -t lustre -o nfsvers=4.1,addr=<mount_target_dns_name> <mount_point>

Use code with caution.

Replace <mount_target_dns_name> with the DNS name of your mount target and <mount_point> with the desired mount point on your instance.

AWS Elastic Disaster Recovery LAB

 

1. Set Up On-Premises Replication

• Install the EDR agent: Install the EDR agent on your on-premises servers that you want to replicate.
• Configure replication: Configure the agent to replicate your workloads to AWS.
• Test replication:
  Verify that the replication is working as expected.

installing the EDR agent on an onpremises server

2. Create a Replication Instance

• Create a replication instance: In the AWS Management Console, navigate to the EDR service and create a replication instance.
• Choose a VPC and subnet: Select the VPC and subnet where you want to create the replication instance.
• Configure replication settings: Configure the replication settings for your on-premises workloads.

creating a replication instance in the AWS Management Console

3. Create a Recovery Point

• Create a recovery point: Once the replication instance is running, create a recovery point to capture a snapshot of your on-premises workloads.
• Schedule recovery points: Schedule regular recovery points to ensure that you have up-to-date backups.

creating a recovery point in the AWS Management Console

4. Test Disaster Recovery

• Trigger a failover: Simulate a disaster by triggering a failover to AWS.
• Test application functionality: Verify that your applications are running correctly in the AWS environment.
• Perform a failback: If necessary, perform a failback to your on-premises environment.

triggering a failover in the AWS Management Console

5. Manage and Monitor

• Monitor replication: Monitor the replication process to ensure that it is running smoothly.
• Manage recovery points: Manage your recovery points to optimize storage costs and ensure that you have the latest backups.
• Update replication settings: Update the replication settings as needed to reflect changes in your on-premises environment.

EFS LAB

 

1. Create an EFS File System

• Navigate to the EFS console: In the AWS Management Console, search for "EFS" and select the EFS service.
• Create a file system: Click on "Create file system".
• Choose a file system type: Select either "General Purpose" or "Infrequent Access" based on your access patterns.
• Configure performance: Choose the desired performance mode for your file system.
• Select a VPC and subnet: Specify the VPC and subnet where you want to create the file system.
• Create the file system: Click on "Create file system".

creating an EFS file system in the AWS Management Console

2. Mount the EFS File System

• Mount target: In the EFS console, click on the file system you created.
• Create a mount target: Click on "Create mount target".
• Choose a subnet: Select the subnet where you want to mount the file system.
• Create the mount target: Click on "Create mount target".

creating a mount target for an EFS file system

• Mount the file system: Using an SSH client or EC2 instance, mount the EFS file system using the provided mount point and security credentials. For example:

Bash

sudo mount -t nfs -o nfsvers=4.1,addr=<mount_target_dns_name> <mount_point>

Replace <mount_target_dns_name> with the DNS name of your mount target and <mount_point> with the desired mount point on your instance.

3. Access and Use the EFS File System

• Access files: Once the file system is mounted, you can access and manipulate files using standard file system operations like ls, mkdir, cp, and rm.
• Create and modify files: Create new files and modify existing files using your preferred text editor or application.
• Store data: Use the EFS file system to store data for your applications or workloads.

4. Manage the EFS File System

• Modify performance: Adjust the performance mode of your file system as needed.
• Create snapshots: Create snapshots of your file system to create backups or restore to a previous state.
• Manage lifecycle: Manage the lifecycle of your file system by deleting it when it's no longer needed.

Installing and Removing Packages

 1. Update package lists:

This step ensures that your package manager has the latest information about available packages.

terminal showing sudo apt update command

Bash

sudo apt update

2. Search for a package:

Use the package manager's search function to find the specific package you want to install.

terminal showing sudo apt search command

Bash

sudo apt search <package_name>

3. Install the package:

Use the package manager's installation command to install the package.

terminal showing sudo apt install command

Bash

sudo apt install <package_name>

Removing Packages

1. Remove the package:

Use the package manager's removal command to uninstall the package.

terminal showing sudo apt remove command

Bash

sudo apt remove <package_name>

2. Remove configuration files:

If you want to completely remove the package, including its configuration files, use the purge option.

terminal showing sudo apt purge command

Bash

sudo apt purge <package_name>