Friday, 28 June 2024

Adapting to Change at Workplace

 


Put your adaptability skills to work

New challenges arise that change the status quo in every work environment, making adaptability a critical skill that will aid your career success in today's workplace environment. Thoroughly understanding adaptability and how to demonstrate it at work ensures you can pivot your strategies and remain successful – an important characteristic of valued employees. Whether the change you encounter is systematic, organizational, or industry-wide, being flexible, positive, and willing to work towards the best solutions, regardless of the circumstances, will remain vital to career success in the years ahead. 



How to handle change at work

Handling change at work effectively involves a combination of adaptability, communication, and proactive strategies. Here are some steps to help you manage change at work:

1. Challenge your interpretation of the facts

During any time of change, you will likely face unfamiliar challenges which may make you apprehensive. When these feelings arise, challenge your interpretation of events by asking yourself the following questions: 


 

  • Is your interpretation of the change you are facing rational, objective, and based purely on the facts?
     

  • Can you challenge your interpretation with an opposing argument?
     

  • If so, what’s the alternative perspective of this situation?

The way you interpret information relating to the change you are facing and the meaning you give them is what will determine your approach to change, the course you take and ultimately how successful you will be in adopting the change. By objectively examining a challenging situation and doing your best to remove your negative, and potentially unfounded assumptions, you’ll have a more positive emotional reaction and subsequently will be able to determine the practical steps you need to take to arrive at a productive outcome.

 

2. Ask questions 

Much of the anxiety people fear about change stems from a fear of the unknown and the only way to alleviate the ambiguity is to fill in the gaps. Don’t wait for people to provide it to you, ask. Your manager may not know that you want or need the information. The sooner you have all the facts, the sooner you will be able to process them and interpret what they mean to you.

 

3. Recognise and rationalize the voice of caution

When confronted with an unfamiliar situation, there’s often a voice of caution in our heads telling us to be careful and go slow. By recognizing that this is what is happening and reminding ourselves that all will be okay, we can stay open-minded and prepare to take on the change in careful, measured steps.

 

4. Reframe change as an opportunity

By exploring what specifically about the change is making you feel anxious, you can reframe the process into one of opportunity. For example, are you worried about a lack of support or an increased workload?

 

Now consider whether your interpretation of these aspects could be reframed in a positive light. For example, additional responsibilities and the opportunity to manage your workload with increased independence could help to advance your career.

 

Asking yourself the following questions may help:

 

  • Forget the way the change was worded when it was communicated to you. Instead, think about how you would word this challenge or change if you were to explain it to others. Saying it out loud might help you to detect what about the change is troubling you.
     

  • What are the real implications and opportunities for you?
     

  • In the past, when you handled change well, what did you do, and what actions in particular worked?
     

  • The aim here is to try to keep things in perspective and aligned with what matters to you and your career. 

5. Break down the information

Take some time to work out exactly what you will have to do differently day-to-day as a result of this change, breaking it down into smaller manageable portions. Transitioning to a new way of working, for example, may seem daunting and unfamiliar, especially in a tight timeframe, but segmenting it into individual, practical steps like the following will make it seem less intimidating: 

 

  • Consider your key tasks and identify those that will change and which will stay the same.
     

  • Highlight any new responsibilities you will have, what they entail and when key actions will be required.
     

  • Find out what the new priorities will be, what the expectations will be for you individually going forward and how this will be monitored.
     

  • Find out how you will need to collaborate with your team going forward.
     

  • Think about how you will need to use systems differently or what new software you will need to become familiar with.
     

  • Identify any areas where you feel you may need more knowledge or skills to carry out your role successfully.
     

  • Make sure you’re checking in regularly with your colleagues and manager to run through any decisions or processes you’re unsure of.

6. Be patient with yourself, persevere and ask for help if needed

It takes time and perseverance to adapt to change and learn how to demonstrate adaptability at work, so don’t expect things to transform overnight. If you’re struggling to adapt to a particular change you are facing, then ask to be directed to any relevant employee assistance programs or training resources that could help you. Talk to your manager about signing up to Hays Learning, which provides thousands of free online training courses that could help.

 

7. Broaden your comfort zone

Your comfort zone is the set of behaviors and actions that together create the drumbeat of your day-to-day life, reducing risk and stress and providing us with a sense of security. It is this comfort zone that is often threatened by change, so the challenge is to identify how to quickly establish a new routine and integrate it into your comfort zone as soon as possible. 

 

Think about how to map out your day or week now as a result of the change. What are the key regular activities you will need to do? How long will they take? When will you do them? 

 

8. Celebrate daily wins

With time, changes that might have seemed significant will start to gradually integrate into your day-to-day life and feel much more natural.  

 

