Cloud Migration Flashcards

(31 cards)

1
Q

Migration Strategies

Retire

A

Turn off things you don’t need

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Migration Strategies

Retain

A

Keep in your source environment or applications that you are not ready to migrate.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Migration Strategy

Relocate

A

Transfer servers, comprising one or more applications, from on-premises to cloud

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Migration Strategy

Rehost

A

Also known as lift and shift. Move your applications without making any changes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Migration Strategy

Replatform

A

Move the application and introduce some level of optimization to reduce costs, or to take advantage of cloud capabilities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Migration Strategies

Repurchase

A

Replace your application with a different version or product.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Migration Strategies

Refactor

A

Modify its architecture by taking full advantage of cloud-native features to improve agility, performance, and scalability.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

AWS Storage Gateway

A

Bridge data between on-premise and aws

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

AWS Storage Gateway

S3 File Gateway

A

S3 files accesible using NFS and SMB from on-premise. Most recently used data is cached.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

AWS Storage Gateway

Volume Gateway

A

Cloud-backed iSCSI block storage volumes to your on-premises applications

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

AWS Storage Gateway

Snapshots in a volume gateway

A

Ppoint-in-time snapshots in the form of EBS snapshots. You can use them as the starting point for a new EBS volume, which you can then attach to an EC2 instance.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Cached Volume Gateway mode

A

Primary data is stored in S3, while retaining your frequently accessed data locally in the cache for low latency access

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Stored Volume Gateway mode

A

Entire dataset is available for low latency access on premises while also asynchronously getting backed up to S3

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

AWS Snowball

A

Highly-secure portable devices to collect and process data at the edge and migrate it into AWS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

When to use AWS Snowball

A
  • Limited connectivity
  • Limited bandwidth
  • High network cost
  • Shared bandwidth
  • Conecction stability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Database Migration Service

A

With an EC2 instance perform replication tasks while the source database remains available. Supports homogeneus and heterogeneus migrations

17
Q

Database Migration Service Encryption

A

The replication instance is encrypted by KMS and cannot be disabled.

18
Q

AWS Schema Conversion Tools

A

Convert your DB schema and procedures from one engine to another

19
Q

Database Migration Service tasks

A
  • Migration of existing data (full load)
  • The application of cached changes
  • Ongoing replication (Change Data Capture)
20
Q

Snowball + Database Migration Service

A
  • Use Schema Convertion Tool to extract data locally
  • Ship the Edge device
  • Upload data to S3 and DMS migrates it to target data store
21
Q

Disaster Recovery strategies

A
  • Backup and restore (RTO 24 hours or less, RPO hours)
  • Pilot light (RTO hours, RPO minutes)
  • Warm standby (RTO minutes, RPO seconds)
  • Hot site / Multi site (RTO and RPO near-zero)
22
Q

Disaster Recovery

Pilot light

A

A small version of the app is always running in the cloud. Useful for critical core.

23
Q

Disaster Recovery

Warm standby

A

Full system is running, but with a minimum size. Upon disaster, it scales to production load.

24
Q

Disaster Recovery

Multi Site / Hot Site

A

Full scale production is running On-Premise and AWS

25
AWS Fault Injection Simulator
Based on chaos engineering, stressing an application by creating disruptive events and observing how the system responds
26
Application Discovery Service
Gather information about on-premise data centers 1. Agentless discovery: OS agnostic 2. Agent-based discovery
27
# Application Discovery Service Agentless Collector
On-premises application that collects information through agentless methods about your environment. Prerequisites: 1. An IAM user that is set up to use the managed policy AWSApplicationDiscoveryAgentlessCollectorAccess 2. Outbound access over TCP port 443 to several AWS domains
28
# Application Discovery Service Migration Hub Data Exploration
Allows Amazon Athena to analyze data collected from discovery and integrate to quicksight to visualize
29
Application Migration Service
Lift and shift solution which siplify migrating applicatins to AWS
30
Elastic Disaster Recovery
Recover your physical, virtual and cloud-based servers into AWS
31
License Manager
Manage software licenses centrally across AWS and on-premise. Rule-based controls on the consumption with hard or soft limits.