Skip to main content

Preventing accidentally resource deletion - Lock Resource | Azure

A week ago, one of our team member modified a script that clean (removes) Azure resources, based on a naming convention. Because the number of our Azure Subscription is limited, the Development Team is sharing the same subscription between them and for DEV and TEST environment.
To be able to have a control on resources and trace the owner of them we have:
  • Naming conventions: A prefix that specify the owner of the resource or the environment

    • rvteststorage (rv - Radu Vunvulea)
    • dv (Dev Environment) 
    • tt (Test Environment)
    • ...
  • Azure Resource Groups that give us the possibility to group resources together.
 
As we can see in the above diagram, Azure Resource Groups can be used with success to group together different resources that have a logic for your application or from a business perspective. 

Coming back to the initial cleaning script, there was a small bug in the script, that didn't took into account the prefix of Azure Resource Groups and removed all the resources that were under that subscription. 

Now, the questions is what we can do to avoid  this kind of things in the future. Of course, multiple subscriptions would be great, but this will not happen. A review of the script from another team member would work also, but not all the time there will be time for things like this and bugs like this cannot be seen each time.

How nice it would be to have a flag on our resources, that would not allow anybody to remove (delete) the resources. This features exist on AWS for some time and wait.... we forgot that from last year we have a similar feature on Azure also. 
This feature is called "Resource Lock" and allows us to lock a resource for deletion. People will be able to modify it, but as long as this flag is set, nobody will be able to delete this resource. In this way we can avoid in the future situations like this.
This lock can be set not only when we create the resource, but also after it and can be used for any time of resource. The Lock can be set using Power Shell by specifying LockLevel flag to 'CanNotDelete' of using ARM.

Power Shell
$resourceGroup = 'devenv'
$storageAccountName = 'devlogstorage'

New-AzureResourceLock -LockLevel CanNotDelete '
-LockNotes 'Delete is not allowed for DEV env storage' `
-LockName 'DevEnvStorageLock' `
-ResourceName $storageAccountName `
-ResourceType 'Microsoft.Storage/storageAccounts' `
-ResourceGroup $resourceGroup -Verbose

More information about this feature can be found on Azure page: https://azure.microsoft.com/en-us/documentation/articles/resource-group-lock-resources/

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP