Skip to main content

Preventing accidentally resource deletion - Lock Resource | Azure

By
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/
Labels:

Comments

Post a Comment

Popular posts from this blog

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

By
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(...
Post a Comment
Read more

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more