3 min read
Velero is an open-source tool that helps you backup, restore, and migrate Kubernetes resources and volumes. It provides a simple and reliable way to protect your Kubernetes applications and data from data loss or disasters. Although Velero supports multiple cloud providers, in this post we are just going to see how to install it on AWS (both using IRSA and an explicit IAM role)
12/04/2023
Read more...2 min read
When provisioning cloud resources using sceptre we can endup with plenty of errors that we'll have to track down:
$ sceptre create example
Do you want to create 'example' [y/N]: y
[2023-01-26 05:18:31] - example/s3 - Creating Stack
[2023-01-26 05:18:33] - example/s3 s3 AWS::CloudFormation::Stack CREATE_IN_PROGRESS User Initiated
[2023-01-26 05:18:37] - example/s3 Bucket AWS::ServiceCatalog::CloudFormationProvisionedProduct CREATE_IN_PROGRESS
[2023-01-26 05:18:41] - example/s3 Bucket AWS::ServiceCatalog::CloudFormationProvisionedProduct CREATE_IN_PROGRESS Resource creation Initiated
[2023-01-26 05:20:15] - example/s3 Bucket AWS::ServiceCatalog::CloudFormationProvisionedProduct CREATE_COMPLETE
[2023-01-26 05:20:20] - example/s3 s3 AWS::CloudFormation::Stack CREATE_COMPLETE
[2023-01-26 05:20:24] - example/demo-policy - Creating Stack
[2023-01-26 05:20:25] - example/demo-policy demo-policy AWS::CloudFormation::Stack CREATE_IN_PROGRESS User Initiated
[2023-01-26 05:20:29] - example/demo-policy IAMPolicy AWS::ServiceCatalog::CloudFormationProvisionedProduct CREATE_IN_PROGRESS
[2023-01-26 05:20:33] - example/demo-policy IAMPolicy AWS::ServiceCatalog::CloudFormationProvisionedProduct CREATE_FAILED Resource handler returned message: "Invalid request provided: AWS::ServiceCatalog::CloudFormationProvisionedProduct" (RequestToken: 4580f5a3-bec2-72cc-5f9f-abad3792e57a, HandlerErrorCode: InvalidRequest)
[2023-01-26 09:20:33] - example/demo-policy demo-policy AWS::CloudFormation::Stack ROLLBACK_IN_PROGRESS The following resource(s) failed to create: [IAMPolicy]. Rollback requested by user.
[2023-01-26 05:23:12] - example/demo-policy IAMPolicy AWS::ServiceCatalog::CloudFormationProvisionedProduct DELETE_COMPLETE
[2023-01-26 05:23:12] - example/demo-policy demo-policy AWS::CloudFormation::Stack ROLLBACK_COMPLETE
16/03/2023
Read more...1 min read
When we are using the output of one stack as a parameter for another one we are defining an implicit dependency: sceptre is going to create one first, get it's output and then create the other one. If we still need to create some stack after another but we are not using any output as parameter, we can still define an explicit dependency.
01/03/2023
Read more...2 min read
If you are working with Amazon Web Services (AWS), you may have heard the term "assuming a role" in the context of one role using another role. This phrase refers to the process of temporarily taking on a specific set of permissions or privileges within an AWS account, in order to perform certain actions or access specific resources.
Since when we are using the AWS console we are using a specific role to have access, we can assume another role as well.
21/02/2023
Read more...3 min read
If we try to run localstack using colima we might face the following error:
$ localstack status services
✖ ERROR: could not connect to LocalStack health endpoint at http://localhost:4566
20/02/2023
Read more...