Amazon: Delete bucket created by Elastic Beanstalk

By -
I tested Beanstalk once and found it not suitable for my requirements, so I decided to terminate it right away. However, it had created an S3 bucket that persisted. I tried manually deleting the bucket but it gave me an 'Access Denied' error, which was odd because I had full permissions on it.

After some research, I found this quick fix:

  1. On S3 console, select the bucket and go to its Properties
  2. Expand Permissions
  3. Click on Edit bucket policy
  4.  Scroll down to where it says:
    {
    "Sid": "eb-58950a8c-feb6-11e2-89e0-0800277d041b",
    "Effect": "Deny",
    "Principal": {
                    "AWS": "*"
                },
    "Action": "s3:DeleteBucket",
    "Resource": "arn:aws:s3:::elasticbeanstalk-ap-southeast-1-662143823546"

    }
  5. Change the "Deny" value to "Allow".
  6. Save and that's it. You can now delete the bucket


Comments

Post a Comment

Popular posts from this blog

Remote Desktop to a PC not joined to AD domain

By -
Image
 In cases where you are in an Active Directory environment and you need to remote to a desktop that's not joined to that directory, or is a member of an Azure directory, the login prompt usually leads to an error. Remote machine is AAD joined. IF you are signing in to your work account, try using your work email address: There are a couple of options:  Log in via Azure web (will required 2FT if enabled) Present the login AFTER the RDC connection Here are the steps: 1. Login via Azure On Remote Desktop, click Show Options, Advanced tab Check "Use a web account to sign in to the remote computer" Click Connect Your organisation's Azure SSO login screen will appear.  2. Present the login screen AFTER connecting to RDC Go to your Documents folder and look for .rdp that you are using Right-click this file and edit using Notepad At the bottom of the file, add this line: enablecredsspsupport:i:0 authentication level:i:2 Save the file. Open Remote Desktop and connect to the co...
Read more

Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine

By -
Image
I had an issue today where an Office update caused my C# applications to stop connecting to my access database. I suddenly started getting the error: Here's how to fix it. First, confirm that you do not have Office 12.0 OLE DB Provider by opening up PowerShell and running this command (New-Object system.data.oledb.oledbenumerator).GetElements() | select SOURCES_NAME, SOURCES_DESCRIPTION This screen shot was taken after I fixed my computer. It shows ACE.OLEDB.12.0, 15.0, and 16.0. If you don't have these, run the Access 2016 runtime installer from: http://www.microsoft.com/en-us/download/details.aspx?id=50040
Read more

Windows RRAS VPN configuration when server is behind NAT

By -
The following configuration changes have to be done when the Windows VPN server (Remote Access and Routing Service) is behind NAT (ie, server has a private IP). To make PPTP work: Allow tcp/1723 traffic to flow through the firewall to the RRAS server Add inspect pptp on the firewall To make L2TP/IPSec work on Windows clients: On the client device, open Registry Editor Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent Add a DWORD (32-bit) key named AssumeUDPEncapsulationContextOnSendRule   Set the value to 2, and base to Hexadecimal Restart the client PC (this is important). Done!
Read more