Jump to content

Search the Community

Showing results for tags 'Azure'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Categories

  • autoexec.gr
  • Events
  • Γενικά

Forums

  • Γενικά
    • Τα πρωτοσέλιδα
    • Café
    • Λοιπά Θέματα
    • Ειδήσεις & Εκδηλώσεις
  • Προϊόντα
    • Εργαλεία και συμβουλές
    • Microsoft Office
    • Windows
    • Windows Server
    • Microsoft SQL Server
    • Exchange Server
    • SharePoint Server
    • Microsoft Hyper-V
    • Microsoft Azure
    • PowerShell
  • Τεχνολογία
    • Cloud
    • Virtualization
    • Management & Automation
  • Εκπαίδευση & Πιστοποίηση
    • Εκπαίδευση
    • Πιστοποίηση
  • Αγγελίες
    • Προσφορά Εργασίας
    • Αγοραπωλησίες
  • Archives
    • Γενικά
    • Εργαλεία και συμβουλές
    • Hardware
    • OS
    • Servers
    • Netwok & Security
    • Magazino

Blogs

  • Το προσωπικό σου blog
  • Bits & Bytes
  • Το Ελληνικό Exchange Blog
  • Ioannis Alexopoulos -- IT Blog
  • Εξομολογήσεις ενός διαχειριστή
  • Για την αντι-γραφή
  • spanougakis.com
  • Project Management: Art or Science? Profession or Competence?
  • BlackTrack
  • Hyper-Vangelis
  • Frees Point
  • Klag Rulez
  • Heimaros
  • Info Overflow
  • The dark side
  • Greek Active Directory Blog
  • The Greek Windows PKI blog
  • Greek Geek Girls "3G"
  • Tips, Tricks and Recipes for IT Pros
  • There is nothing like 127.0.0.1
  • kpsalida's Blog
  • απλά...το βλογ μου
  • Θέλω να γίνω τσομπάνης!
  • Holy IT
  • Admin
  • Catastrophic Failure
  • Rocking with Knowledge of SQL Server
  • Apple Macintosh in the Enteprise
  • Firewall In A Nutshell
  • The Infrastructurer
  • Smart Office
  • Το άδειο σεντούκι
  • iThalis
  • Παιδιά! Έχουμε mail ?
  • SBS & όχι μόνο , Ioannis Zontos
  • Paradigm Shift
  • Αη-Τι (ο άγιος Τι)
  • The TroubleShooter
  • George Markou's Blog
  • fmarkos' Blog
  • dead:beef::1
  • Vaggelis' Blog
  • Proxima's IT Admin Corner

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Occupation

