aws cloudformation importing existing resources

In this demo, i am going to import an existing storage called "appjerwo-demo-test" and once i have done that I will create another s3 bucket called "myjerwo-new-bucket-2026".

To get started, I will need to have to prepare my import s3 template.

import-template.yaml

AWSTemplateFormatVersion: '2010-09-09'
Description: Import existing S3 bucket

Resources:
  ImportedAppBucket:  # ← ONLY the resource being imported
    Type: AWS::S3::Bucket
    DeletionPolicy: Retain  # ← REQUIRED for imports
    Properties:
      BucketName: appjerwo-demo-test

And then I will proceed to run the following command to create import changeset. My stack name is called my-app-stack. 


  aws cloudformation create-change-set \
  --stack-name my-app-stack \
  --change-set-name import-bucket \
  --change-set-type IMPORT \
  --template-body file://import-template.yaml \
  --resources-to-import '[{
    "ResourceType": "AWS::S3::Bucket",
    "LogicalResourceId": "ImportedAppBucket",
    "ResourceIdentifier": {"BucketName": "appjerwo-demo-test"}
  }]' \
  --capabilities CAPABILITY_NAMED_IAM --region ap-southeast-2


Next we will update specify our change set name

aws cloudformation execute-change-set \
  --stack-name my-app-stack \
  --change-set-name import-bucket --region ap-southeast-2


Once we have imported our existing resource, next we will need to add more resources to it. In this case, we are creating another s3 instance. 

full-stack.yaml 

AWSTemplateFormatVersion: '2010-09-09'
Description: Stack with imported bucket + new resources

Resources:
  ImportedAppBucket:
    Type: AWS::S3::Bucket
    DeletionPolicy: Retain  # ← Keep this!
    Properties:
      BucketName: appjerwo-demo-test

  NewS3Bucket:
    Type: AWS::S3::Bucket
    DeletionPolicy: Delete  # ← Optional (default is Delete)
    Properties:
      BucketName: myjerwo-new-bucket-2026

And now it is time for us to deploy our stack


aws cloudformation wait stack-import-complete
--stack-name my-app-stack --region ap-southeast-2

We can see that 1 new s3 instance has been created

And you can also see our stack has 2 resources 






Comments

Post a Comment

Popular posts from this blog

vllm : Failed to infer device type

Trying to run vllm without gpu will typicaly lands you into this issue. To resolve this issue: we can use set these both. Setting one does not work for me. So i had to configure both settings below:- 1.  environment variable CUDA_VISIBLE_DEVICES = "" 2. in the command line, change to use device cpu and remove  tensor-parallel-size. For example, python3 -m vllm.entrypoints.openai.api_server --port 8080 --model deepseek-ai/DeepSeek-R1 --device cpu --trust-remote-code --max-model-len 4096" References https://docs.vllm.ai/en/latest/getting_started/troubleshooting.html#failed-to-infer-device-type
Read more

android studio kotlin source is null error

Image
This org.jetbrains.kotlin.util.FileAnalysisException with a java.lang.IllegalArgumentException: source must not be null is a known issue that can sometimes occur with the Kotlin compiler. It seems to be related to how the compiler analyzes certain source code structures. When this happens, you need to go clean your project and do another rebuild.  For my case, I was trying to test out the databinding = true feature. 
Read more

gemini cli getting file not defined error

Image
 While trying to run gemini cli on my windows linux subsystem, i bump into this error here - "/Roaming/npm/node_modules/@google/gemini-cli/node_modules/undici/lib/web/webidl/index.js:512 webidl.is.File = webidl.util.MakeTypeAssertion(File)"  "ReferenceError: File is not defined" In Node.js, there’s no built-in File (until very recent Node 20+ with experimental WHATWG APIs). So, unless polyfilled, File is undefined, leading to the ReferenceError. And to resolve this, I had to upgrade to node 22 (might work for node 20) and then I was able to run it.
Read more