During times of change, it is straightforward to focus on what you couldn't do or what went wrong, rather than what went well. Focusing on your wins every day, no matter how small will help you avoid negative emotions to understand how you are moving forward and working on embracing positive change. 

 

9. Remember it’s a lifelong skill

It’s important to remember that change can occur at any time and you will likely experience many periods of change throughout your life. Embracing change and demonstrating adaptability successfully is an important skill that will serve you well throughout your life.



Written by, Siddhi Shinde, Project Management Officer at Cloud.in


Cloud Security Beyond Native Tools: Integrating On-Premises Security Measures

 


Don't Be Cloud-Naive: Extending On-Premises Security to Your Cloud Journey

Migrating to the cloud offers undeniable benefits, but security concerns can hold businesses back. Relying solely on native cloud security tools might not be enough.

A holistic defense strategy requires integrating your existing on-premises security solutions with your cloud environment. This ensures comprehensive protection across your entire IT landscape.

Why Extend On-Premises Security?

  • Unified Visibility & Control: Gain a centralized view of security posture across both cloud and on-premises environments.

  • Consistent Security Policies: Enforce the same security policies consistently, regardless of location.

  • Reduced Complexity: Manage security from a single pane of glass, streamlining operations.

Strategies for Extending Security

Here are key strategies to bridge the security gap between on-premises and cloud:

  • Cloud Security Posture Management (CSPM): Utilize CSPM tools to continuously monitor and identify security misconfigurations in your cloud environment.

  • Cloud Access Security Broker (CASB): Implement a CASB to centrally manage access controls and user behavior across all cloud applications.

  • Data Loss Prevention (DLP): Extend your existing DLP solution to the cloud to prevent sensitive data from being accidentally or maliciously leaked.

  • Security Information and Event Management (SIEM): Integrate your SIEM with cloud security logs to gain a consolidated view of security events across your entire IT infrastructure.


Move Beyond Lift-and-Shift: Architecting for Cloud-Native Benefits

 


Many businesses see cloud migration as a simple "lift-and-shift" process. While it offers some initial benefits, it fails to harness the true power of cloud computing. To thrive in this dynamic environment, companies need to embrace cloud-native architectures.

Cloud-native applications are designed specifically for the cloud, utilizing features like autoscaling, serverless functions, and containerization. This approach offers significant advantages:

  • Cost Efficiency: Autoscaling automatically adjusts resources based on demand, eliminating overprovisioning and reducing costs.

  • Enhanced Agility: Serverless functions eliminate infrastructure management, enabling faster development and deployment cycles.

  • Effortless Scalability: Cloud-native applications can easily scale up or down to meet fluctuating needs.

  • Improved Fault Tolerance: Cloud platforms offer built-in redundancy and fault tolerance, ensuring application uptime.

Refactoring for the Cloud

Transitioning to a cloud-native approach often involves refactoring existing applications. This isn't a complete rewrite but a strategic restructuring to leverage cloud-specific features. Here are some key strategies:

  • Microservices Architecture: Break down monolithic applications into smaller, independent services that can be developed and deployed independently.

  • Containerization: Package applications and their dependencies into standardized containers for easy deployment and portability across cloud environments.

  • API-driven Development: Design applications around APIs to enable flexibility, integration, and communication between services.

Cloud.in: Your Cloud Journey Partner

Cloud.in empowers businesses to navigate their cloud journey seamlessly. We offer a comprehensive suite of services, including:

  • Cloud Migration Assessments: We analyze your existing applications and develop a roadmap for cloud-native adoption.

  • Cloud Architecture Design: We design a secure and scalable cloud architecture tailored to your needs.

  • Cloud Development & Refactoring: We assist with refactoring your applications to leverage cloud-specific features.

  • Managed Cloud Services: We provide ongoing management and support for your cloud infrastructure.

Ready to Embrace Cloud-Native?

Get a free consultation through our cloud experts: sales@cloud.in/ +91 20 6608 0123



AWS-Managed Prefix List: The Modern Way Of Restricting Origin Traffic

 


Introduction

Securing your web applications and APIs is paramount in today's cloud-centric world. One critical aspect is ensuring that your content origins are accessible only via your CDN (Content Delivery Network), in this case, Amazon CloudFront. 

AWS has recently introduced a more efficient method to achieve this, which is using an AWS-managed prefix list for CloudFront. This post will guide you through how to use this new feature to restrict access to your origins effectively.

Why Restrict Origin Access?