Found 22 results

  1. At the previous post we created an Azure Front Door to scale our web apps across Azure Regions and also publish them only through the Front Door’s URL. At this post we will create Web Application Firewall (WAF) rules, to protect our web apps. To add WAF functionality to the Front Door we need first to create WAF rules and then attach them to the Front Door Create the WAF Rule From the Azure Marketplace search for WAF and create a Web Application Firewall At the “Create a WAF policy” wizard select “Global WAF (Front Door) for policy, provide the subscription and resource group, give a name for the policy and select if you want it to be created enabled or disabled. At the next step select if the policy will prevent the action or just detect and report it. You can change this later too. You can provide a Redirect URL for rules that support redirection. The default status code is 403 but we can change it to e.g. 404. We can also add a custom response body. The next step is the rule. We can select one or more predefined rule sets and then customize at will. To customize, expand the rule set and select a rule. You can enable / disable the rule and you can change the action to Allow, Block, Lod or Redirect. WAF Custom Rule The next step is the custom rules. There’s a lot to customise here. First are the rule type settings. Select status of the rule, enabled or disabled. Select the Rule type between Match and Rate limit. If you select rate limit you will be prompt to set rate limit and threshold. The final rule tupe setting is to set the priority of the rule. Next is the Conditions (If this) and the action (then that). The condition can be Geolocation, IP address, Size or String. After selecting the Match Type the rest options are altered accordingly. The action can be Allow traffic, Deny traffic, Log traffic only or Redirect traffic For the demo I created a rule that will Deny all traffic from The Netherlands, because I can test it from an Azure VM located at the West Europe Region. The next step is to associate the rule to the Front Door. After that assign Tags if needed and create the rule. Once the Rule is ready, a “Front Door WAF policy” resource will be at the selected Resource Group. Inside the Front Door, at the Web application firewall section, you can review the assigned rules. Test 1 From an Azure VM at West Europe Region, I tried to access the Front Door’s URL and we can see my custom 403 body text! Test 2 From my Computer I tested a typical SQL Injection attack from https://www.owasp.org/index.php/Testing_for_SQL_Injection_(OTG-INPVAL-005) . Again my custom 403 page! The post Use Web Application Firewall (WAF) Rules with the Front Door to protect your app appeared first on Apostolidis IT Corner.
  2. At the previous post we created an Azure Front Door to scale our web apps across Azure Regions and also publish them only through the Front Door’s URL. At this post we will create Web Application Firewall (WAF) rules, to protect our web apps. To add WAF functionality to the Front Door we need first to create WAF rules and then attach them to the Front Door Create the WAF Rule From the Azure Marketplace search for WAF and create a Web Application Firewall At the “Create a WAF policy” wizard select “Global WAF (Front Door) for policy, provide the subscription and resource group, give a name for the policy and select if you want it to be created enabled or disabled. At the next step select if the policy will prevent the action or just detect and report it. You can change this later too. You can provide a Redirect URL for rules that support redirection. The default status code is 403 but we can change it to e.g. 404. We can also add a custom response body. The next step is the rule. We can select one or more predefined rule sets and then customize at will. To customize, expand the rule set and select a rule. You can enable / disable the rule and you can change the action to Allow, Block, Lod or Redirect. WAF Custom Rule The next step is the custom rules. There’s a lot to customise here. First are the rule type settings. Select status of the rule, enabled or disabled. Select the Rule type between Match and Rate limit. If you select rate limit you will be prompt to set rate limit and threshold. The final rule tupe setting is to set the priority of the rule. Next is the Conditions (If this) and the action (then that). The condition can be Geolocation, IP address, Size or String. After selecting the Match Type the rest options are altered accordingly. The action can be Allow traffic, Deny traffic, Log traffic only or Redirect traffic For the demo I created a rule that will Deny all traffic from The Netherlands, because I can test it from an Azure VM located at the West Europe Region. The next step is to associate the rule to the Front Door. After that assign Tags if needed and create the rule. Once the Rule is ready, a “Front Door WAF policy” resource will be at the selected Resource Group. Inside the Front Door, at the Web application firewall section, you can review the assigned rules. Test 1 From an Azure VM at West Europe Region, I tried to access the Front Door’s URL and we can see my custom 403 body text! Test 2 From my Computer I tested a typical SQL Injection attack from https://www.owasp.org/index.php/Testing_for_SQL_Injection_(OTG-INPVAL-005) . Again my custom 403 page! The post Use Web Application Firewall (WAF) Rules with the Front Door to protect your app appeared first on Apostolidis IT Corner.
  3. At the previous post we created an Azure Front Door to scale our web apps across Azure Regions and also publish them only through the Front Door’s URL. At this post we will create Web Application Firewall (WAF) rules, to protect our web apps. To add WAF functionality to the Front Door we need first to create WAF rules and then attach them to the Front Door Create the WAF Rule From the Azure Marketplace search for WAF and create a Web Application Firewall At the “Create a WAF policy” wizard select “Global WAF (Front Door) for policy, provide the subscription and resource group, give a name for the policy and select if you want it to be created enabled or disabled. At the next step select if the policy will prevent the action or just detect and report it. You can change this later too. You can provide a Redirect URL for rules that support redirection. The default status code is 403 but we can change it to e.g. 404. We can also add a custom response body. The next step is the rule. We can select one or more predefined rule sets and then customize at will. To customize, expand the rule set and select a rule. You can enable / disable the rule and you can change the action to Allow, Block, Lod or Redirect. WAF Custom Rule The next step is the custom rules. There’s a lot to customise here. First are the rule type settings. Select status of the rule, enabled or disabled. Select the Rule type between Match and Rate limit. If you select rate limit you will be prompt to set rate limit and threshold. The final rule tupe setting is to set the priority of the rule. Next is the Conditions (If this) and the action (then that). The condition can be Geolocation, IP address, Size or String. After selecting the Match Type the rest options are altered accordingly. The action can be Allow traffic, Deny traffic, Log traffic only or Redirect traffic For the demo I created a rule that will Deny all traffic from The Netherlands, because I can test it from an Azure VM located at the West Europe Region. The next step is to associate the rule to the Front Door. After that assign Tags if needed and create the rule. Once the Rule is ready, a “Front Door WAF policy” resource will be at the selected Resource Group. Inside the Front Door, at the Web application firewall section, you can review the assigned rules. Test 1 From an Azure VM at West Europe Region, I tried to access the Front Door’s URL and we can see my custom 403 body text! Test 2 From my Computer I tested a typical SQL Injection attack from https://www.owasp.org/index.php/Testing_for_SQL_Injection_(OTG-INPVAL-005) . Again my custom 403 page! The post Use Web Application Firewall (WAF) Rules with the Front Door to protect your app appeared first on Apostolidis IT Corner.
  4. Securely scale your Web Apps with Azure Front Door There is a big buzz out there about Azure Front Door. Is it a Load Balancer? A CDN? A Traffic Manager? A Web Application Firewall ? A Reverse Proxy? An Application Gateway? So, what is Azure Front Door? Azure Front Door actually is all the above and more. It is a global service, that routes web traffic based on performance and availability. A Layer 7 multi-region load balancer with Web Application Firewall (WAF) capabilities, DDoS protection & CDN. Azure Front Door is the entry point, the edge, of all Microsoft’s WAN. All Microsoft services, like Office 365 & Bing, are using Azure Front Door. The services that Azure Front door provides are: Accelerate application performance Increase application availability with smart health probes URL-based routing Multi-site hosting URL redirection Session affinity SSL termination Custom Domain & certificate management Security via custom WAF rules DDoS protection URL rewrite IPv6 and HTTP/2 support At Azure Front Door documentation there is a paragraph that can help to understand the difference between Azure Front Door and other publishing / load balancing Azure solutions and where to use each. Azure provides a suite of fully managed load-balancing solutions for your scenarios. If you are looking for a DNS based global routing and do not have requirements for Transport Layer Security (TLS) protocol termination (“SSL offload”) or per-HTTP/HTTPS request, application-layer processing, review Traffic Manager. If you are looking for load balancing between your servers in a region, for application layer, review Application Gateway and for network layer load balancing, review Load Balancer. Your end-to-end scenarios might benefit from combining these solutions as needed. For pricing information, see Front Door Pricing. How to scale your web apps with Front Door Create two simple Azure Web apps. Check this guide for a simple guide on how to create Azure App Service: https://www.e-apostolidis.gr/microsoft/azure/azure-start-point-your-first-web-app/ One at West Europe: and one at North Europe: Using FTP, I deployed an one-page html site at both regions. I change the text of both site to say “This Web Site is located at North Europe Azure Datacenter” and “West Europe” to the other. Then create a Front Door. Search for Front Door at Azure marketplace and Create one. This is a high level diagram of the Front Door with two Web Apps design that we will create The “create a Front Door” wizard will start and we can configure it step by step. First we will create a Frontend host by clicking the + at the Step 1 At the frontend host we will create the URL that our apps will be available. I added the papostolidis.azurefd.net. of course later you can add your custom domain and add a CNAME to route the traffic to the Front Door. Then, at the Backend pools (Step 2), press the + to add the web apps. add a name for the backend pool, like “myapps” and press + ADD a backend to add the apps. Select host type, you can add app service, cloud service, storage and custom host (URL). I selected the app service. Select the subscription and the app service and add the correct ports for http and https traffic. The priority defines if the traffic will be routed to the host with the lower priority number (e.g. 1) and if that host fails will route to the next host with bigger priority number (e.g. 2). If you add the same priority to more than one host then it will follow the weight number. The weight number defines the percentage of requests that will be routed to each host. The same way add the second web app Finally select a path, protocol and interval for the probe that will do health checks to the app to define if it is active or not. The third step is to add the routing rules. At the routing rules you can specify: The accepted protocol, http or https. the frontend host for this rule the patterns that the route will accept, like www.e-apostolidis.gr/mysite/* or just /* ro root. Route type forward or redirect. The backend pool that this rule will direct the traffic The protocol that the traffic will be forwarded. Here we define the SSL Offload if we select HTTPs for frontend accepted protocol and HTTP for backend. URL Rewrite rules Caching, for static content caching like CDN. Once all steps are completed we can move on and create the Front Door When the Front Door is ready, we can see the URL at the Overview. And browse our web app using the Front Door URL: How to protect your web apps with Front Door Right now we scaled our web apps. If we use each app’s URL we can still access the app. The first security step is to lock the web apps to be accessed only through the Front Door URL. Checking the Azure Front Door FAQ page, https://docs.microsoft.com/en-us/azure/frontdoor/front-door-faq it lists the Front Door’s address rance. Front Door’s IPv4 backend IP space: 147.243.0.0/16 Go to the App Service, at the Networking section, select “Configure Access Restrictions” Add an allow access restriction with the IP range of the Front Door. Automatically a Deny rule will be created for everything else. Add the rule to both web apps and then try to access the apps with their direct links. Now on, we can access the apps only by using the Front Door URL: This is a high level diagram after the restrictions At the next article, we will see how to add Web Application Firewall (WAF) Rules to Front Door, Stay Tuned!! The post Securely scale your Web Apps with Azure Front Door appeared first on Apostolidis IT Corner.
  5. Securely scale your Web Apps with Azure Front Door There is a big buzz out there about Azure Front Door. Is it a Load Balancer? A CDN? A Traffic Manager? A Web Application Firewall ? A Reverse Proxy? An Application Gateway? So, what is Azure Front Door? Azure Front Door actually is all the above and more. It is a global service, that routes web traffic based on performance and availability. A Layer 7 multi-region load balancer with Web Application Firewall (WAF) capabilities, DDoS protection & CDN. Azure Front Door is the entry point, the edge, of all Microsoft’s WAN. All Microsoft services, like Office 365 & Bing, are using Azure Front Door. The services that Azure Front door provides are: Accelerate application performance Increase application availability with smart health probes URL-based routing Multi-site hosting URL redirection Session affinity SSL termination Custom Domain & certificate management Security via custom WAF rules DDoS protection URL rewrite IPv6 and HTTP/2 support At Azure Front Door documentation there is a paragraph that can help to understand the difference between Azure Front Door and other publishing / load balancing Azure solutions and where to use each. Azure provides a suite of fully managed load-balancing solutions for your scenarios. If you are looking for a DNS based global routing and do not have requirements for Transport Layer Security (TLS) protocol termination (“SSL offload”) or per-HTTP/HTTPS request, application-layer processing, review Traffic Manager. If you are looking for load balancing between your servers in a region, for application layer, review Application Gateway and for network layer load balancing, review Load Balancer. Your end-to-end scenarios might benefit from combining these solutions as needed. For pricing information, see Front Door Pricing. How to scale your web apps with Front Door Create two simple Azure Web apps. Check this guide for a simple guide on how to create Azure App Service: https://www.e-apostolidis.gr/microsoft/azure/azure-start-point-your-first-web-app/ One at West Europe: and one at North Europe: Using FTP, I deployed an one-page html site at both regions. I change the text of both site to say “This Web Site is located at North Europe Azure Datacenter” and “West Europe” to the other. Then create a Front Door. Search for Front Door at Azure marketplace and Create one. This is a high level diagram of the Front Door with two Web Apps design that we will create The “create a Front Door” wizard will start and we can configure it step by step. First we will create a Frontend host by clicking the + at the Step 1 At the frontend host we will create the URL that our apps will be available. I added the papostolidis.azurefd.net. of course later you can add your custom domain and add a CNAME to route the traffic to the Front Door. Then, at the Backend pools (Step 2), press the + to add the web apps. add a name for the backend pool, like “myapps” and press + ADD a backend to add the apps. Select host type, you can add app service, cloud service, storage and custom host (URL). I selected the app service. Select the subscription and the app service and add the correct ports for http and https traffic. The priority defines if the traffic will be routed to the host with the lower priority number (e.g. 1) and if that host fails will route to the next host with bigger priority number (e.g. 2). If you add the same priority to more than one host then it will follow the weight number. The weight number defines the percentage of requests that will be routed to each host. The same way add the second web app Finally select a path, protocol and interval for the probe that will do health checks to the app to define if it is active or not. The third step is to add the routing rules. At the routing rules you can specify: The accepted protocol, http or https. the frontend host for this rule the patterns that the route will accept, like www.e-apostolidis.gr/mysite/* or just /* ro root. Route type forward or redirect. The backend pool that this rule will direct the traffic The protocol that the traffic will be forwarded. Here we define the SSL Offload if we select HTTPs for frontend accepted protocol and HTTP for backend. URL Rewrite rules Caching, for static content caching like CDN. Once all steps are completed we can move on and create the Front Door When the Front Door is ready, we can see the URL at the Overview. And browse our web app using the Front Door URL: How to protect your web apps with Front Door Right now we scaled our web apps. If we use each app’s URL we can still access the app. The first security step is to lock the web apps to be accessed only through the Front Door URL. Checking the Azure Front Door FAQ page, https://docs.microsoft.com/en-us/azure/frontdoor/front-door-faq it lists the Front Door’s address rance. Front Door’s IPv4 backend IP space: 147.243.0.0/16 Go to the App Service, at the Networking section, select “Configure Access Restrictions” Add an allow access restriction with the IP range of the Front Door. Automatically a Deny rule will be created for everything else. Add the rule to both web apps and then try to access the apps with their direct links. Now on, we can access the apps only by using the Front Door URL: This is a high level diagram after the restrictions At the next article, we will see how to add Web Application Firewall (WAF) Rules to Front Door, Stay Tuned!! The post Securely scale your Web Apps with Azure Front Door appeared first on Apostolidis IT Corner.
  6. Securely scale your Web Apps with Azure Front Door There is a big buzz out there about Azure Front Door. Is it a Load Balancer? A CDN? A Traffic Manager? A Web Application Firewall ? A Reverse Proxy? An Application Gateway? So, what is Azure Front Door? Azure Front Door actually is all the above and more. It is a global service, that routes web traffic based on performance and availability. A Layer 7 multi-region load balancer with Web Application Firewall (WAF) capabilities, DDoS protection & CDN. Azure Front Door is the entry point, the edge, of all Microsoft’s WAN. All Microsoft services, like Office 365 & Bing, are using Azure Front Door. The services that Azure Front door provides are: Accelerate application performance Increase application availability with smart health probes URL-based routing Multi-site hosting URL redirection Session affinity SSL termination Custom Domain & certificate management Security via custom WAF rules DDoS protection URL rewrite IPv6 and HTTP/2 support At Azure Front Door documentation there is a paragraph that can help to understand the difference between Azure Front Door and other publishing / load balancing Azure solutions and where to use each. Azure provides a suite of fully managed load-balancing solutions for your scenarios. If you are looking for a DNS based global routing and do not have requirements for Transport Layer Security (TLS) protocol termination (“SSL offload”) or per-HTTP/HTTPS request, application-layer processing, review Traffic Manager. If you are looking for load balancing between your servers in a region, for application layer, review Application Gateway and for network layer load balancing, review Load Balancer. Your end-to-end scenarios might benefit from combining these solutions as needed. For pricing information, see Front Door Pricing. How to scale your web apps with Front Door Create two simple Azure Web apps. Check this guide for a simple guide on how to create Azure App Service: https://www.e-apostolidis.gr/microsoft/azure/azure-start-point-your-first-web-app/ One at West Europe: and one at North Europe: Using FTP, I deployed an one-page html site at both regions. I change the text of both site to say “This Web Site is located at North Europe Azure Datacenter” and “West Europe” to the other. Then create a Front Door. Search for Front Door at Azure marketplace and Create one. This is a high level diagram of the Front Door with two Web Apps design that we will create The “create a Front Door” wizard will start and we can configure it step by step. First we will create a Frontend host by clicking the + at the Step 1 At the frontend host we will create the URL that our apps will be available. I added the papostolidis.azurefd.net. of course later you can add your custom domain and add a CNAME to route the traffic to the Front Door. Then, at the Backend pools (Step 2), press the + to add the web apps. add a name for the backend pool, like “myapps” and press + ADD a backend to add the apps. Select host type, you can add app service, cloud service, storage and custom host (URL). I selected the app service. Select the subscription and the app service and add the correct ports for http and https traffic. The priority defines if the traffic will be routed to the host with the lower priority number (e.g. 1) and if that host fails will route to the next host with bigger priority number (e.g. 2). If you add the same priority to more than one host then it will follow the weight number. The weight number defines the percentage of requests that will be routed to each host. The same way add the second web app Finally select a path, protocol and interval for the probe that will do health checks to the app to define if it is active or not. The third step is to add the routing rules. At the routing rules you can specify: The accepted protocol, http or https. the frontend host for this rule the patterns that the route will accept, like www.e-apostolidis.gr/mysite/* or just /* ro root. Route type forward or redirect. The backend pool that this rule will direct the traffic The protocol that the traffic will be forwarded. Here we define the SSL Offload if we select HTTPs for frontend accepted protocol and HTTP for backend. URL Rewrite rules Caching, for static content caching like CDN. Once all steps are completed we can move on and create the Front Door When the Front Door is ready, we can see the URL at the Overview. And browse our web app using the Front Door URL: How to protect your web apps with Front Door Right now we scaled our web apps. If we use each app’s URL we can still access the app. The first security step is to lock the web apps to be accessed only through the Front Door URL. Checking the Azure Front Door FAQ page, https://docs.microsoft.com/en-us/azure/frontdoor/front-door-faq it lists the Front Door’s address rance. Front Door’s IPv4 backend IP space: 147.243.0.0/16 Go to the App Service, at the Networking section, select “Configure Access Restrictions” Add an allow access restriction with the IP range of the Front Door. Automatically a Deny rule will be created for everything else. Add the rule to both web apps and then try to access the apps with their direct links. Now on, we can access the apps only by using the Front Door URL: This is a high level diagram after the restrictions At the next article, we will see how to add Web Application Firewall (WAF) Rules to Front Door, Stay Tuned!! The post Securely scale your Web Apps with Azure Front Door appeared first on Apostolidis IT Corner.
  7. Securely scale your Web Apps with Azure Front Door There is a big buzz out there about Azure Front Door. Is it a Load Balancer? A CDN? A Traffic Manager? A Web Application Firewall ? A Reverse Proxy? An Application Gateway? So, what is Azure Front Door? Azure Front Door actually is all the above and more. It is a global service, that routes web traffic based on performance and availability. A Layer 7 multi-region load balancer with Web Application Firewall (WAF) capabilities, DDoS protection & CDN. Azure Front Door is the entry point, the edge, of all Microsoft’s WAN. All Microsoft services, like Office 365 & Bing, are using Azure Front Door. The services that Azure Front door provides are: Accelerate application performance Increase application availability with smart health probes URL-based routing Multi-site hosting URL redirection Session affinity SSL termination Custom Domain & certificate management Security via custom WAF rules DDoS protection URL rewrite IPv6 and HTTP/2 support At Azure Front Door documentation there is a paragraph that can help to understand the difference between Azure Front Door and other publishing / load balancing Azure solutions and where to use each. Azure provides a suite of fully managed load-balancing solutions for your scenarios. If you are looking for a DNS based global routing and do not have requirements for Transport Layer Security (TLS) protocol termination (“SSL offload”) or per-HTTP/HTTPS request, application-layer processing, review Traffic Manager. If you are looking for load balancing between your servers in a region, for application layer, review Application Gateway and for network layer load balancing, review Load Balancer. Your end-to-end scenarios might benefit from combining these solutions as needed. For pricing information, see Front Door Pricing. How to scale your web apps with Front Door Create two simple Azure Web apps. Check this guide for a simple guide on how to create Azure App Service: https://www.e-apostolidis.gr/microsoft/azure/azure-start-point-your-first-web-app/ One at West Europe: and one at North Europe: Using FTP, I deployed an one-page html site at both regions. I change the text of both site to say “This Web Site is located at North Europe Azure Datacenter” and “West Europe” to the other. Then create a Front Door. Search for Front Door at Azure marketplace and Create one. This is a high level diagram of the Front Door with two Web Apps design that we will create The “create a Front Door” wizard will start and we can configure it step by step. First we will create a Frontend host by clicking the + at the Step 1 At the frontend host we will create the URL that our apps will be available. I added the papostolidis.azurefd.net. of course later you can add your custom domain and add a CNAME to route the traffic to the Front Door. Then, at the Backend pools (Step 2), press the + to add the web apps. add a name for the backend pool, like “myapps” and press + ADD a backend to add the apps. Select host type, you can add app service, cloud service, storage and custom host (URL). I selected the app service. Select the subscription and the app service and add the correct ports for http and https traffic. The priority defines if the traffic will be routed to the host with the lower priority number (e.g. 1) and if that host fails will route to the next host with bigger priority number (e.g. 2). If you add the same priority to more than one host then it will follow the weight number. The weight number defines the percentage of requests that will be routed to each host. The same way add the second web app Finally select a path, protocol and interval for the probe that will do health checks to the app to define if it is active or not. The third step is to add the routing rules. At the routing rules you can specify: The accepted protocol, http or https. the frontend host for this rule the patterns that the route will accept, like www.e-apostolidis.gr/mysite/* or just /* ro root. Route type forward or redirect. The backend pool that this rule will direct the traffic The protocol that the traffic will be forwarded. Here we define the SSL Offload if we select HTTPs for frontend accepted protocol and HTTP for backend. URL Rewrite rules Caching, for static content caching like CDN. Once all steps are completed we can move on and create the Front Door When the Front Door is ready, we can see the URL at the Overview. And browse our web app using the Front Door URL: How to protect your web apps with Front Door Right now we scaled our web apps. If we use each app’s URL we can still access the app. The first security step is to lock the web apps to be accessed only through the Front Door URL. Checking the Azure Front Door FAQ page, https://docs.microsoft.com/en-us/azure/frontdoor/front-door-faq it lists the Front Door’s address rance. Front Door’s IPv4 backend IP space: 147.243.0.0/16 Go to the App Service, at the Networking section, select “Configure Access Restrictions” Add an allow access restriction with the IP range of the Front Door. Automatically a Deny rule will be created for everything else. Add the rule to both web apps and then try to access the apps with their direct links. Now on, we can access the apps only by using the Front Door URL: This is a high level diagram after the restrictions At the next article, we will see how to add Web Application Firewall (WAF) Rules to Front Door, Stay Tuned!! The post Securely scale your Web Apps with Azure Front Door appeared first on Apostolidis IT Corner.
  8. Securely scale your Web Apps with Azure Front Door There is a big buzz out there about Azure Front Door. Is it a Load Balancer? A CDN? A Traffic Manager? A Web Application Firewall ? A Reverse Proxy? An Application Gateway? So, what is Azure Front Door? Azure Front Door actually is all the above and more. It is a global service, that routes web traffic based on performance and availability. A Layer 7 multi-region load balancer with Web Application Firewall (WAF) capabilities, DDoS protection & CDN. Azure Front Door is the entry point, the edge, of all Microsoft’s WAN. All Microsoft services, like Office 365 & Bing, are using Azure Front Door. The services that Azure Front door provides are: Accelerate application performance Increase application availability with smart health probes URL-based routing Multi-site hosting URL redirection Session affinity SSL termination Custom Domain & certificate management Security via custom WAF rules DDoS protection URL rewrite IPv6 and HTTP/2 support At Azure Front Door documentation there is a paragraph that can help to understand the difference between Azure Front Door and other publishing / load balancing Azure solutions and where to use each. Azure provides a suite of fully managed load-balancing solutions for your scenarios. If you are looking for a DNS based global routing and do not have requirements for Transport Layer Security (TLS) protocol termination (“SSL offload”) or per-HTTP/HTTPS request, application-layer processing, review Traffic Manager. If you are looking for load balancing between your servers in a region, for application layer, review Application Gateway and for network layer load balancing, review Load Balancer. Your end-to-end scenarios might benefit from combining these solutions as needed. For pricing information, see Front Door Pricing. How to scale your web apps with Front Door Create two simple Azure Web apps. Check this guide for a simple guide on how to create Azure App Service: https://www.e-apostolidis.gr/microsoft/azure/azure-start-point-your-first-web-app/ One at West Europe: and one at North Europe: Using FTP, I deployed an one-page html site at both regions. I change the text of both site to say “This Web Site is located at North Europe Azure Datacenter” and “West Europe” to the other. Then create a Front Door. Search for Front Door at Azure marketplace and Create one. This is a high level diagram of the Front Door with two Web Apps design that we will create The “create a Front Door” wizard will start and we can configure it step by step. First we will create a Frontend host by clicking the + at the Step 1 At the frontend host we will create the URL that our apps will be available. I added the papostolidis.azurefd.net. of course later you can add your custom domain and add a CNAME to route the traffic to the Front Door. Then, at the Backend pools (Step 2), press the + to add the web apps. add a name for the backend pool, like “myapps” and press + ADD a backend to add the apps. Select host type, you can add app service, cloud service, storage and custom host (URL). I selected the app service. Select the subscription and the app service and add the correct ports for http and https traffic. The priority defines if the traffic will be routed to the host with the lower priority number (e.g. 1) and if that host fails will route to the next host with bigger priority number (e.g. 2). If you add the same priority to more than one host then it will follow the weight number. The weight number defines the percentage of requests that will be routed to each host. The same way add the second web app Finally select a path, protocol and interval for the probe that will do health checks to the app to define if it is active or not. The third step is to add the routing rules. At the routing rules you can specify: The accepted protocol, http or https. the frontend host for this rule the patterns that the route will accept, like www.e-apostolidis.gr/mysite/* or just /* ro root. Route type forward or redirect. The backend pool that this rule will direct the traffic The protocol that the traffic will be forwarded. Here we define the SSL Offload if we select HTTPs for frontend accepted protocol and HTTP for backend. URL Rewrite rules Caching, for static content caching like CDN. Once all steps are completed we can move on and create the Front Door When the Front Door is ready, we can see the URL at the Overview. And browse our web app using the Front Door URL: How to protect your web apps with Front Door Right now we scaled our web apps. If we use each app’s URL we can still access the app. The first security step is to lock the web apps to be accessed only through the Front Door URL. Checking the Azure Front Door FAQ page, https://docs.microsoft.com/en-us/azure/frontdoor/front-door-faq it lists the Front Door’s address rance. Front Door’s IPv4 backend IP space: 147.243.0.0/16 Go to the App Service, at the Networking section, select “Configure Access Restrictions” Add an allow access restriction with the IP range of the Front Door. Automatically a Deny rule will be created for everything else. Add the rule to both web apps and then try to access the apps with their direct links. Now on, we can access the apps only by using the Front Door URL: This is a high level diagram after the restrictions At the next article, we will see how to add Web Application Firewall (WAF) Rules to Front Door, Stay Tuned!! The post Securely scale your Web Apps with Azure Front Door appeared first on Apostolidis IT Corner.
  9. Securely scale your Web Apps with Azure Front Door There is a big buzz out there about Azure Front Door. Is it a Load Balancer? A CDN? A Traffic Manager? A Web Application Firewall ? A Reverse Proxy? An Application Gateway? So, what is Azure Front Door? Azure Front Door actually is all the above and more. It is a global service, that routes web traffic based on performance and availability. A Layer 7 multi-region load balancer with Web Application Firewall (WAF) capabilities, DDoS protection & CDN. Azure Front Door is the entry point, the edge, of all Microsoft’s WAN. All Microsoft services, like Office 365 & Bing, are using Azure Front Door. The services that Azure Front door provides are: Accelerate application performance Increase application availability with smart health probes URL-based routing Multi-site hosting URL redirection Session affinity SSL termination Custom Domain & certificate management Security via custom WAF rules DDoS protection URL rewrite IPv6 and HTTP/2 support At Azure Front Door documentation there is a paragraph that can help to understand the difference between Azure Front Door and other publishing / load balancing Azure solutions and where to use each. Azure provides a suite of fully managed load-balancing solutions for your scenarios. If you are looking for a DNS based global routing and do not have requirements for Transport Layer Security (TLS) protocol termination (“SSL offload”) or per-HTTP/HTTPS request, application-layer processing, review Traffic Manager. If you are looking for load balancing between your servers in a region, for application layer, review Application Gateway and for network layer load balancing, review Load Balancer. Your end-to-end scenarios might benefit from combining these solutions as needed. For pricing information, see Front Door Pricing. How to scale your web apps with Front Door Create two simple Azure Web apps. Check this guide for a simple guide on how to create Azure App Service: https://www.e-apostolidis.gr/microsoft/azure/azure-start-point-your-first-web-app/ One at West Europe: and one at North Europe: Using FTP, I deployed an one-page html site at both regions. I change the text of both site to say “This Web Site is located at North Europe Azure Datacenter” and “West Europe” to the other. Then create a Front Door. Search for Front Door at Azure marketplace and Create one. This is a high level diagram of the Front Door with two Web Apps design that we will create The “create a Front Door” wizard will start and we can configure it step by step. First we will create a Frontend host by clicking the + at the Step 1 At the frontend host we will create the URL that our apps will be available. I added the papostolidis.azurefd.net. of course later you can add your custom domain and add a CNAME to route the traffic to the Front Door. Then, at the Backend pools (Step 2), press the + to add the web apps. add a name for the backend pool, like “myapps” and press + ADD a backend to add the apps. Select host type, you can add app service, cloud service, storage and custom host (URL). I selected the app service. Select the subscription and the app service and add the correct ports for http and https traffic. The priority defines if the traffic will be routed to the host with the lower priority number (e.g. 1) and if that host fails will route to the next host with bigger priority number (e.g. 2). If you add the same priority to more than one host then it will follow the weight number. The weight number defines the percentage of requests that will be routed to each host. The same way add the second web app Finally select a path, protocol and interval for the probe that will do health checks to the app to define if it is active or not. The third step is to add the routing rules. At the routing rules you can specify: The accepted protocol, http or https. the frontend host for this rule the patterns that the route will accept, like www.e-apostolidis.gr/mysite/* or just /* ro root. Route type forward or redirect. The backend pool that this rule will direct the traffic The protocol that the traffic will be forwarded. Here we define the SSL Offload if we select HTTPs for frontend accepted protocol and HTTP for backend. URL Rewrite rules Caching, for static content caching like CDN. Once all steps are completed we can move on and create the Front Door When the Front Door is ready, we can see the URL at the Overview. And browse our web app using the Front Door URL: How to protect your web apps with Front Door Right now we scaled our web apps. If we use each app’s URL we can still access the app. The first security step is to lock the web apps to be accessed only through the Front Door URL. Checking the Azure Front Door FAQ page, https://docs.microsoft.com/en-us/azure/frontdoor/front-door-faq it lists the Front Door’s address rance. Front Door’s IPv4 backend IP space: 147.243.0.0/16 Go to the App Service, at the Networking section, select “Configure Access Restrictions” Add an allow access restriction with the IP range of the Front Door. Automatically a Deny rule will be created for everything else. Add the rule to both web apps and then try to access the apps with their direct links. Now on, we can access the apps only by using the Front Door URL: This is a high level diagram after the restrictions At the next article, we will see how to add Web Application Firewall (WAF) Rules to Front Door, Stay Tuned!! The post Securely scale your Web Apps with Azure Front Door appeared first on Apostolidis IT Corner.
  10. Securely scale your Web Apps with Azure Front Door There is a big buzz out there about Azure Front Door. Is it a Load Balancer? A CDN? A Traffic Manager? A Web Application Firewall ? A Reverse Proxy? An Application Gateway? So, what is Azure Front Door? Azure Front Door actually is all the above and more. It is a global service, that routes web traffic based on performance and availability. A Layer 7 multi-region load balancer with Web Application Firewall (WAF) capabilities, DDoS protection & CDN. Azure Front Door is the entry point, the edge, of all Microsoft’s WAN. All Microsoft services, like Office 365 & Bing, are using Azure Front Door. The services that Azure Front door provides are: Accelerate application performance Increase application availability with smart health probes URL-based routing Multi-site hosting URL redirection Session affinity SSL termination Custom Domain & certificate management Security via custom WAF rules DDoS protection URL rewrite IPv6 and HTTP/2 support At Azure Front Door documentation there is a paragraph that can help to understand the difference between Azure Front Door and other publishing / load balancing Azure solutions and where to use each. Azure provides a suite of fully managed load-balancing solutions for your scenarios. If you are looking for a DNS based global routing and do not have requirements for Transport Layer Security (TLS) protocol termination (“SSL offload”) or per-HTTP/HTTPS request, application-layer processing, review Traffic Manager. If you are looking for load balancing between your servers in a region, for application layer, review Application Gateway and for network layer load balancing, review Load Balancer. Your end-to-end scenarios might benefit from combining these solutions as needed. For pricing information, see Front Door Pricing. How to scale your web apps with Front Door Create two simple Azure Web apps. Check this guide for a simple guide on how to create Azure App Service: https://www.e-apostolidis.gr/microsoft/azure/azure-start-point-your-first-web-app/ One at West Europe: and one at North Europe: Using FTP, I deployed an one-page html site at both regions. I change the text of both site to say “This Web Site is located at North Europe Azure Datacenter” and “West Europe” to the other. Then create a Front Door. Search for Front Door at Azure marketplace and Create one. This is a high level diagram of the Front Door with two Web Apps design that we will create The “create a Front Door” wizard will start and we can configure it step by step. First we will create a Frontend host by clicking the + at the Step 1 At the frontend host we will create the URL that our apps will be available. I added the papostolidis.azurefd.net. of course later you can add your custom domain and add a CNAME to route the traffic to the Front Door. Then, at the Backend pools (Step 2), press the + to add the web apps. add a name for the backend pool, like “myapps” and press + ADD a backend to add the apps. Select host type, you can add app service, cloud service, storage and custom host (URL). I selected the app service. Select the subscription and the app service and add the correct ports for http and https traffic. The priority defines if the traffic will be routed to the host with the lower priority number (e.g. 1) and if that host fails will route to the next host with bigger priority number (e.g. 2). If you add the same priority to more than one host then it will follow the weight number. The weight number defines the percentage of requests that will be routed to each host. The same way add the second web app Finally select a path, protocol and interval for the probe that will do health checks to the app to define if it is active or not. The third step is to add the routing rules. At the routing rules you can specify: The accepted protocol, http or https. the frontend host for this rule the patterns that the route will accept, like www.e-apostolidis.gr/mysite/* or just /* ro root. Route type forward or redirect. The backend pool that this rule will direct the traffic The protocol that the traffic will be forwarded. Here we define the SSL Offload if we select HTTPs for frontend accepted protocol and HTTP for backend. URL Rewrite rules Caching, for static content caching like CDN. Once all steps are completed we can move on and create the Front Door When the Front Door is ready, we can see the URL at the Overview. And browse our web app using the Front Door URL: How to protect your web apps with Front Door Right now we scaled our web apps. If we use each app’s URL we can still access the app. The first security step is to lock the web apps to be accessed only through the Front Door URL. Checking the Azure Front Door FAQ page, https://docs.microsoft.com/en-us/azure/frontdoor/front-door-faq it lists the Front Door’s address rance. Front Door’s IPv4 backend IP space: 147.243.0.0/16 Go to the App Service, at the Networking section, select “Configure Access Restrictions” Add an allow access restriction with the IP range of the Front Door. Automatically a Deny rule will be created for everything else. Add the rule to both web apps and then try to access the apps with their direct links. Now on, we can access the apps only by using the Front Door URL: This is a high level diagram after the restrictions At the next article, we will see how to add Web Application Firewall (WAF) Rules to Front Door, Stay Tuned!! The post Securely scale your Web Apps with Azure Front Door appeared first on Apostolidis IT Corner.
  11. Καλημέρα σε όλους, ενδιαφερόμαστε για την αποθήκευση των αρχείων backup της εταιρίας εκτός κτιρίου και απο ότι βλέπω γενικά, το storage πάει cloud οπότε λέμε μήπως μεταβούμε στο Azure. Ψάχνοντας τα διάφορα είδη Storage που δίνει, ποιό λέτε πως ταιριάζει στο δικό μας σενάριο? Μιλάμε για 7-10ΤΒ δεδομένων στο Azure. Τα αρχεία θα ανανεώνονται κάθε 2 μήνες και είναι σε μορφή .TIB (Acronis Advanced Backup 12.5) βλέπω πως υπάρχουν τα εξής : File Storage Blob Storage (μάλλον αυτό θα πρέπει να κοιτάξω) Archive Storage Queue Storage Disk Storage Data Box Azure Backup Azure Data Lake Storage Εγώ ενδιαφέρομαι απλά να μπορώ να ανεβάζω αυτά τα αρχεία 2 φορές το μήνα πάνω στο Cloud.. YΓ : Με το Veeam, μπορώ να παίρνω backup κάποιων shared folders? Σας ευχαριστώ πολύ.
  12. To event που όλοι περιμέναμε, το Athens Azure Bootcamp 2019, που φέτος λόγω Πάσχα δεν ακολούθησε την ημερομηνία διεξαγωγής του παγκόσμιου event, θα πραγματοποιηθεί στο Gazarte, το Σάββατο 11 Μαίου 2019. Δηλώστε συμμετοχή στον παρακάτω σύνδεσμο: Register to Athens Azure Bootcamp 2019 και ελάτε να γνωριστούμε και να συζητήσουμε από κοντά, τις τεχνολογίες, τα προβλήματα, αλλά και τις λύσεις στα θέματα που μας απασχολούν καθημερινά. Το event στηρίζουν οι κοινότητες πληροφορικής azureheads.gr, autoexec.gr και sqlschool.gr, ενώ θα περιλαμβάνει, περισσότερους από 12 ομιλητές σε 2 παράλληλα Sessions. Περισσότερες λεπτομέρειες σχετικά με τις ομιλίες καθώς και το πρόγραμμα, θα βρείτε στην σελίδα του event, στο: Athens Azure Bootcamp 2019 Κάντε την εγγραφή σας σήμερα, για να μην χάσετε μία ημέρα γεμάτη Azure!
  13. Μια μέρα αφιερωμένη στο Cloud και το Microsoft Azure! Περισσότεροι από 16 ομιλητές, 3 παράλληλα sessions κι οι μεγαλύτερες κοινότητες πληροφορικής azureheads.gr, autoexec.gr, sqlschool.gr, dotnetzone.gr, συναντώνται στον πολυχώρο της Τεχνόπολις στο Γκάζι για μια μέρα γεμάτη Azure! Περισσότερες πληροφορίες θα βρείτε στην σελίδα του event athens.azurebootcamp.net! Δηλώστε συμμετοχή χρησιμοποιώντας τον παρακάτω σύνδεσμο https://www.eventbrite.com/e/global-azure-bootcamp-2018-athens-tickets-44480452230 κι ελάτε να γνωριστούμε και να συζητήσουμε από κοντά τεχνολογίες, προβλήματα και λύσεις σε θέματα που αντιμετωπίζουμε.
  14. ThinkRIT, is an information technology Services and Solutions Provider, operating in Automotive & Retail industry. With extensive knowledge and experience in the market, the company offers a comprehensive suite of services to their customers in the areas of Consulting, Implementation, Support and Training. Develops cloud applications & smart solutions and always having as a principle to fulfill upcoming market and customer needs. We have an immediate opening for Software Developers in our Athens office to join the Development team. Responsibilities · Work with a team to design, develop, test, and maintain web based business applications · Design, develop and test software in accordance to the established standards · Participate in peer-reviews of solution designs and related code · Work with teammates to analyze and resolve software problems · Adhere to high quality development principles while delivering solutions on time and on budget · Provide third level support to business users Minimum requirements · Strong work ethics, drive and enthusiasm to deliver high quality products and ability to work under pressure · Understanding of software life cycle · Understanding of business processes and requirements and strong desire to learn · Computer Science degree or equivalent training · 2-3 years practical software development experience · Verbal and written communication skills in the English language Preferred competency requirements · Hands on experience with C#, Java or JS · SOA, Cloud services · PaaS, SaaS · Web & mobile applications · RDBMS, MS SQL Server · Microsoft Dynamics · Microsoft Azure We Offer · An excellent work environment · Training and development opportunities in a rapidly growing company · This is a full-time position. Qualified candidates should send their CV to hr@thinkrit.gr
  15. Global Azure Bootcamp 2017 – Athens Απρίλιος 22 @ 09:00 - 18:30 Αγαπητοί φίλοι, Τον Απρίλιο του 2013 πραγματοποιήθηκε το πρώτο Global Azure Bootcamp σε περισσότερες από 90 περιοχές ανά τον κόσμο. Αυτός ο αριθμός ολοένα και αυξανόταν, για να φτάσει τις 136 περιοχές το 2014, τις 182 το 2015 και 187 το 2016! Στην Ελλάδα διοργανώθηκε για πρώτη φορά το 2014 με μαζική συμμετοχή, η οποία αναμένεται να φτάσει σε… επίπεδα ρεκόρ φέτος, την τέταρτη συνεχή χρονιά διοργάνωσής του. Η κοινότητα των επαγγελματιών πληροφορικής που ασχολούνται με Cloud τεχνολογίες www.azureheads.gr, σε συνεργασία με το autoexec.gr, sqlschool.gr και dotnetzone.gr, βρίσκονται στην ευχάριστη θέση να σας προσφέρουν και φέτος μια εις βάθος παρουσίαση της πλατφόρμας Cloud Computing της Microsoft, Microsoft Azure. Εκτός από τις παρουσιάσεις που θα έχετε την ευκαιρία να παρακολουθήσετε, θα μπορέσετε να αποκτήσετε και τη σχετική κατάρτιση συμμετέχοντας στο lab που θα δημιουργηθεί, προκειμένου να υλοποιηθεί μια παγκόσμια υπολογιστική φάρμα (computation farm) για φιλανθρωπικό σκοπό. Για περισσότερες πληροφορίες, επικεφτείτε την σελίδα μας athens.azurebootcamp.net και δηλώστε συμμετοχή RSVP Τι θα χρειαστείτε Αν αποφασίσετε να συμμετάσχετε στο lab θα χρειαστείτε: Έναν υπολογιστή που να μπορεί να τρέξει Visual Studio 2015 ή 2017 Visual Studio 2015 ή 2017 Το Windows Azure SDK από εδώ https://azure.microsoft.com/en-us/downloads/ Εκτός από τα παραπάνω θα χρειαστείτε μια ενεργή Windows Azure συνδρομή! Υπάρχουν αρκετοί τρόποι για να την αποκτήσετε εάν δεν έχετε ήδη: Ξεκινήστε ένα FREE trial at https://azure.microsoft.com/en-us/free/ ΣΗΜΕΙΩΣΗ: η συνδρομή αυτή είναι ενεργή μόνο για 1 μήνα, οπότε καλό θα ήταν να την ενεργοποιήσετε λιγότερο από ένα μήνα πριν από τις 22 Απριλίου. MSDN benefit! Αν είστε κάτοχος συνδρομής MSDN, BizSpark ή DreamSpark μπορείτε να ενεργοποιήσετε δωρεάν τη Microsoft Azure συνδρομή σας από εδώ msdn.microsoft.com. Αν ωστόσο δεν σας κάνουν τα παραπάνω, μπορείτε απλά να ενεργοποιήσετε μια συνδρομή με χρήση πιστωτικής κάρτας από εδώ azure.microsoft.com. Συχνές Ερωτήσεις Πώς θα έρθω και πού θα παρκάρω; Ελάτε με τον ηλεκτρικό (Πράσινη Γραμμή) μέχρι το ΚΑΤ και μετά με τα πόδια ή με λεωφορείο. Υπάρχει χώρος πάρκινγκ αν έρθετε με αυτοκίνητο.Χρειάζεται προεγγραφή; Ναι, δηλώστε συμμετοχή RSVP.Πόσο κοστίζει η είσοδος; Είναι δωρεάν!Σημείωση Λόγω της αυξημένης ασφάλειας που υπάρχει στο κτίριο, όσοι θελήσουν να παραβρεθούν θα πρέπει να δηλώσουν τη συμμετοχή τους στο σχετικό event στο Meetup. Η δήλωση συμμετοχής ενδείκνυται, καθότι θα δοθεί λίστα με τα ονοματεπώνυμα των συμμετεχόντων για την είσοδό τους στο κτίριο. Επίσης, για την είσοδο στο event, θα χρειαστεί να φέρετε μαζί σας ταυτότητα ή άλλο ισοδύναμο έγγραφο για να γίνει ταυτοποίηση. + ΗΜΕΡΟΛΟΓΙΟ GOOGLE + ΕΙΣΑΓΩΓΗ ICAL Λεπτομέρειες Ημερομηνία: Απρίλιος 22 Ώρα: 09:00 - 18:30 Κατηγορίες Εκδήλωση: autoexec.gr, azureheads.gr, dotNETZone.gr, Events, sqlSchool.gr Ετικέτες Εκδήλωση azure, gab, global azure bootcamp Ιστοσελίδα: http://athens.azurebootcamp.net Διοργανωτές azureheads.gr autoexec.gr dotNETZone.gr sqlschool.gr Χώρος Διεξαγωγής Microsoft Hellas Leof. Kifisias 221 Athens, Marousi 15124 Greece + Χάρτης Google Πηγή: http://www.azureheads.gr/event/global-azure-bootcamp-2017-athens/
  16. To AzureHeads Community διοργανώνει το πρώτο του meetup και μας προσκαλεί. Την πρόσκληση καθώς και τον σύνδεσμο για την απαραίτητη εγγραφή, θα τον βρείτε εδώ: http://www.azureheads.gr/event/webjobs-azure-functions-serverless-computing/
  17. Φίλες και φίλοι, Με μεγάλη χαρά ανακοινώνουμε το 1o Azure Bootcamp για IT Professionals, που θα γίνει στα γραφεία της Microsoft Hellas, το Σάββατο 23 Απριλίου 2016. Σε αυτό το event θα αναλύσουμε πως μπορείτε να εμπλουτίσετε τις δεξιότητες και τις γνώσεις σας, για να βοηθήσετε την επιχείρησής σας να επεκταθεί πέρα από τα όρια και τις δυνατότητες των On-Premises υποδομών. Θα δείξουμε Deep-Dive scenarios που χρησιμοποιούν υπηρεσίες Compute, Network & Storage του Azure Infrastructure as a Service, μέσω του νέου μοντέλου που ονομάζεται Azure Resource Manager. Θα παρουσιάσουμε ένα ολοκληρωμένο scenario μετάβασης μιάς ολόκληρης υποδομής στο DR Site, με απλό και αυτοματοποιημένο τρόπο, με την χρήση των υπηρεσιών Azure Recovery Services, ενώ θα απαντήσουμε στο ερώτημα τι σημαίνει Enterprise Mobility για εσάς, την επιχείρησή σας και τους χειριστές της. Κατά την διάρκεια του event, θα έχετε την ευκαιρία να συμμετάσχετε σε ολοκληρωμένα Hands-on-Labs ακολουθώντας τα αναλυτικά βήματα με τις οδηγίες που θα δοθούν στους συμμετέχοντες. Πρόγραμμα 10:00 – 10:15, Εγγραφές και Καφές 10:15 – 11:00, Azure Computing: Virtual Machines on Azure in the new resource model (ARM) 11:00 – 12:00, Azure Networking: VNETs: what can be done & how 12:00 – 12:15, Διάλειμμα με Καφέ 12:15 – 13:00, Azure Networking: Συνέχεια 13:00 – 13:30, Azure Storage: Details on the Storage, SSDs and StorSimple 13:30 – 14:00, Ελαφρύ Γεύμα 14:00 – 15:00, Business Continuity: Azure Backup & Azure Site Recovery 15:00 – 16:00, Azure Identity & Enterprise Mobility Suite 16:00 – 16:30, Διάλειμμα με Καφέ/Συζήτηση Ομιλητές: Παναγιώτης Κουρής Βαγγέλης Κάππας Οι θέσεις είναι περιορισμένες γι αυτό είναι απαραίτητη η εγγραφή σας μέσω του παρακάτω συνδέσμου. Εγγραφή
  18. Τα πράγματα είναι απλά... έχω μπερδευτεί! έχω σηκώσει στο Azure ένα Kali Linux στο οποίο συνδέομαι μία χαρά με SSH. Σε αυτό έχω βάλει VNC server και στο οποίο προσπαθώ να συνδεθώ. Προφανώς να έχω ρυθμίσει κάτι λάθος στο kali για τις ρυθμίσεις του VNC server τσεκάρω να δω ποια πόρτα χρησιμοποιεί by default (5900???) και αν κόβει τίποτα το azure σε αυτή την περίπτωση! βάζοντας στον VNC viewer την IP:5900 ή IP::5900 http://1drv.ms/1QgC5qp δοκίμασα να το κάνω και μέσω SSH tunelling, βάζοντας localhost:1 περιμένωντας κάποια ώρα πέρνω το παρακάτω μήνυμα! http://1drv.ms/1QgCo4x δώστε λίγο τα φώτα σας να δω τι έχω κάνει λάθος!
  19. Καλημέρα, θέλω να κάνω μια ερώτηση που με ταλαιπωρεί αρκετό καιρό με το Azure. έχω ανεβάσει ενα custom image απο το old platform (γιατί δεν το βρίσκω στη νεα platform) και απο εκει ξεκινάνε ολα μου τα προβλήματα. Ερωτήματα 1. Μπορεί να μεταφερθεί ενα VM απο ενα Virtual Network σε άλλο? απο την νεα πλατφορμα? 2. Μπορέι η νέα πλατφόρμα να φτιάξει μηχανή απο custom image η να έχει σαν δίσκο εναν ήδη υπάρχον? 3. Όταν φτιάχνεις μηχανή απο το παλαιό πλατφορμ πως μπορείς να επιλέξεις ποιο virtual network θα χρησημοποιει? ευχαριστώ, Παναγιώτης
  20. Επειδη πρεπει να λεμε τα πραγματα οπως ειναι, στο αρθρο του theregister αναφερει οτι το azure εχει μια κακη χρονια για το2014 σε σχεση παντα με τους μεγαλους παιχτες της αγορας στο κομματι της διαθεσιμοτητας. Αναλυτικοτερα το Azure ειχε 103 outages με συνολικο χρονο 43 ωρες, αντιστοιχα για google 86 μ 3,5 ωρες και τον μεγαλο αντιπαλο Amazon EC2 με το εντυπωσιακο των 12 outages και 2 ωρες. Αναλυτικα η διαθεσιμότητα ολων των cloud services. https://cloudharmony.com/status-1year-of-storage-and-compute-group-by-regions-and-provider NK
  21. Storage Performance like a boss! Διαθέσιμο στο Technet το White Paper του Storage performance για το Cloud Platform System! Μερικά νούμερα (w0000000tttttt!!!!!!!) Boot storm: ~1800 Azure A1-sized VMs* cold started within 150 seconds at a median start time of 20 seconds/VM VM microbenchmarks across 112 Azure A1-sized VMs: 1.01 million 4KiB random read IOPS at an average latency of 0.90 milliseconds (ms), with 44% of SSU (storage scale unit) connectivity utilized 321,000 mixed 4KiB (70:30) read/write IOPS at average latencies of 2.49ms read and 4.47ms write VM SQL Server database OLTP across 84 Azure A4-sized VMs sustained ~35,000 transactions/second (s) 222,000 total IOPS (182,000 read and 40,000 write) at an average 1.5ms read and 9.0ms write latency
  22. Διαθέσιμα για κατέβασμα 2 ΔΩΡΕΑΝ βιβλία για το Windows Azure καθώς και ένα νέο βίβλιο (επί πληρωμή) που καλύπτει την εξέταση 70-533 Implementing Microsoft Azure Infrastructure Solutions Microsoft Azure Essentials Fundamentals of Azure Microsoft Azure Essentials: Azure Automation Implementing Microsoft Azure Infrastructure Solutions
×
×
  • Create New...