[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7944YQZ8MH2G410QRVT3XFS":3,"skill-same:01M7944YQZ8MH2G410QRVT3XFS":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M7944YQZ8MH2G410QRVT3XFS","oraclecloud-migration-deep-dive",null,"Migrate workloads from AWS or Azure to OCI — IAM translation, networking mapping, compute image import, and data migration.\nUse when planning an AWS-to-OCI or Azure-to-OCI migration, translating cloud concepts, or importing custom images.\nTrigger with \"oraclecloud migration\", \"aws to oci\", \"azure to oci\", \"oci migration deep dive\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--oraclecloud-pack--oraclecloud-migration-deep-dive\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: oraclecloud-migration-deep-dive\ndescription: |\n  Migrate workloads from AWS or Azure to OCI — IAM translation, networking mapping, compute image import, and data migration.\n  Use when planning an AWS-to-OCI or Azure-to-OCI migration, translating cloud concepts, or importing custom images.\n  Trigger with \"oraclecloud migration\", \"aws to oci\", \"azure to oci\", \"oci migration deep dive\".\nallowed-tools: Read, Write, Edit, Bash(oci:*), Bash(python3:*), Bash(terraform:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, oraclecloud, oci]\ncompatible-with: claude-code\n---\n\n# Oracle Cloud Migration Deep Dive\n\n## Overview\n\nMigrating to OCI from AWS or Azure requires translating IAM concepts (roles to policies, accounts to compartments), networking (VPC to VCN, Security Groups to NSGs), and compute (AMI to custom image). OCI's migration tooling is underdocumented compared to AWS Migration Hub or Azure Migrate. This skill provides comprehensive concept mapping tables, custom image import procedures, network topology translation, IAM policy translation, and data migration patterns — everything needed for a controlled cloud migration.\n\n**Purpose:** Translate AWS\u002FAzure architecture into OCI equivalents and execute the migration using OCI CLI and Python SDK, with verification at each step.\n\n## Prerequisites\n\n- **OCI account** with an active tenancy — https:\u002F\u002Fcloud.oracle.com\n- **OCI CLI installed and configured** — `~\u002F.oci\u002Fconfig` validated (see `oraclecloud-install-auth`)\n- **Python 3.8+** with the OCI SDK — `pip install oci`\n- **Source cloud CLI** — `aws` CLI or `az` CLI for exporting resources\n- **Object Storage bucket** in OCI for staging image imports\n- **IAM policies**: `manage objects in compartment`, `manage custom-images in compartment`, `manage virtual-network-family in compartment`\n\n## Instructions\n\n### Step 1: AWS-to-OCI Concept Mapping\n\n| AWS Concept | OCI Equivalent | Key Differences |\n|-------------|---------------|-----------------|\n| Account | Tenancy | One tenancy = one billing entity, use compartments for isolation |\n| Organization OU | Compartment | Compartments are hierarchical, up to 6 levels deep |\n| IAM Role | IAM Policy | OCI policies use `allow group X to verb resource in compartment Y` syntax |\n| IAM User | IAM User | Same concept, but OCI uses API key auth (not access keys) |\n| VPC | VCN | VCN subnets are regional (not AZ-scoped like AWS) |\n| Security Group | Network Security Group (NSG) | NSGs attach to VNICs, not instances. Also have Security Lists (subnet-level) |\n| Route Table | Route Table | Similar, but OCI route rules target gateway OCIDs |\n| Internet Gateway | Internet Gateway | Identical concept |\n| NAT Gateway | NAT Gateway | Identical concept |\n| VPC Endpoint | Service Gateway | Service Gateway routes to OCI services without internet |\n| VPC Peering | LPG \u002F DRG | LPG for same-region, DRG for cross-region or on-premises |\n| AMI | Custom Image | Export as VMDK\u002FQCOW2, import via Object Storage |\n| EBS | Block Volume | Attachable block storage, similar performance tiers |\n| S3 | Object Storage | Compatible API (S3 compatibility mode available) |\n| RDS | Autonomous Database | Fully managed, but different administration model |\n| EC2 Instance Type | Shape | Flex shapes allow fractional OCPU allocation |\n| Availability Zone | Availability Domain (AD) | Same concept, 1-3 ADs per region |\n| CloudWatch | Monitoring Service | Uses MQL (Monitoring Query Language) instead of CloudWatch metrics |\n| CloudTrail | Audit Service | Automatic, no setup required |\n\n### Step 2: Azure-to-OCI Concept Mapping\n\n| Azure Concept | OCI Equivalent | Key Differences |\n|---------------|---------------|-----------------|\n| Subscription | Compartment | OCI uses compartments for billing isolation (not separate subscriptions) |\n| Resource Group | Compartment | Compartments are hierarchical; resource groups are flat |\n| Azure AD | OCI IAM \u002F IDCS | OCI Identity Domains replaces IDCS for SSO\u002Ffederation |\n| VNet | VCN | OCI subnets are regional, not tied to a zone |\n| NSG | NSG | Nearly identical concept |\n| Azure SQL | Autonomous Database | Different scaling model (OCPU-based) |\n| Managed Disk | Block Volume | Similar, but OCI uses volume groups for snapshots |\n| Blob Storage | Object Storage | Different API, but S3-compatible mode available |\n| Azure Monitor | Monitoring Service | MQL query language instead of Kusto |\n| Azure Policy | Cloud Guard | Detective controls, not preventive like Azure Policy |\n\n### Step 3: Custom Image Import (AWS AMI to OCI)\n\nExport the AMI from AWS, then import to OCI via Object Storage:\n\n```bash\n# Step 3a: Export AMI from AWS as VMDK\naws ec2 create-store-image-task \\\n  --image-id ami-0123456789abcdef0 \\\n  --bucket my-export-bucket\n\n# Step 3b: Download and upload to OCI Object Storage\naws s3 cp s3:\u002F\u002Fmy-export-bucket\u002Fami-0123456789abcdef0.vmdk .\u002Fimage.vmdk\n\noci os object put \\\n  --bucket-name migration-staging \\\n  --file .\u002Fimage.vmdk \\\n  --name \"imported-image.vmdk\" \\\n  --namespace \"$NAMESPACE\"\n```\n\n```python\nimport oci\n\nconfig = oci.config.from_file(\"~\u002F.oci\u002Fconfig\")\ncompute = oci.core.ComputeClient(config)\n\n# Step 3c: Import as OCI custom image\nimage = compute.create_image(\n    oci.core.models.CreateImageDetails(\n        compartment_id=\"COMPARTMENT_OCID\",\n        display_name=\"migrated-from-aws\",\n        image_source_details=oci.core.models.ImageSourceViaObjectStorageTupleDetails(\n            source_type=\"objectStorageTuple\",\n            bucket_name=\"migration-staging\",\n            namespace_name=\"NAMESPACE\",\n            object_name=\"imported-image.vmdk\",\n            source_image_type=\"VMDK\",\n        ),\n    )\n).data\n\nprint(f\"Image import started: {image.id}\")\nprint(f\"State: {image.lifecycle_state}\")  # IMPORTING → AVAILABLE\n```\n\n### Step 4: IAM Policy Translation\n\nAWS IAM roles use JSON policies attached to entities. OCI uses human-readable policy statements attached to compartments:\n\n```\n# AWS: Allow EC2 instances to read S3\n{\n  \"Effect\": \"Allow\",\n  \"Action\": [\"s3:GetObject\", \"s3:ListBucket\"],\n  \"Resource\": \"arn:aws:s3:::my-bucket\u002F*\"\n}\n\n# OCI equivalent:\nallow dynamic-group app-instances to read objects in compartment prod where target.bucket.name='my-bucket'\n```\n\nCommon IAM translations:\n\n| AWS Policy | OCI Policy Statement |\n|------------|---------------------|\n| `AdministratorAccess` | `allow group admins to manage all-resources in tenancy` |\n| `ReadOnlyAccess` | `allow group readers to inspect all-resources in tenancy` |\n| `AmazonEC2FullAccess` | `allow group compute-admins to manage instances in compartment prod` |\n| `AmazonS3ReadOnlyAccess` | `allow group readers to read objects in compartment prod` |\n| `AmazonVPCFullAccess` | `allow group net-admins to manage virtual-network-family in compartment prod` |\n\n```bash\n# Create an OCI IAM policy\noci iam policy create \\\n  --compartment-id \"$COMPARTMENT_OCID\" \\\n  --name \"app-compute-policy\" \\\n  --description \"Allow app team to manage compute in prod\" \\\n  --statements '[\"allow group app-team to manage instances in compartment prod\",\"allow group app-team to use volumes in compartment prod\"]'\n```\n\n### Step 5: Network Topology Translation\n\nTranslate an AWS VPC with public\u002Fprivate subnets into an OCI VCN:\n\n```bash\n# Export AWS VPC configuration\naws ec2 describe-vpcs --vpc-ids vpc-0123456789abcdef0 --output json > aws-vpc.json\naws ec2 describe-subnets --filters \"Name=vpc-id,Values=vpc-0123456789abcdef0\" --output json > aws-subnets.json\naws ec2 describe-route-tables --filters \"Name=vpc-id,Values=vpc-0123456789abcdef0\" --output json > aws-routes.json\n\n# Create equivalent OCI VCN\noci network vcn create \\\n  --compartment-id \"$COMPARTMENT_OCID\" \\\n  --display-name \"migrated-vcn\" \\\n  --cidr-blocks '[\"10.0.0.0\u002F16\"]' \\\n  --dns-label \"migratedvcn\"\n```\n\n### Step 6: Data Migration (S3 to Object Storage)\n\nOCI Object Storage supports S3-compatible API, enabling direct migration:\n\n```python\nimport oci\n\nconfig = oci.config.from_file(\"~\u002F.oci\u002Fconfig\")\nos_client = oci.object_storage.ObjectStorageClient(config)\nnamespace = os_client.get_namespace().data\n\n# Create destination bucket\nos_client.create_bucket(\n    namespace_name=namespace,\n    create_bucket_details=oci.object_storage.models.CreateBucketDetails(\n        compartment_id=\"COMPARTMENT_OCID\",\n        name=\"migrated-data\",\n        storage_tier=\"Standard\",\n    ),\n)\n\n# Upload objects (for large migrations, use OCI Data Transfer Service)\nwith open(\"data-export.csv\", \"rb\") as f:\n    os_client.put_object(\n        namespace_name=namespace,\n        bucket_name=\"migrated-data\",\n        object_name=\"data-export.csv\",\n        put_object_body=f,\n    )\n\nprint(f\"Uploaded to: https:\u002F\u002Fobjectstorage.{config['region']}.oraclecloud.com\u002Fn\u002F{namespace}\u002Fb\u002Fmigrated-data\u002Fo\u002Fdata-export.csv\")\n```\n\n**S3 Compatibility mode** for tools that speak S3 natively:\n\n```bash\n# OCI Object Storage S3-compatible endpoint\n# https:\u002F\u002F\u003Cnamespace>.compat.objectstorage.\u003Cregion>.oraclecloud.com\n\n# Use with aws cli (after configuring OCI customer secret keys)\naws s3 sync s3:\u002F\u002Fsource-bucket\u002F s3:\u002F\u002Fmigrated-data\u002F \\\n  --endpoint-url \"https:\u002F\u002FNAMESPACE.compat.objectstorage.us-ashburn-1.oraclecloud.com\"\n```\n\n## Output\n\nSuccessful completion produces:\n- AWS-to-OCI and Azure-to-OCI concept mapping tables for architecture translation\n- Custom image imported from VMDK into OCI compute (ready to launch instances)\n- IAM policies translated from AWS JSON format to OCI policy statements\n- Network topology (VCN, subnets, gateways) matching the source VPC\u002FVNet configuration\n- Data migrated from S3 to OCI Object Storage via direct upload or S3-compatible API\n\n## Error Handling\n\n| Error | Code | Cause | Solution |\n|-------|------|-------|----------|\n| NotAuthorizedOrNotFound | 404 | Missing IAM policy for image import | Add `allow group migrators to manage custom-images in compartment prod` |\n| InvalidParameter | 400 | Unsupported image format | OCI accepts VMDK and QCOW2 only — convert other formats first |\n| NotAuthenticated | 401 | API key misconfigured | Re-validate: `oci iam user get --user-id $(grep ^user ~\u002F.oci\u002Fconfig \\| cut -d= -f2)` |\n| TooManyRequests | 429 | Rate limited during bulk upload | Add delays between Object Storage uploads — no Retry-After header |\n| InternalError | 500 | OCI service issue | Retry after 60 seconds; check https:\u002F\u002Focistatus.oraclecloud.com |\n| Image import stuck in IMPORTING | — | Large image or Object Storage throttling | Check work request: `oci work-requests work-request get --work-request-id \u003Cid>` |\n\n## Examples\n\n**Quick migration pre-flight check:**\n\n```bash\n# Verify OCI compartment is ready\noci iam compartment get --compartment-id \"$COMPARTMENT_OCID\" \\\n  --query 'data.{name:name, state:\"lifecycle-state\"}' --output table\n\n# Verify Object Storage bucket exists\noci os bucket get --bucket-name migration-staging --namespace \"$NAMESPACE\" \\\n  --query 'data.name' --raw-output\n\n# Check image import status\noci compute image list --compartment-id \"$COMPARTMENT_OCID\" \\\n  --query 'data[?contains(\"display-name\",`migrated`)].{name:\"display-name\",state:\"lifecycle-state\"}' \\\n  --output table\n```\n\n## Resources\n\n- [OCI Migration Guide](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FMigration\u002Fhome.htm) — official migration documentation\n- [OCI Compute Custom Images](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FCompute\u002FTasks\u002Fimageimportexport.htm) — image import\u002Fexport procedures\n- [OCI S3 Compatibility API](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FObject\u002FTasks\u002Fs3compatibleapi.htm) — using S3-compatible tools with OCI\n- [OCI Python SDK Reference](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002Ftools\u002Fpython\u002Flatest\u002F) — ComputeClient, ObjectStorageClient APIs\n- [OCI CLI Reference](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FAPI\u002FConcepts\u002Fcliconcepts.htm) — command-line interface documentation\n- [OCI Terraform Provider](https:\u002F\u002Fregistry.terraform.io\u002Fproviders\u002Foracle\u002Foci\u002Flatest\u002Fdocs) — infrastructure as code for migrated workloads\n\n## Next Steps\n\nAfter migration, review `oraclecloud-reference-architecture` to validate the OCI topology, then run `oraclecloud-prod-checklist` to ensure the migrated environment meets production standards.\n","# Oracle Cloud Migration Deep Dive\n\n## Overview\n\nMigrating to OCI from AWS or Azure requires translating IAM concepts (roles to policies, accounts to compartments), networking (VPC to VCN, Security Groups to NSGs), and compute (AMI to custom image). OCI's migration tooling is underdocumented compared to AWS Migration Hub or Azure Migrate. This skill provides comprehensive concept mapping tables, custom image import procedures, network topology translation, IAM policy translation, and data migration patterns — everything needed for a controlled cloud migration.\n\n**Purpose:** Translate AWS\u002FAzure architecture into OCI equivalents and execute the migration using OCI CLI and Python SDK, with verification at each step.\n\n## Prerequisites\n\n- **OCI account** with an active tenancy — https:\u002F\u002Fcloud.oracle.com\n- **OCI CLI installed and configured** — `~\u002F.oci\u002Fconfig` validated (see `oraclecloud-install-auth`)\n- **Python 3.8+** with the OCI SDK — `pip install oci`\n- **Source cloud CLI** — `aws` CLI or `az` CLI for exporting resources\n- **Object Storage bucket** in OCI for staging image imports\n- **IAM policies**: `manage objects in compartment`, `manage custom-images in compartment`, `manage virtual-network-family in compartment`\n\n## Instructions\n\n### Step 1: AWS-to-OCI Concept Mapping\n\n| AWS Concept | OCI Equivalent | Key Differences |\n|-------------|---------------|-----------------|\n| Account | Tenancy | One tenancy = one billing entity, use compartments for isolation |\n| Organization OU | Compartment | Compartments are hierarchical, up to 6 levels deep |\n| IAM Role | IAM Policy | OCI policies use `allow group X to verb resource in compartment Y` syntax |\n| IAM User | IAM User | Same concept, but OCI uses API key auth (not access keys) |\n| VPC | VCN | VCN subnets are regional (not AZ-scoped like AWS) |\n| Security Group | Network Security Group (NSG) | NSGs attach to VNICs, not instances. Also have Security Lists (subnet-level) |\n| Route Table | Route Table | Similar, but OCI route rules target gateway OCIDs |\n| Internet Gateway | Internet Gateway | Identical concept |\n| NAT Gateway | NAT Gateway | Identical concept |\n| VPC Endpoint | Service Gateway | Service Gateway routes to OCI services without internet |\n| VPC Peering | LPG \u002F DRG | LPG for same-region, DRG for cross-region or on-premises |\n| AMI | Custom Image | Export as VMDK\u002FQCOW2, import via Object Storage |\n| EBS | Block Volume | Attachable block storage, similar performance tiers |\n| S3 | Object Storage | Compatible API (S3 compatibility mode available) |\n| RDS | Autonomous Database | Fully managed, but different administration model |\n| EC2 Instance Type | Shape | Flex shapes allow fractional OCPU allocation |\n| Availability Zone | Availability Domain (AD) | Same concept, 1-3 ADs per region |\n| CloudWatch | Monitoring Service | Uses MQL (Monitoring Query Language) instead of CloudWatch metrics |\n| CloudTrail | Audit Service | Automatic, no setup required |\n\n### Step 2: Azure-to-OCI Concept Mapping\n\n| Azure Concept | OCI Equivalent | Key Differences |\n|---------------|---------------|-----------------|\n| Subscription | Compartment | OCI uses compartments for billing isolation (not separate subscriptions) |\n| Resource Group | Compartment | Compartments are hierarchical; resource groups are flat |\n| Azure AD | OCI IAM \u002F IDCS | OCI Identity Domains replaces IDCS for SSO\u002Ffederation |\n| VNet | VCN | OCI subnets are regional, not tied to a zone |\n| NSG | NSG | Nearly identical concept |\n| Azure SQL | Autonomous Database | Different scaling model (OCPU-based) |\n| Managed Disk | Block Volume | Similar, but OCI uses volume groups for snapshots |\n| Blob Storage | Object Storage | Different API, but S3-compatible mode available |\n| Azure Monitor | Monitoring Service | MQL query language instead of Kusto |\n| Azure Policy | Cloud Guard | Detective controls, not preventive like Azure Policy |\n\n### Step 3: Custom Image Import (AWS AMI to OCI)\n\nExport the AMI from AWS, then import to OCI via Object Storage:\n\n```bash\n# Step 3a: Export AMI from AWS as VMDK\naws ec2 create-store-image-task \\\n  --image-id ami-0123456789abcdef0 \\\n  --bucket my-export-bucket\n\n# Step 3b: Download and upload to OCI Object Storage\naws s3 cp s3:\u002F\u002Fmy-export-bucket\u002Fami-0123456789abcdef0.vmdk .\u002Fimage.vmdk\n\noci os object put \\\n  --bucket-name migration-staging \\\n  --file .\u002Fimage.vmdk \\\n  --name \"imported-image.vmdk\" \\\n  --namespace \"$NAMESPACE\"\n```\n\n```python\nimport oci\n\nconfig = oci.config.from_file(\"~\u002F.oci\u002Fconfig\")\ncompute = oci.core.ComputeClient(config)\n\n# Step 3c: Import as OCI custom image\nimage = compute.create_image(\n    oci.core.models.CreateImageDetails(\n        compartment_id=\"COMPARTMENT_OCID\",\n        display_name=\"migrated-from-aws\",\n        image_source_details=oci.core.models.ImageSourceViaObjectStorageTupleDetails(\n            source_type=\"objectStorageTuple\",\n            bucket_name=\"migration-staging\",\n            namespace_name=\"NAMESPACE\",\n            object_name=\"imported-image.vmdk\",\n            source_image_type=\"VMDK\",\n        ),\n    )\n).data\n\nprint(f\"Image import started: {image.id}\")\nprint(f\"State: {image.lifecycle_state}\")  # IMPORTING → AVAILABLE\n```\n\n### Step 4: IAM Policy Translation\n\nAWS IAM roles use JSON policies attached to entities. OCI uses human-readable policy statements attached to compartments:\n\n```\n# AWS: Allow EC2 instances to read S3\n{\n  \"Effect\": \"Allow\",\n  \"Action\": [\"s3:GetObject\", \"s3:ListBucket\"],\n  \"Resource\": \"arn:aws:s3:::my-bucket\u002F*\"\n}\n\n# OCI equivalent:\nallow dynamic-group app-instances to read objects in compartment prod where target.bucket.name='my-bucket'\n```\n\nCommon IAM translations:\n\n| AWS Policy | OCI Policy Statement |\n|------------|---------------------|\n| `AdministratorAccess` | `allow group admins to manage all-resources in tenancy` |\n| `ReadOnlyAccess` | `allow group readers to inspect all-resources in tenancy` |\n| `AmazonEC2FullAccess` | `allow group compute-admins to manage instances in compartment prod` |\n| `AmazonS3ReadOnlyAccess` | `allow group readers to read objects in compartment prod` |\n| `AmazonVPCFullAccess` | `allow group net-admins to manage virtual-network-family in compartment prod` |\n\n```bash\n# Create an OCI IAM policy\noci iam policy create \\\n  --compartment-id \"$COMPARTMENT_OCID\" \\\n  --name \"app-compute-policy\" \\\n  --description \"Allow app team to manage compute in prod\" \\\n  --statements '[\"allow group app-team to manage instances in compartment prod\",\"allow group app-team to use volumes in compartment prod\"]'\n```\n\n### Step 5: Network Topology Translation\n\nTranslate an AWS VPC with public\u002Fprivate subnets into an OCI VCN:\n\n```bash\n# Export AWS VPC configuration\naws ec2 describe-vpcs --vpc-ids vpc-0123456789abcdef0 --output json > aws-vpc.json\naws ec2 describe-subnets --filters \"Name=vpc-id,Values=vpc-0123456789abcdef0\" --output json > aws-subnets.json\naws ec2 describe-route-tables --filters \"Name=vpc-id,Values=vpc-0123456789abcdef0\" --output json > aws-routes.json\n\n# Create equivalent OCI VCN\noci network vcn create \\\n  --compartment-id \"$COMPARTMENT_OCID\" \\\n  --display-name \"migrated-vcn\" \\\n  --cidr-blocks '[\"10.0.0.0\u002F16\"]' \\\n  --dns-label \"migratedvcn\"\n```\n\n### Step 6: Data Migration (S3 to Object Storage)\n\nOCI Object Storage supports S3-compatible API, enabling direct migration:\n\n```python\nimport oci\n\nconfig = oci.config.from_file(\"~\u002F.oci\u002Fconfig\")\nos_client = oci.object_storage.ObjectStorageClient(config)\nnamespace = os_client.get_namespace().data\n\n# Create destination bucket\nos_client.create_bucket(\n    namespace_name=namespace,\n    create_bucket_details=oci.object_storage.models.CreateBucketDetails(\n        compartment_id=\"COMPARTMENT_OCID\",\n        name=\"migrated-data\",\n        storage_tier=\"Standard\",\n    ),\n)\n\n# Upload objects (for large migrations, use OCI Data Transfer Service)\nwith open(\"data-export.csv\", \"rb\") as f:\n    os_client.put_object(\n        namespace_name=namespace,\n        bucket_name=\"migrated-data\",\n        object_name=\"data-export.csv\",\n        put_object_body=f,\n    )\n\nprint(f\"Uploaded to: https:\u002F\u002Fobjectstorage.{config['region']}.oraclecloud.com\u002Fn\u002F{namespace}\u002Fb\u002Fmigrated-data\u002Fo\u002Fdata-export.csv\")\n```\n\n**S3 Compatibility mode** for tools that speak S3 natively:\n\n```bash\n# OCI Object Storage S3-compatible endpoint\n# https:\u002F\u002F\u003Cnamespace>.compat.objectstorage.\u003Cregion>.oraclecloud.com\n\n# Use with aws cli (after configuring OCI customer secret keys)\naws s3 sync s3:\u002F\u002Fsource-bucket\u002F s3:\u002F\u002Fmigrated-data\u002F \\\n  --endpoint-url \"https:\u002F\u002FNAMESPACE.compat.objectstorage.us-ashburn-1.oraclecloud.com\"\n```\n\n## Output\n\nSuccessful completion produces:\n- AWS-to-OCI and Azure-to-OCI concept mapping tables for architecture translation\n- Custom image imported from VMDK into OCI compute (ready to launch instances)\n- IAM policies translated from AWS JSON format to OCI policy statements\n- Network topology (VCN, subnets, gateways) matching the source VPC\u002FVNet configuration\n- Data migrated from S3 to OCI Object Storage via direct upload or S3-compatible API\n\n## Error Handling\n\n| Error | Code | Cause | Solution |\n|-------|------|-------|----------|\n| NotAuthorizedOrNotFound | 404 | Missing IAM policy for image import | Add `allow group migrators to manage custom-images in compartment prod` |\n| InvalidParameter | 400 | Unsupported image format | OCI accepts VMDK and QCOW2 only — convert other formats first |\n| NotAuthenticated | 401 | API key misconfigured | Re-validate: `oci iam user get --user-id $(grep ^user ~\u002F.oci\u002Fconfig \\| cut -d= -f2)` |\n| TooManyRequests | 429 | Rate limited during bulk upload | Add delays between Object Storage uploads — no Retry-After header |\n| InternalError | 500 | OCI service issue | Retry after 60 seconds; check https:\u002F\u002Focistatus.oraclecloud.com |\n| Image import stuck in IMPORTING | — | Large image or Object Storage throttling | Check work request: `oci work-requests work-request get --work-request-id \u003Cid>` |\n\n## Examples\n\n**Quick migration pre-flight check:**\n\n```bash\n# Verify OCI compartment is ready\noci iam compartment get --compartment-id \"$COMPARTMENT_OCID\" \\\n  --query 'data.{name:name, state:\"lifecycle-state\"}' --output table\n\n# Verify Object Storage bucket exists\noci os bucket get --bucket-name migration-staging --namespace \"$NAMESPACE\" \\\n  --query 'data.name' --raw-output\n\n# Check image import status\noci compute image list --compartment-id \"$COMPARTMENT_OCID\" \\\n  --query 'data[?contains(\"display-name\",`migrated`)].{name:\"display-name\",state:\"lifecycle-state\"}' \\\n  --output table\n```\n\n## Resources\n\n- [OCI Migration Guide](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FMigration\u002Fhome.htm) — official migration documentation\n- [OCI Compute Custom Images](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FCompute\u002FTasks\u002Fimageimportexport.htm) — image import\u002Fexport procedures\n- [OCI S3 Compatibility API](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FObject\u002FTasks\u002Fs3compatibleapi.htm) — using S3-compatible tools with OCI\n- [OCI Python SDK Reference](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002Ftools\u002Fpython\u002Flatest\u002F) — ComputeClient, ObjectStorageClient APIs\n- [OCI CLI Reference](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FAPI\u002FConcepts\u002Fcliconcepts.htm) — command-line interface documentation\n- [OCI Terraform Provider](https:\u002F\u002Fregistry.terraform.io\u002Fproviders\u002Foracle\u002Foci\u002Flatest\u002Fdocs) — infrastructure as code for migrated workloads\n\n## Next Steps\n\nAfter migration, review `oraclecloud-reference-architecture` to validate the OCI topology, then run `oraclecloud-prod-checklist` to ensure the migrated environment meets production standards.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","oraclecloud","oci","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Migrate workloads from AWS or Azure to OCI — IAM translation, networking mapping, compute image import, and data migration.\nUse when planning an AWS-to-OCI or Azure-to-OCI migration, translating cloud concepts, or importing custom images.\nTrigger with \"oraclecloud migration\", \"aws to oci\", \"azure to oci\", \"oci migration deep dive\".\n","Read, Write, Edit, Bash(oci:*), Bash(python3:*), Bash(terraform:*), Grep","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--oraclecloud-pack--oraclecloud-migration-deep-dive",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill oraclecloud-migration-deep-dive",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill oraclecloud-migration-deep-dive",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill oraclecloud-migration-deep-dive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--oraclecloud-pack--oraclecloud-migration-deep-dive\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]