Before diving into the technical details, it's essential to understand why restricting origin access is crucial:

  1. Security: Prevent direct access to your origin servers, reducing the attack surface.

  2. Performance: Ensure that all traffic to your origin goes through CloudFront, leveraging its caching and performance optimization.

  3. Cost-Effectiveness: Reduce bandwidth costs by ensuring requests are served from the CDN cache when possible.

Introducing AWS-Managed Prefix List

AWS has introduced a managed prefix list that contains the IP ranges used by CloudFront. This list is maintained and updated by AWS, ensuring you always have the correct ranges without manual intervention. 

By using this list, you can configure your origin security groups to allow only CloudFront traffic, enhancing security and reducing administrative overhead.

Step-by-Step Guide to Restricting Origin Traffic

1. Create a CloudFront Distribution

If you haven't already, the first step is to create a CloudFront distribution. This process involves:

  • Defining your origin (e.g., an EC2 instance, an Elastic Load Balancer).

  • Configuring cache behaviors.

  • Setting up SSL/TLS settings for secure communication.

2. Identify Your Origin Security Group

For EC2 instances or Elastic Load Balancers, you need to modify the security group attached to your origin. This security group will be updated to restrict traffic to only CloudFront IP ranges.

3. Modify the Security Group with the AWS-Managed Prefix List

AWS provides a managed prefix list that includes all CloudFront IP ranges. Follow these steps to update your security group:

  1. Access the Security Group:

    • Navigate to the EC2 Dashboard in the AWS Management Console.

    • Select "Security Groups" from the left-hand menu.

    • Find and select the security group associated with your origin.

  2. Edit Inbound Rules:

    • Click on the "Inbound rules" tab.

    • Click "Edit inbound rules."

  3. Add Rules for the AWS-Managed Prefix List:

    • Add a new rule:

      • Type: Custom TCP Rule (or HTTP or HTTPS).

      • Protocol: TCP.

      • Port Range: 80 (for HTTP).

      • Source: Prefix list.

      • Prefix List: Select the AWS-managed prefix list for CloudFront (com.amazonaws.global.cloudfront.origin-facing).

    • Add another rule:

      • Type: Custom TCP Rule (or HTTPS).

      • Protocol: TCP.

      • Port Range: 443 (for HTTPS).

      • Source: Prefix list.

      • Prefix List: Select the AWS-managed prefix list for CloudFront (com.amazonaws.global.cloudfront.origin-facing).

  4. Save Rules:

    • Click "Save rules" to apply the changes.

Important Considerations

  • Rule Limits: The AWS-managed prefix list for CloudFront counts as 55 rules in a security group. The default quota for security groups is 60 rules, leaving room for only 5 additional rules if you add one managed prefix list for CloudFront in your inbound rules. If you limit both HTTP and HTTPS requests using the managed prefix list for CloudFront, you must add two separate rules, which will count as 110 total rules.

  • Quota Increase: You can request a quota increase for your security group rules if necessary. However, a simpler and more efficient approach is to open only one inbound port, preferably HTTPS. Configure the CloudFront origin protocol policy to use only HTTPS to access your origin. This way, you only need one rule, which counts as 55 rules, staying within the default quota.

4. Configure CloudFront to Use HTTPS (Optional but Recommended)

To ensure that CloudFront communicates with your origin only over HTTPS:

  1. Access CloudFront Distribution:

    • Navigate to the CloudFront console.

    • Select your distribution.

    • Click on "Origins and Origin Groups."

  2. Edit Origin:

    • Select your origin.

    • Click "Edit."

  3. Configure Origin Protocol Policy:

    • Set the "Origin Protocol Policy" to "HTTPS Only."

  4. Save Changes:

    • Save your changes.

5. Verification

After updating the security group and CloudFront settings, verify that your origin is now only accessible through CloudFront:

  • Direct Access Test: Try to access your origin directly via its IP address or domain name. This should fail if the security group is configured correctly.

  • CloudFront Access Test: Access your content through the CloudFront distribution URL. This should succeed, indicating that CloudFront can access the origin.

6. Monitoring and Maintenance

Regularly monitor your CloudFront distribution and origin metrics to ensure everything functions as expected. AWS will automatically update the managed prefix list, so your security group remains up-to-date without additional effort.

Conclusion

Using the AWS-managed prefix list for CloudFront is a modern and efficient way to secure your origin servers. By leveraging this managed service, you can ensure that only traffic from CloudFront reaches your origins, enhancing security and reducing the need for manual IP range updates. Implement this in your infrastructure today to take advantage of these benefits.



Written by, Shubham Kumar, DevSecOps Engineer at Cloud.in


Cross-Account Access Demystified: IAM Roles, External IDs, and AssumeRole Done Right

Secure cross-account access becomes essential as businesses grow their AWS infrastructure. The ability to correctly configure cross-account ...